Sorry that this is probably a dumb question, but is it possible to not blow
away the partition table since I just want to swap the MLO and u-boot.img?
I'm just running the standard image on a Beagle Bone Black that does not
have an eMMC or hdmi chip. I assumed it was busy because I was trying to
reprogram the disk while on an OS that was using the disk?
This was the error:
Checking that no-one is using this disk right now ...
BLKRRPART: Device or resource busy
After adding the force option it said:
Checking that no-one is using this disk right now ...
BLKRRPART: Device or resource busy
This disk is currently in use - repartitioning is probably a bad idea.
Umount all file systems, and swapoff all swap partitions on this disk.
Use the --no-reread flag to suppress this check.
Disk /dev/mmcblk0: 121008 cylinders, 4 heads, 16 sectors/track
sfdisk: ERROR: sector 3069576189 does not have an msdos signature
/dev/mmcblk0: unrecognized partition table type
Old situation:
No partitions found
New situation:
Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End MiB #blocks Id System
/dev/mmcblk0p1 * 1 3780 3780 3870720 83 Linux
/dev/mmcblk0p2 0 - 0 0 0 Empty
/dev/mmcblk0p3 0 - 0 0 0 Empty
/dev/mmcblk0p4 0 - 0 0 0 Empty
Successfully wrote the new partition table
Re-reading the partition table ...
BLKRRPART: Device or resource busy
I have the serial output after the last test, but not from the test where
I did not recreate the partition table.
U-Boot 2015.10-rc2-00001-g5879130-dirty (Oct 09 2015 - 15:52:49 +0000)
Watchdog enabled
I2C: ready
DRAM: 512 MiB
Reset Source: Global external warm reset has occurred.
Reset Source: Power-on reset has occurred.
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment
Net: <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot: 0
gpio: pin 53 (gpio 53) value is 1
switch to partitions #0, OK
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt ...
Checking for: /boot.scr ...
Checking for: /boot/boot.scr ...
Checking for: /boot/uEnv.txt ...
** Invalid partition 2 **
** Invalid partition 3 **
** Invalid partition 4 **
** Invalid partition 5 **
** Invalid partition 6 **
** Invalid partition 7 **
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
Card did not respond to voltage select!
gpio: pin 54 (gpio 54) value is 1
Card did not respond to voltage select!
** Bad device mmc 1 **
Checking for: /uEnv.txt ...
Card did not respond to voltage select!
** Bad device mmc 1 **
Checking for: /boot.scr ...
Card did not respond to voltage select!
** Bad device mmc 1 **
Checking for: /boot/boot.scr ...
Card did not respond to voltage select!
** Bad device mmc 1 **
Checking for: /boot/uEnv.txt ...
Card did not respond to voltage select!
** Bad device mmc 1 **
Card did not respond to voltage select!
** Bad device mmc 1 **
Card did not respond to voltage select!
** Bad device mmc 1 **
Card did not respond to voltage select!
** Bad device mmc 1 **
Card did not respond to voltage select!
** Bad device mmc 1 **
Card did not respond to voltage select!
** Bad device mmc 1 **
Card did not respond to voltage select!
** Bad device mmc 1 **
FAILSAFE: U-Boot UMS (USB Mass Storage) enabled, media now available over
the usb slave port ...
Card did not respond to voltage select!
** Bad device mmc 1 **
Which uEnv.txt would you like? The only modifications I made from stock
were to disable the eMMC and hdmi.
Thanks,
Chris
On Thu, Oct 8, 2015 at 4:29 PM, William Hermans <[email protected]> wrote:
> I've found that 2 LEDs, or any number of LEDS on, and stuck on after a
> boot is a uEnv.txt configuration error. Anyway you can show us your
> uEnv.txt file contents ?
>
> Also it would be good to get the output from the serial debug port.
>
> On Thu, Oct 8, 2015 at 1:25 PM, Robert Nelson <[email protected]>
> wrote:
>
>> On Thu, Oct 8, 2015 at 3:06 PM, Christopher Stack <[email protected]>
>> wrote:
>> > Let me know if I need to put this in a new thread, or if someone wants
>> to
>> > take off the group entirely.
>> >
>> > I followed the directions here:
>> >
>> https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot
>> .
>> > Specifically this section: Bootloader: U-Boot and the bootloader
>> portion of
>> > Setup microSD card.
>> >
>> > After following those directions the Beagle Bone fails to boot, leaving
>> 2
>> > LEDS on and messages on UART0 saying that there is no partition table.
>> >
>> > I see the next step in Setup microSD card is creating the partition
>> table,
>> > but that doesn't seem to be working it complains that the device is
>> > currently busy. I'd prefer not to blow away the operating system if
>> that's
>> > possible? Just to see what happened I forced the sfdisk command and it
>> > seemed to create 4 partitions, only one of which had a size which seems
>> > right to me. When i rebooted though I get an error that says bad device
>> mmc
>> > 1.
>>
>> busy? odd as you just blew out the partition table in the step before...
>>
>> I'm guessing... Virtual Machine???
>>
>> or an evil auto-mounter...
>>
>> 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 [email protected].
>> 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 a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/aXv6An1xfqI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> 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 [email protected].
For more options, visit https://groups.google.com/d/optout.
