Hi,
 I have the same problem,I have not deleted any files. I have downloaded  
image of angstrom kernel and file-system from below link.
  
https://s3.amazonaws.com/angstrom/demo/beaglebone/Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.06.20.img.xz
 

and followed the procedure to boot through SD Card given by the following 
link.

http://www.beagleboard.org/Getting<http://www.beagleboard.org/Getting%20Started#update>

Initially I have been holding the BOOT/USER button and power up the BBB 
board all 4 LED's will lid up,
By then I release the BOOT button, there after only 3 LED's start blinking 
USR0, USR1 and USR2 nothing happens.
Can you please suggest what has to be done to boot it properly?


Thanks & Regards
Harsha
On Monday, August 26, 2013 7:39:11 PM UTC+5:30, [email protected] wrote:
>
> On Monday, August 26, 2013 7:13:54 AM UTC-4, Manoj Jayaram wrote:
>
>> I have removed the existing kernel and files system from BBB. I have 
>> downloaded prebuild  image of angstrom kernel and file-system from below 
>> link.
>>   
>> https://s3.amazonaws.com/angstrom/demo/beaglebone/Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.06.20.img.xz
>>  
>>
>> and followed the procedure to boot through SD Card given by the following 
>> link.
>>
>> http://www.beagleboard.org/Getting%20Started#update
>>
>> The 4 LED,s get lit up if i hold down the switch after that the USR0 and 
>> USR2 LED's keep blinking but nothing happens,  still am not able to boot my 
>> board.
>> Any help will be highly appreciated. 
>>
>
> Can you get a serial console connected?
>
>
> http://circuitco.com/support/index.php?title=BeagleBone_Black_Accessories#Serial_Debug_Cables
>
> If so, then you should be able to boot the flasher and log in via the 
> serial cable and see what's going on.
>
> I *think* the issue is because you removed the filesystem from the BBB 
> first.  I have been working on building my own flasher image and I found 
> that the stock flasher image didn't have some of the necessary tools, 
> namely blockdev and kpartx.  In my case, it didn't matter because the eMMC 
> was already set up, the script got errors but was still able to unpack the 
> root fs image.
>
> You can then verify this theory by manually running the flasher (execute 
> /usr/bin/emmc.sh) and look for errors.  If I'm right about the missing 
> blockdev & kpartx, then you *should* be able to connect the BBB to the 
> ethernet, and use opkg to install blockdev and kpartx to the flasher image 
> and retry the emmc.sh script.  For more information, take a look at this 
> page that describes how the flasher works:
>
> http://www.crashcourse.ca/wiki/index.php/BBB_software_update_process
>
> If you don't have a serial cable, but you have a Linux "host" system (e.g. 
> a VM), you can mount the flasher SD card (the second, linux partition) and 
> look for kpartx and blockdev tools on the mounted fs.  You'd have to get 
> hold of the ipks for blockdev and kpartx and somehow install them from your 
> Linux host.
>
> Hope this helps.
>
>
> -W.
>
>

-- 
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to