Actions
Forum Thread Details
  • State Not Answered
  • Replies 3 replies
  • Subscribers 102 subscribers
  • Views 432 views
  • Users 0 members are here
Related

BBB not booting after Flashing

Former Member

Hello,

 

I just started with a new batch of BBBs.  I placed the SD Card in and powered them up.  LED blinks and then goes solid as expected.  Remove power and SD card.  Reapply power and only the power LED comes on.

 

The same SD card works with earlier version of the BBB.  I can get order dates if that helps.  Both boards have "PCB REVB6" in copper near the power connector.  Both came in the white Element 14 box.  Not sure what else I can compare easily.

 

Has anyone else had this problem?

 

Thanks,

Rob

Parents
  • 0

    Ok, I looked on line and a user had a similar issue and did a new SDCard configuration and said it worked.  So I am trying the same thing.  First try failed, but I did see something odd that could well be the issue, but not a BBB expert enough to know for sure.

     

    My project was using an old 2GB of the Angstrom OS, but we needed more memory.  It was expanded using these steps (first question is this valid - it seemed to work):

    • fdisk /dev/mmcblk0
    • delete partition 2
    • new partition 2 same start, but end is final sector
    • write the changes
    • reboot
    • resize2fs /dev/mmcblk0p2
    • space increase verified with df -h

    I made an image and probably updated 10-15 boards.  Got the new batch in a no luck.  So I started a rebuild of the OS in the hope of making a new image.  However in fdisk if I look at the partition option the old boards said "Disk /dev/mmcblk0: 3867 MB..." the new ones report "Disk /dev/mmcblk0: 3825 MB...".  So my guess is that the image was too large for the new BBB and either missed something critical or did a wrap of the memory copy and over wrote the beginning.

     

    Well a 4Gig memory chip should have 4Gig since they have a set number of address lines - right?  Anyway the eMMC on one is a Kingston KE4CN2H5A (old) and the other is a Kingston EMMC04G-S100 (new).  I think these are the part numbers anyway, I need to get boards to production and each one needs to be hand updated.  So if they are wrong let me know, but I am hoping to get an answer with this information.

     

    Thanks,

    All

Reply
  • 0

    Ok, I looked on line and a user had a similar issue and did a new SDCard configuration and said it worked.  So I am trying the same thing.  First try failed, but I did see something odd that could well be the issue, but not a BBB expert enough to know for sure.

     

    My project was using an old 2GB of the Angstrom OS, but we needed more memory.  It was expanded using these steps (first question is this valid - it seemed to work):

    • fdisk /dev/mmcblk0
    • delete partition 2
    • new partition 2 same start, but end is final sector
    • write the changes
    • reboot
    • resize2fs /dev/mmcblk0p2
    • space increase verified with df -h

    I made an image and probably updated 10-15 boards.  Got the new batch in a no luck.  So I started a rebuild of the OS in the hope of making a new image.  However in fdisk if I look at the partition option the old boards said "Disk /dev/mmcblk0: 3867 MB..." the new ones report "Disk /dev/mmcblk0: 3825 MB...".  So my guess is that the image was too large for the new BBB and either missed something critical or did a wrap of the memory copy and over wrote the beginning.

     

    Well a 4Gig memory chip should have 4Gig since they have a set number of address lines - right?  Anyway the eMMC on one is a Kingston KE4CN2H5A (old) and the other is a Kingston EMMC04G-S100 (new).  I think these are the part numbers anyway, I need to get boards to production and each one needs to be hand updated.  So if they are wrong let me know, but I am hoping to get an answer with this information.

     

    Thanks,

    All

Children