Re: [beagleboard] blank flasher

[Tim Limon]

Hi Robert,I need your expertise here, please.  I am still unable to boot a production debian image from an SD card.  I’m stuck working with the paltry 2Gb eMMC.  I’ve included the log from the serial port during two boot attempts: one with S2 not depressed and one with S2 depressed.  Let me know what to do, please.—Tim 



-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


screenlog.0
Description: Binary data
On Jan 5, 2016, at 10:43 AM, Tim Limón  wrote:Spoke too soon. Bone-68 did not like to reboot.  it stalled again.  reflashing to start over again using the only working image.On Tue, Jan 5, 2016 at 10:20 AM, Tim Limón  wrote:I ended up downgrading the kernel thanks to your instructions: https://groups.google.com/forum/#!topic/beagleboard/LEMjcdgYM50I'll give the eth0 a try tonight.  I also ordered a serial cable  :)On Tue, Jan 5, 2016 at 9:26 AM, Tim Limón  wrote:As far as the eth0 issue, I can configure and bring up with ifup but there is no communication with the router.  Pings remain unanswered, and the network sees the mac address, but no IP is assigned.  Also the lights on the Ethernet port are dead.  I have a working rev C board with 7.9 loaded.  I moved the /etc/network/interfaces file from that on onto the 8.3, with no luck.  I;m thinking at some point I may need to RMA the boardThank you for the help, by the way.  I appreciate your generosity.On Tue, Jan 5, 2016 at 9:13 AM, Tim Limón  wrote:I have no serial cable.  On Tue, Jan 5, 2016 at 9:12 AM, Robert Nelson  wrote:On Tue, Jan 5, 2016 at 11:08 AM, Tim Limón  wrote:
> Thanks for the help.  The 8.3 image I loaded on my A5C board has issues with
> the Ethernet port.  Could you recommend a 7.9 or 7.5 (LTS) snapshot?  These
> two "production release" images won't flash on my old board:

What "issues" are you seeing?

> BBB-eMMC-flasher-debian-7.9-console-armhf-2015-11-03-2gb.img
> BBB-eMMC-flasher-debian-7.9-lxde-armhf-2015-11-03-2gb.img

please attach a serial boot log (eMMC flasher logs all data over serial..)

Regards,

--
Robert Nelson
https://rcn-ee.com/
--  --Tim408-309-4207www.linkedin.com/pub/timothy-limon/4/867/869

--  --Tim408-309-4207www.linkedin.com/pub/timothy-limon/4/867/869

--  --Tim408-309-4207www.linkedin.com/pub/timothy-limon/4/867/869

--  --Tim408-309-4207www.linkedin.com/pub/timothy-limon/4/867/869





-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Debian: re-partition 2Gb eMMC for a little more space?

[tim . limon]

Hello,
I have an old A5C board that I'm bringing up for a temperature logger.  I 
flashed 4.1.13-ti-r38 last night, did the usual "apt-get update", installed 
the Atheros firmware, configured the WiFi, and now I'm out of space. I 
can't even use "apt-get remove" at this point.  I'd like to keep the MMC as 
a removable device so I can grab the data once in a while, so putting the 
boot image is less desirable.

Is there anyway to re-partition the eMMC card so I can have some breathing 
room to remove some of the unneeded packages?

Here's the stats:

root@beaglebone:~# *df -h*
Filesystem  Size  Used Avail Use% Mounted on
udev 10M 0   10M   0% /dev
tmpfs98M  4.4M   94M   5% /run
/dev/mmcblk1p1  1.8G  1.8G 0 100% /
tmpfs   245M 0  245M   0% /dev/shm
tmpfs   5.0M 0  5.0M   0% /run/lock
tmpfs   245M 0  245M   0% /sys/fs/cgroup
/dev/mmcblk0p1   15G   24K   15G   1% /media/card
root@beaglebone:~#
root@beaglebone:~# *fdisk -l*

Disk /dev/mmcblk0: 14.9 GiB, 15931539456 bytes, 31116288 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xfb28685a

Device Boot Start  End  Sectors  Size Id Type
/dev/mmcblk0p1   2048 31115263 31113216 14.9G  c W95 FAT32 (LBA)

Disk /dev/mmcblk1: 1.8 GiB, 1920991232 bytes, 3751936 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x

Device Boot Start End Sectors  Size Id Type
/dev/mmcblk1p1 * 2048 3751935 3749888  1.8G 83 Linux

Disk /dev/mmcblk1boot1: 1 MiB, 1048576 bytes, 2048 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mmcblk1boot0: 1 MiB, 1048576 bytes, 2048 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
root@beaglebone:~#
root@beaglebone:~#


Thank you fo the help,
--Tim

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] blank flasher

[tim . limon]

Thank you, Robert.

