BBB RevC will not boot from usb or eMMC

That image should auto-flash from microSD to eMMC on first bootup… Just use etcher.io to write it directly to the microSD…

Regards,

Should I hold the S2 button down on power up until all 4 LEDs come on?
Or is that necessary with the eMMC flasher images?

1 Like

Since the eMMC is blank right now, it’s safe to just power it up… The microSD will take over…

1 Like

It seems to be loading (no output to the putty session though)…
A clarification,
Once this is loaded into eMMC, I am pretty sure my FPP v5.5 image is NOT
an eMMC-flasher image… Based on all the hoopla I have gone through the
past few days. I think to make it a flasher, I somehow

  1. Have to edit the uEnv.txt file and uncomment that last line
  2. Save it, load the image to SD,
  3. Power down the BBB,
  4. Insert the SD into the slot,
  5. Power back up while pressing the S2 button.

So, in the process above, is there any “special” way I should edit the file in /boot
folder of that image?

Thanks again Robert, you have been most helpful…
And I see while typing this up, the BBB started throwing output the the putty session.
I say one fail fly by in regards to something being readOnly in the /etc folder.
but these were the final messages in the output.

752.195122] systemd-shutdow: 46 output lines suppressed due to ratelimiting
[ 752.462231] systemd-shutdown[1]: Syncing filesystems and block devices.
[ 752.619173] systemd-shutdown[1]: Sending SIGTERM to remaining processes…
[ 752.662022] systemd-journald[6607]: Received SIGTERM from PID 1 (systemd-shutdow).
[ 752.716077] systemd-udevd[6623]: rtc-max6902: Worker [6632] did not accept message, killing the worker: Connection refused
[ 752.734846] systemd-udevd[6623]: rtc-max6902: Worker [6630] did not accept message, killing the worker: Connection refused
[ 752.746376] systemd-udevd[6623]: rtc-max6902: Worker [6649] did not accept message, killing the worker: Connection refused
[ 752.762069] systemd-udevd[6623]: rtc-max6902: Worker [6635] did not accept message, killing the worker: Connection refused
[ 752.774034] systemd-udevd[6623]: rtc-max6902: Worker [6631] did not accept message, killing the worker: Connection refused
[ 752.785456] systemd-udevd[6623]: rtc-max6902: Worker [6639] did not accept message, killing the worker: Connection refused
[ 752.796908] systemd-udevd[6623]: rtc-max6902: Worker [6637] did not accept message, killing the worker: Connection refused
[ 752.825237] systemd-shutdown[1]: Sending SIGKILL to remaining processes…
[ 752.850067] systemd-shutdown[1]: Unmounting file systems.
[ 752.862510] [6855]: Remounting ‘/’ read-only in with options ‘errors=remount-ro’.
[ 752.888090] EXT4-fs (mmcblk0p1): re-mounted. Opts: errors=remount-ro
[ 753.031121] systemd-shutdown[1]: All filesystems unmounted.
[ 753.037221] systemd-shutdown[1]: Deactivating swaps.
[ 753.042804] systemd-shutdown[1]: All swaps deactivated.
[ 753.048238] systemd-shutdown[1]: Detaching loop devices.
[ 753.054488] systemd-shutdown[1]: All loop devices detached.
[ 753.060278] systemd-shutdown[1]: Detaching DM devices.
[ 753.119204] reboot: Power down

i would really really ask the developer behind that project.

I’m sorry, i don’t know what they use…

Regards,

1 Like

SUCCESS! BBB is sitting at a login prompt in the putty session…

1 Like