Hi,
So I have done something rather stupid and managed to brick my BBB!
I was attempting to copy a bootable SD image using the dd command to the nand flash, and instead of copying the rootfs partition I copied the boot partition! e.g.
dd if=/dev/mmcblk0p1 of=/dev/mmcblk1p1
Now the device does not boot, no LED’s apart from power.
If I look at the serial console output all I get is the letter ‘C’ repeated every 300m or so. 
denton.matthew@gmail.com <denton.matthew@gmail.com> [14-10-28 16:52]:
Hi,
So I have done something rather stupid and managed to brick my BBB!
I was attempting to copy a bootable SD image using the dd command to the
nand flash, and instead of copying the rootfs partition I copied the boot
partition! e.g.dd if=/dev/mmcblk0p1 of=/dev/mmcblk1p1
Now the device does not boot, no LED's apart from power.
If I look at the serial console output all I get is the letter 'C' repeated
every 300m or so.--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi Denton,
as for my knowledge it is not that easy to brick a BBB... 
Prepare a SDcard for booting from it, insert the SDcard, boot and
repair the emmc...
If necessary, "urge" the board to boot from SDcard.
Or try the steps described here:
Under "Update board with latest software"
GOOD LUCK!
Best regards,
mcc
I’ve managed to really screw up one of my Beaglebone Blacks too. It appears that I have clobbered the partition table on the eMMC, which seems to make U-Boot very unhappy! The AM335x processor skips the eMMC boot and goes directly to uSD boot after power is applied, no matter the position of the boot switch. I have tried booting several eMMC flashers, but none have worked:
The latest Debian (5/14/14) shows this in serial console:
`
U-Boot SPL 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54)
** Partition 1 not valid on device 0 **
spl_register_fat_device: fat register err - -1
`
and reboots every ~48 seconds
Angstrom (06/20/13) shows this once:
`
U-Boot SPL 2013.04-dirty (Jun 19 2013 - 09:57:14)
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
OMAP SD/MMC: 0
** Partition 1 not valid on device 0 **
spl: fat register err - -1
`
I even tried an old BBW A6A image from 11/12/12:
U-Boot SPL 2011.09-00053-gb423c52 (Aug 10 2012 - 11:26:55) Texas Instruments Revision detection unimplemented No daughter card present Did not find a recognized configuration, assuming General purpose EVM in Profile 0 with Daughter board
I have used the Ubuntu 12.04 Disks tool to wipe the partitions and/or format the uSD card. I have tried Win32 Disk Imager version 0.9 and 0.91 on Windows 7x64. I have tried dd under Ubuntu. I have also tried several different uSD cards. The board is powered via a 24v, 50 watt power supply going to a 5v 50 watt DC-DC converter (the other 7 BBBs running on this power supply are fine…). This is a Rev C from Element14.
Any other insight? I’m running out of ideas…perhaps I can fiddle with U-Boot? Is there a special version, of U-Boot, that will ignore the eMMC, or give me the power to create a partition table? If I can just get a user prompt, that would go a long way.
Thanks,
Louis
I figured out my problem…it was hardware. My mounting posts were randomly touching the uSD holder pins.
The crazy thing is, is that U-Boot would detect the card and be able to read it’s info (manufacturer, ID, size, etc) but could not read the partition table.
Hope this saves someone else a few days of troubleshooting…