I stumbled a bit getting the SD card to accept the image file.  I ended up 
formatting my 8 GB card as NTFS with a 1024 block size prior to writing the 
image via Win32DiskImager.  The card became unreadable in windows once the 
image was written.  I took a chance and installed it in the BBB anyway. 
 When I applied power, the board began reflashing.  I'm up and running now. 
Thank you for the pointer.


Does anyone know why the card becomes unreadable once the .img file is 
written?  Is this normal behavior?

 

On Monday, January 4, 2016 at 6:04:57 AM UTC-8, RobertCNelson wrote:
>
> On Sun, Jan 3, 2016 at 12:29 AM,  > 
> wrote: 
> > I'm new at this so I beg your forgiveness. 
> > 
> > Which files go on the USB stick and which go on the MicroSD card? 
> > 
> > I have a A5C board that stalls on booting and won't allow me to boot 
> from 
> > the SD card.  I'm hoping the USB flasher will help. 
> > 
> > Thanks on advance for the guidance 
>
> Use any image market with '2gb' here: 
>
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Image_Testing_Snapshots
>  
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] blank flasher

[tim . limon]

I'm new at this so I beg your forgiveness.  

Which files go on the USB stick and which go on the MicroSD card?  

I have a A5C board that stalls on booting and won't allow me to boot from 
the SD card.  I'm hoping the USB flasher will help.

Thanks on advance for the guidance

--Tim

On Monday, December 21, 2015 at 4:36:59 PM UTC-8, William Hermans wrote:
>
> *Sure, internally, it's just bmaptools/dd...*
>>
>> * and it'll dump errors/directions to the serial console..*
>>
>> * For almost all *.img's i include a *.job.txt file that'll just work.*
>>
>
> Ok, cool. I kind of half expected this to be a Jessie only feature. 
>
> On Mon, Dec 21, 2015 at 5:17 PM, Robert Nelson  > wrote:
>
>> On Mon, Dec 21, 2015 at 5:35 PM, William Hermans > > wrote:
>> > Robert, can this also be used with the "release" images as well ?
>>
>> Sure, internally, it's just bmaptools/dd...
>>
>> and it'll dump errors/directions to the serial console..
>>
>> For almost all *.img's i include a *.job.txt file that'll just work.
>>
>> Regards,
>>
>>
>> --
>> Robert Nelson
>> https://rcn-ee.com/
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to beagleboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: permission denied to pins unless root

[tim . limon]

Try this solution:  It worked for me!

http://unix.stackexchange.com/questions/118716/unable-to-write-to-a-gpio-pin-despite-file-permissions-on-sys-class-gpio-gpio18

"I have not played with the GPIO pins this way but based on lgeorgets 
*second* comment and this 
article,
 
you must first set the direction of the pin to "out". The direction node is 
owned by root, so:

sudo sh -c 'echo out > /sys/class/gpio/gpio18/direction'

sh -c is needed here to execute that command in a root subshell. This is 
because sudo echo out > direction would execute echo as root, but the 
redirection (> direction) would be done by your current (non-root) shell. 
You could also just do this su root.
After that you should, hopefully, be able to set value as cameron."

On Thursday, September 26, 2013 1:23:11 AM UTC-7, sam.oute...@gmail.com 
wrote:
>
>
> I'm trying to run a simple led blink example like here:
>
>
> http://www.phys-x.org/rbots/index.php?option=com_content&view=article&id=104:lesson-1-beaglebone-black-blink-led&catid=46:beaglebone-black&Itemid=81
>
> I'm running a Ubuntu image on my beaglebone black with node 0.8.x.  I get 
> a permission problem that looks like some form of failure to have access to 
> the pins.  I added my user to the dialout group and that didn't work.  Then 
> I added my user to every group I could find and that didn't work either.  
> The only way I can get the code to run and do the blinking is if I run it 
> as root.  My question is, how do I give my user access to whatever is 
> needed to reach the pins running as non-root.  The permission problem looks 
> like the following:
>
> fs.js:338
>   return binding.open(pathModule._makeLong(path), stringToFlags(flags), 
> mode);
>  ^
> Error: EACCES, permission denied 
> '/sys/class/leds/beaglebone:green:usr0/trigger'
> at Object.fs.openSync (fs.js:338:18)
> at Object.fs.writeFileSync (fs.js:756:15)
> at Object.f.pinMode 
> (/home/ubuntu/projects/hello_express/node_modules/bonescript/index.js:132:20)
> at Object. 
> (/home/ubuntu/projects/hello_express/hello_express.js:31:3)
> at Module._compile (module.js:449:26)
> at Object.Module._extensions..js (module.js:467:10)
> at Module.load (module.js:356:32)
> at Function.Module._load (module.js:312:12)
> at Module.runMain (module.js:492:10)
>
> Thanks for any help in advance.  I'm pretty excited to get this running. 
>
> - Samuel
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.