inindev / odroid-m1 Goto Github PK

Line 32 in the script is unable to find the .dtb
local dtb=$(download "$cache" 'https://github.com/inindev/odroid-m1/releases/download/v12.0/rk3568-odroid-m1.dtb')

Hello,
thanks for this project. I'm interested in using the system you prepared for building a NAS.
I got information from odroid forum about booting from nvme:

In order to start the system from NVME, the following prerequisites are required:

• cleared SPI flash
• odroid-m1_bookworm-rc4 image on NVME
• idbloader.img and u-boot.itb in place in an otherwise cleared microSD card.
  (alternatively idbloader.img and u-boot.itb in place in SPI flash.)

Is it true or it works with petitboot? For me petitboot says "Waiting for device discovery" and I can't do anything with it when Bookworm is flashed on nvme (or SSD). To boot your system I need to disable petitboot.

Thanks!

Hi, this works in the M1S? thanks.

Just a quick note, I am running the image I built and a quick look says, things are good. I will test your published image when I get a chance. Nice!!!!

I tried downloading the image from <wget https://github.com/inindev/odroid-m1/releases/download/v12.0/bookworm.img.xz>
This failed. Where can I find your image to try?

Thanks, Steve

Is there any need or there are no big changes made on newer u-boot

Thanks !

I went for the vacation. When I turned my M1 on again after coming back, it didn't boot. I can only see blinking or not blinking "_" character when HDMI is connected. The board itself and SPI is most likely not broken as it still boots from SD card. The RTC battery was inserted just right after I bought it (which was just like a month or 2 ago).

Found this thread:
https://forum.odroid.com/viewtopic.php?f=216&t=46130

They suggest to add pcie_aspm=off to kernel command line parameters. I was struggling a bit but finally found this:
https://github.com/inindev/odroid-m1/blob/main/debian/make_debian_img.sh#L138

So I started a system from SD card, mounted the nvme as chroot-debian and run:

mount -o bind /dev chroot-debian/dev
mount -o bind /proc chroot-debian/proc
chroot chroot-debian /bin/bash

changed the kernel parameters in /boot/boot.txt and issued the command from the comment at the top of the file (I think it was /boot/mkscr.sh?)

So the result is the same: blinking or not blinking "_", depends how it decides to boot this time. Blue LED is blinking, network interface is blinking, I can hardly see any activity of nvme's green led.

I could see this behavior in the past, but in the past I managed just to restart the board and it worked. Now it looks quite dead. Any ideas?

The uboot read-me says

Once the spi flash has been written, the boot sequence should prefer removable mmc media if present, then boot m.2 nvme ssd.

Does this mean the microSD card is ignored, or is that also checked before booting the nvme ssd.
Also, if i update the spi flash, can it load and execute an OS on the nvme ssd without uboot on the drive?

I followed these 3 steps.

1. download the image

wget https://github.com/inindev/odroid-m1/releases/download/v12.0.2/odroid-m1_bookworm-1202.img.xz

2. determine the target micro sd card location

before connecting the device
ls -l /dev/sd*
ls: cannot access '/dev/sd*': No such file or directory
after connecting the device
ls -l /dev/sd*
brw-rw---- 1 root disk 8, 0 Apr 10 15:56 /dev/sda
note: for Mac the device is /dev/rdiskX

3. in the above case replace 'a' with 'X' in the command below (for /dev/sda)

sudo sh -c 'xzcat odroid-m1_bookworm-1202.img.xz > /dev/sdX && sync'

After all these steps, Odroid cannot boot from this SD card
Is there anything else that needs to be done?

Thank you
Karel