Odroid N2+ Boot up Problem with eMMC

Troubleshooting
21

Hi Michalng, thank you for this amazon piece of software. I met the same problem that the OP has and need some help.

Required Information

  • DietPi version | 9.13
  • Distro version | N/A
  • Kernel version | N/A
  • Architecture | Armv8
  • SBC model | odroid n2 (2G RAM version)
  • Power supply used | Hardkernel official 12V-2A
  • SD card used | Hardkernel official 128G eMMC

Steps to reproduce

  1. Download DietPi_OdroidN2-ARMv8-Bookworm.img.xz from dietpi.com
  2. Flash image with balenaEtcher 2.12 to eMMC with Hardkernel official eMMC to MicroSD adapter on Windows 11
  3. Plug in HDMI + 12-2A power supply

Expected behaviour

System should boot and should see HDMI output

Actual behaviour

  • [Expected] Red power light solid on
  • [Expected] After 2 seconds, blue light start to flash
  • [Issue] Monitor has no output

Extra details

  1. I tried 9.8 release before and it worked perfectly. However, I recently installed desktop and broke the boot somehow, so I decided to flash the latest OS again, but this time it did not boot. If someone can send me a 9.8 version of Odroid N2 image, I can test.
  2. Regarding your previous comment (Odroid N2+ Boot up Problem with eMMC - #20 by MichaIng), can you provide a bit more detail about steps?
22

Thanks for your report.

How do you boot it, via SPI bootloader or MMC? In my case it boots fine when switching to MMC bootloader. With SPI bootloader, it spits out:

Load FIP HDR from SPI, src: 0x00010000, des: 0xfffd0000, size: 0x00004000, part: 0
fw parse done
Load ddrfw from SPI, src: 0x00038000, des: 0xfffd0000, size: 0x00004000, part: 0
Error! DDR fw check fail!

on serial console in fast loop, never booting. I remember I had issues with SPI bootloader and eMMC in the past, while the SPI bootloader could boot from SD card and USB just fine. But at that time, I tested the petitboot that the board ships with. Now I have the binary flashed that is shipped with our image. Not sure whether that one was ever able to boot from eMMC in my case.

Can you verify you have the switch set to “MMC”?

EDIT: Ah in your case blue LED flashes. Okay then it booted into kernel already, hence different issue. Are you sure it does not boot up at all, or is just HDMI output missing? Wait will check that in my case.

EDIT2: HDMI working in my case as well.

23

Hi Michalng,

I figured out there should be an issue with the HDMI on my board. I use wired connection and can SSH into DietPi 9.13.

Thank you for your testing anyway!

24

Just out of curiosity, does my firmware build work for you when it’s placed in the SPI flash?

25

I have not used a serial console before so I’m not sure. I tried SPI booting and I saw solid blue light.

26

My firmware build also supports the use of the U-Boot console with HDMI and USB keyboard, therefore serial console access is not strictly necessary.

27

I remember Armbian also enabled it for some boards, disabled it for some again. Not sure about U-Boot defaults in each case. Sounds like a pretty huge benefit it U-Boot brings up HDMI (and USB anyway) with necessary drivers.

… booooah, can you please use a professional file hosting, instead of one which forces you to watch a 30 seconds advertising of far right NiUS propaganda website?

But your U-Boot build flashed to SPI boots from eMMC successfully. However, I flashed the one from Armbian again, and it works as well now. So not sure why I ran into the error earlier, maybe it appears somewhat random, or something went wrong when I flashed that earlier.

28

Then I guess it is the known (at least for me) issue with petitboot and eMMC. Please switch to “MMC” when booting from eMMC.