Odroid m1 Won't boot on recent images in armbian download section

[Mickynuts]

Hello, sorry for the tag (no odroid m1 tag) and if I'm in the wrong place.

 

I downloaded the image Armbian_24.8.3_ordoidm1_jammy_current_6.6.51_kde-neon-kisak-desktop

The image does not start without pressing rcy, so far normal. After flashing the mtd with armbian-installer and copying to SSD. The image still does not start. No display.

 

After trying several things and without success, I decided to try an old image:

Armbian_24.2.1_ordoidm1_jammy_current_6.6.16_xfce_desktop.

 

I here rcy boot, install, copy to SSD, flash mtd and reboot. And it works. So I tried image 6.6.51 kde Again. But without flashing the mtd. And there it boots without problems and no need for rcy.

So it seems that the last image and also the 24.2. 4 that I tried. We have a probably corrupted uboot.

I have the odroid m1 8gb.

 

I hope this will allow others not to waste hours trying because of a corrupted uboot. (This was my first attempt with armbian on this card. Before I had petitboot.)

 

Sorry for my bad English. I used Google translate.

 

PS: I tried to make a bug report form. But you have to provide an armbianmonitor -u output or something like that. And that doesn't match the fact. The card doesn't even boot.

Edited October 1, 2024 by Mickynuts

[Werner]

moved

[usual user]

6 hours ago, Mickynuts said:

I tried to make a bug report form. But you have to provide an armbianmonitor -u output or something like that. And that doesn't match the fact. The card doesn't even boot.

To get help, you have to provide proper logs. In case of boot problems, these are serial console logs. https://debug.armbian.de

[Mickynuts]

29 minutes ago, usual user said:

To get help, you have to provide proper logs. In case of boot problems, these are serial console logs.

I don't need help anymore. As said. I used the uboot present in an earlier version. I didn't try the serial, because there weren't even any screens (I thought there wouldn't be a serial either). The card seemed to just do a reboot Every 5 seconds (depending on the LEDs on the network card and the LEDs on the SSD which flash 1x. I'm not going to try again now that I have a working installation. I just wanted to share with you Other beginners who are not used to this kind of tools and not have the serial cable.

[usual user]

On 10/1/2024 at 9:06 PM, Mickynuts said:

I don't need help anymore. As said. I used the uboot present in an earlier version.

Ok, then no further action needs to be taken and your solution can be used by others in the future.
I also don't need any other firmware because my current one works according to my needs.
And for an update, I know how to build and debug it if necessary.

 

In the meantime, I've moved to 2025.01 with HDMI support enabled, so I no longer need the serial console to interact with the firmware.
And boot menus easily allow the free choice of which option should currently be booted.

Edited January 19 by usual user

[iav]

 

I did kind of manual bisect by commits to config/boards/odroidm1.conf

 

U-Boot 2024.04-armbian (Jan 29 2025 - 02:13:41 +0000)
commit 3215bf9f3699c2ee4bc741efe82065315e4ff46f
linux-u-boot-odroidm1-edge_24.8.0-trunk_arm64__2024.04-S2504-P3b44-Haddb-V73be-B4f92-R448a.deb is GOOD,

 

U-Boot 2024.07-armbian-2024.07-S3f77-P7e9c-Hfb3e-V8f4f-Bb66d-R448a (Jan 29 2025 - 02:30:21 +0000)
commit 268c2e85960978c90025bc18cf7d5f8e5cfbdab6
linux-u-boot-odroidm1-edge_24.8.0-trunk_arm64__2024.07-S3f77-P7e9c-Hfb3e-V8f4f-Bb66d-R448a.deb

is BAD

 

then I fix my Odroid M1 by doing

 

sudo apt install ./linux-u-boot-odroidm1-edge_24.8.0-trunk_arm64__2024.04-S2504-P3b44-Haddb-V73be-B4f92-R448a.deb

 

then

armbian-install → Install/Update the bootloader on MTD Flash

 

[usual user]

Ok, judging by your information, the regression takes place during the transition from U-Boot 2024.04 to 2024.07.
Since mainline U-Boot works perfect for me up to until 2025.01, it must be because of how it's built or what additional patches are applied.
Since it cannot be ruled out that it is due to a incompatible bootflow, it may be interesting to try it with my build.
If this also fails, it is possible to get more information from the HDMI output, even if access to the serial console is not available.
For the test it is perfectly sufficient to start the firmware from a prepared microSD card via RCY button.
The existing setup can stay completely unchanged.