Jump to content

Odroid C2 never starting after a soft reboot (reboot command)


yandritos
Go to solution Solved by teknoid,

Recommended Posts

Odroid C2 never starting after a soft reboot (reboot command).

 

I have the same problem which other user is having with the Odroid C4

 

 

With the last kernel I have 5.10.102-meson64 the Odroid C2 never boots again after the "reboot" command, I need to unplug and plug again the power suply.

 

Thanks and best regards,

David

Link to comment
Share on other sites

To me this sounds like a kernel issue, not an individual support request. Or can't it be replicated by others?

 

I see that the smoke tests go through: https://github.com/armbian/build/runs/5793093247?check_suite_focus=true

But this is "edge" kernel, not "current".

 

@yandritos

Can you verify that the edge kernel solves it:

apt install linux-image-edge-meson64 linux-dtb-edge-meson64 linux-u-boot-odroidc2-edge
Link to comment
Share on other sites

I can't reproduce this issue on my Odroid C2. It reboots just fine on kernel 5.10.102-meson64.

 

Have to add I am still on buster userspace, so can't say yet if it works on bullseye:

 

 

user@xxx:~$ uname -a
Linux xxx 5.10.102-meson64 #22.02.1 SMP PREEMPT Sun Feb 27 09:09:25 UTC 2022 aarch64 GNU/Linux
user@xxx:~$ cat /etc/armbian-image-release
# PLEASE DO NOT EDIT THIS FILE
BOARD=odroidc2
BOARD_NAME="Odroid C2"
BOARDFAMILY=meson-gxbb
BUILD_REPOSITORY_URL=https://github.com/armbian/build
BUILD_REPOSITORY_COMMIT=4a0da762d-dirty
DISTRIBUTION_CODENAME=buster
DISTRIBUTION_STATUS=supported
VERSION=21.08.6
LINUXFAMILY=meson64
ARCH=arm64
IMAGE_TYPE=stable
BOARD_TYPE=conf
INITRD_ARCH=arm64
KERNEL_IMAGE_TYPE=Image
IMAGE_UUID=d4c7f3cf-d9ba-4c54-8922-6eac7f5061e0
user@xxx:~$ cat /etc/armbian-release
# PLEASE DO NOT EDIT THIS FILE
BOARD=odroidc2
BOARD_NAME="Odroid C2"
BOARDFAMILY=meson-gxbb
BUILD_REPOSITORY_URL=https://github.com/armbian/build
BUILD_REPOSITORY_COMMIT=92a1c729d-dirty
VERSION=22.02.1
LINUXFAMILY=meson64
ARCH=arm64
IMAGE_TYPE=stable
BOARD_TYPE=csc
INITRD_ARCH=arm64
KERNEL_IMAGE_TYPE=Image
BRANCH=current
user@xxx:~$

 

Link to comment
Share on other sites

After a confirmation with other user in the dietpi fork, in Odroid C2, the reboot works for him and this this kernel only if the emmc memory is used, if the same iso is installed in the sd card, then the reboot is not working having the same problem I have. Blacki2 are you using emmc or microSD card? @blacki2 

Link to comment
Share on other sites

Am 17.4.2022 um 19:36 schrieb yandritos:

Blacki2 are you using emmc or microSD card? @blacki2 

 

I am using emmc, too. I will test with sdcard and report back.

 

Edit1:

So I did some more testing.

 

First, I tried Armbian_22.02.1_Odroidc2_bullseye_current_5.10.102.img on microSD card.

 

Cold boot Armbian_22.02.1_Odroidc2_bullseye_current_5.10.102.img on microSD:

¦GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0;
TE: 198651
no sdio debug board detected

BL2 Built : 11:44:26, Nov 25 2015.
gxb gfb13a3b-c2 - jcao@wonton

Board ID = 8
set vcck to 1100 mv
set vddee to 1050 mv
CPU clk: 1536MHz
DDR channel setting: DDR0 Rank0+1 same
DDR0: 2048MB(auto) @ 912MHz(2T)-13
DataBus test pass!
AddrBus test pass!
Load fip header from SD, src: 0x0000c200, des: 0x01400000, size: 0x000000b0
Load bl30 from SD, src: 0x00010200, des: 0x01000000, size: 0x00009ef0
Sending bl30........................................OK.
Run bl30...
Load bl301 from SD, src: 0x0001c200, des: 0x01000000, size: 0x000018c0
Wait bl30...Done
Sending bl301.......OK.
Run bl301...
D, src: 0x00020200, des: 0x10100000, size: 0x00011130


--- UART initialized after reboot ---
[Reset cause: unknown]
[Image: unknown, amlogic_v1.1.3046-00db630-dirty 2016-08-31 09:24:14 tao.zeng@droid04]
bl30: check_permit, count is 1
bl30: check_permit: ok!
chipid: eLoad bl33 from SD, src: 0x00034200, des: 0x01000000, size: 0x000a21f0
f be ad de d f0 ad ba ef be ad de not ES chip
[0.313482 Inits done]
secure task start!
high task start!
low task start!
NOTICE:  BL3-1: v1.0(debug):4d2e34d
NOTICE:  BL3-1: Built : 17:08:35, Oct 29 2015
INFO:    BL3-1: Initializing runtime services
INFO:    BL3-1: Preparing for EL3 exit to normal world
INFO:    BL3-1: Next image address = 0x1000000
INFO:    BL3-1: Next image spsr = 0x3c9


U-Boot 2022.01-armbian (Feb 27 2022 - 08:49:30 +0000) odroid-c2

Model: Hardkernel ODROID-C2
SoC:   Amlogic Meson GXBB (S905) Revision 1f:c (0:1)
DRAM:  2 GiB
MMC:   mmc@72000: 0, mmc@74000: 1
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@c9410000
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
7895 bytes read in 2 ms (3.8 MiB/s)
## Executing script at 08000000
U-boot default fdtfile: amlogic/meson-gxbb-odroidc2.dtb
Current variant:
161 bytes read in 4 ms (39.1 KiB/s)
Current fdtfile after armbianEnv: amlogic/meson-gxbb-odroidc2.dtb
Mainline bootargs: root=UUID=df8d1a3e-5538-4f05-a7a5-03c785899e12 rootwait rootfstype=ext4 console=ttyAML0,115200 console=tty1 consoleblank=0 coherent_pool=2M loglevel=1 ubootpart=26fc0000-01 libata.force=noncq usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u   cgroup_enable=memory swapaccount=1
13819466 bytes read in 589 ms (22.4 MiB/s)
26329600 bytes read in 1119 ms (22.4 MiB/s)
38969 bytes read in 7 ms (5.3 MiB/s)
232 bytes read in 3 ms (75.2 KiB/s)
Applying kernel provided DT fixup script (meson-fixup.scr)
## Executing script at 32000000
## Loading init Ramdisk from Legacy Image at 13000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    13819402 Bytes = 13.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 04080000
   Booting using the fdt blob at 0x4080000
   Loading Ramdisk to 7b21c000, end 7bf49e0a ... OK
   Loading Device Tree to 000000007b1aa000, end 000000007b21bfff ... OK

Starting kernel ...


Armbian 22.02.1 Bullseye ttyAML0

odroidc2 login:

 

Reboot Armbian_22.02.1_Odroidc2_bullseye_current_5.10.102.img on microSD:

root@odroidc2:~# init 6
[  146.931479] reboot: Restarting system
INFO:    PSCI Affinity Map:
INFO:      AffInst: Level 0, MPID 0x0, State ON
INFO:      AffInst: Level 0, MPID 0x1, State ON
INFO:      AffInst: Level 0, MPID 0x2, State ON
INFO:      AffInst: Level 0, MPID 0x3, State ON
bl31 reb¦GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:800;USB:8;LOOP:1;EMMC:800;NAND:81;SD:800;USB:8;LOOP:2;EMMC:800;NAND:81;SD:800;USB:8;LOOP:3;EMMC:800;NAND:81;SD:800;USB:8;LOOP:4;EMMC:800;NAND:81;SD:800;USB:8;LOOP:5;EMMC:800;NAND:81;SD:800;USB:8;LOOP:6;EMMC:800;NAND:81;SD:800;USB:8;LOOP:7;EMMC:800;NAND:81;SD:800;USB:8;LOOP:8;EMMC:800;NAND:81;SD:800;USB:8;LOOP:9;EMMC:800;NAND:81;SD:800;USB:8;

 

Then, I tried edge image on microSD.

 

Cold boot Armbian_22.02.1_Odroidc2_jammy_edge_5.15.25.img on microSD:

¦GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0;
TE: 196098
no sdio debug board detected

BL2 Built : 11:44:26, Nov 25 2015.
gxb gfb13a3b-c2 - jcao@wonton

Board ID = 8
set vcck to 1100 mv
set vddee to 1050 mv
CPU clk: 1536MHz
DDR channel setting: DDR0 Rank0+1 same
DDR0: 2048MB(auto) @ 912MHz(2T)-13
DataBus test pass!
AddrBus test pass!
Load fip header from SD, src: 0x0000c200, des: 0x01400000, size: 0x000000b0
Load bl30 from SD, src: 0x00010200, des: 0x01000000, size: 0x00009ef0
Sending bl30........................................OK.
Run bl30...
Load bl301 from SD, src: 0x0001c200, des: 0x01000000, size: 0x000018c0
Wait bl30...Done
Sending bl301.......OK.
Run bl301...
31 from SD, src: 0x00020200, des: 0x10100000, size: 0x00011130


--- UART initialized after reboot ---
[Reset cause: unknown]
[Image: unknown, amlogic_v1.1.3046-00db630-dirty 2016-08-31 09:24:14 tao.zeng@droid04]
bl30: check_permit, count is 1
bl30: check_permit: ok!
chipid: eLoad bl33 from SD, src: 0x00034200, des: 0x01000000, size: 0x000a21f0
f be ad de d f0 ad ba ef be ad de not ES chip
[0.310848 Inits done]
secure task start!
high task start!
low task start!
NOTICE:  BL3-1: v1.0(debug):4d2e34d
NOTICE:  BL3-1: Built : 17:08:35, Oct 29 2015
INFO:    BL3-1: Initializing runtime services
INFO:    BL3-1: Preparing for EL3 exit to normal world
INFO:    BL3-1: Next image address = 0x1000000
INFO:    BL3-1: Next image spsr = 0x3c9


U-Boot 2022.01-armbian (Feb 27 2022 - 08:43:53 +0000) odroid-c2

Model: Hardkernel ODROID-C2
SoC:   Amlogic Meson GXBB (S905) Revision 1f:c (0:1)
DRAM:  2 GiB
MMC:   mmc@72000: 0, mmc@74000: 1
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@c9410000
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
7895 bytes read in 2 ms (3.8 MiB/s)
## Executing script at 08000000
U-boot default fdtfile: amlogic/meson-gxbb-odroidc2.dtb
Current variant:
161 bytes read in 5 ms (31.3 KiB/s)
Current fdtfile after armbianEnv: amlogic/meson-gxbb-odroidc2.dtb
Mainline bootargs: root=UUID=4153ba96-655a-468e-a82e-11622ce8c4f1 rootwait rootfstype=ext4 console=ttyAML0,115200 console=tty1 consoleblank=0 coherent_pool=2M loglevel=1 ubootpart=86a00000-01 libata.force=noncq usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u   cgroup_enable=memory swapaccount=1
17335879 bytes read in 737 ms (22.4 MiB/s)
26003968 bytes read in 1107 ms (22.4 MiB/s)
39319 bytes read in 5 ms (7.5 MiB/s)
232 bytes read in 3 ms (75.2 KiB/s)
Applying kernel provided DT fixup script (meson-fixup.scr)
## Executing script at 32000000
## Loading init Ramdisk from Legacy Image at 13000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    17335815 Bytes = 16.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 04080000
   Booting using the fdt blob at 0x4080000
   Loading Ramdisk to 7aec1000, end 7bf49607 ... OK
   Loading Device Tree to 000000007ae4f000, end 000000007aec0fff ... OK

Starting kernel ...

[    5.344802] lima d00c0000.gpu: dev_pm_opp_set_regulators: no regulator (mali) found: -19
[    5.551565] debugfs: Directory 'c1105400.audio-controller' with parent 'ODROID-C2' already present!

Armbian 22.02.1 Jammy ttyAML0

odroidc2 login:

 

Reboot Armbian_22.02.1_Odroidc2_jammy_edge_5.15.25.img on microSD:

root@odroidc2:~# init 6
[  158.394475] watchdog: watchdog0: watchdog did not stop!
[  159.181652] reboot: Restarting system
INFO:    PSCI Affinity Map:
INFO:      AffInst: Level 0, MPID 0x0, State ON
INFO:      AffInst: Level 0, MPID 0x1, State ON
INFO:      AffInst: Level 0, MPID 0x2, State ON
INFO:      AffInst: Level 0, MPID 0x3, State ON
bl31 reb¦GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:800;USB:8;LOOP:1;EMMC:800;NAND:81;SD:800;USB:8;LOOP:2;EMMC:800;NAND:81;SD:800;USB:8;

 

The same problem occurs on older image (also tested Armbian_21.08.6_Odroidc2_bullseye_current_5.10.81.img).

 

Then I tested cold boot of my eMMC installation:

¦GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:0;
TE: 107815
no sdio debug board detected

BL2 Built : 11:44:26, Nov 25 2015.
gxb gfb13a3b-c2 - jcao@wonton

Board ID = 8
set vcck to 1100 mv
set vddee to 1050 mv
CPU clk: 1536MHz
DDR channel setting: DDR0 Rank0+1 same
DDR0: 2048MB(auto) @ 912MHz(2T)-13
DataBus test pass!
AddrBus test pass!
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x000000b0
Load bl30 from eMMC, src: 0x00010200, des: 0x01000000, size: 0x00009ef0
Sending bl30........................................OK.
Run bl30...
Load bl301 from eMMC, src: 0x0001c200, des: 0x01000000, size: 0x000018c0
Wait bl30...Done
Sending bl301.......OK.
Run bl301...
rom eMMC, src: 0x00020200, des: 0x10100000, size: 0x00011130


--- UART initialized after reboot ---
[Reset cause: unknown]
[Image: unknown, amlogic_v1.1.3046-00db630-dirty 2016-08-31 09:24:14 tao.zeng@droid04]
bl30: check_permit, count is 1
bl30: check_permit: ok!
chipid: ef Load bl33 from eMMC, src: 0x00034200, des: 0x01000000, size: 0x000a1d50
be ad de d f0 ad ba ef be ad de not ES chip
[0.223103 Inits done]
secure task start!
high task start!
low task start!
NOTICE:  BL3-1: v1.0(debug):4d2e34d
NOTICE:  BL3-1: Built : 17:08:35, Oct 29 2015
INFO:    BL3-1: Initializing runtime services
INFO:    BL3-1: Preparing for EL3 exit to normal world
INFO:    BL3-1: Next image address = 0x1000000
INFO:    BL3-1: Next image spsr = 0x3c9


U-Boot 2021.07-armbian (Nov 22 2021 - 11:48:10 +0000) odroid-c2

Model: Hardkernel ODROID-C2
SoC:   Amlogic Meson GXBB (S905) Revision 1f:c (0:1)
DRAM:  2 GiB
MMC:   mmc@72000: 0, mmc@74000: 1
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@c9410000
Hit any key to stop autoboot:  0
Card did not respond to voltage select! : -110
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
7895 bytes read in 1 ms (7.5 MiB/s)
## Executing script at 08000000
U-boot default fdtfile: amlogic/meson-gxbb-odroidc2.dtb
Current variant:
177 bytes read in 1 ms (172.9 KiB/s)
Current fdtfile after armbianEnv: amlogic/meson-gxbb-odroidc2.dtb
Mainline bootargs: root=UUID=3a21733d-df83-4e10-b6d2-be83306f3d3f rootwait rootfstype=ext4 console=ttyAML0,115200 console=tty1 consoleblank=0 coherent_pool=2M loglevel=1 ubootpart=1aca0000-01 libata.force=noncq usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u,0x1058:0x1130:u   cgroup_enable=memory swapaccount=1
13885905 bytes read in 311 ms (42.6 MiB/s)
26329600 bytes read in 589 ms (42.6 MiB/s)
38969 bytes read in 4 ms (9.3 MiB/s)
232 bytes read in 3 ms (75.2 KiB/s)
Applying kernel provided DT fixup script (meson-fixup.scr)
## Executing script at 32000000
## Loading init Ramdisk from Legacy Image at 13000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    13885841 Bytes = 13.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 04080000
   Booting using the fdt blob at 0x4080000
   Loading Ramdisk to 7b20f000, end 7bf4d191 ... OK
   Loading Device Tree to 000000007b19d000, end 000000007b20efff ... OK

Starting kernel ...


Armbian 21.08.6 Buster ttyAML0

odroidc2 login: 

 

And finally reboot of my eMMC installation:

root@odroidc2:~# init 6
[  200.900452] reboot: Restarting system
INFO:    PSCI Affinity Map:
INFO:      AffInst: Level 0, MPID 0x0, State ON
INFO:      AffInst: Level 0, MPID 0x1, State ON
INFO:      AffInst: Level 0, MPID 0x2, State ON
INFO:      AffInst: Level 0, MPID 0x3, State ON
bl31 reb¦GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:0;
TE: 97873
no sdio debug board detected

BL2 Built : 11:44:26, Nov 25 2015.
gxb gfb13a3b-c2 - jcao@wonton

Board ID = 8
set vcck to 1100 mv
set vddee to 1050 mv
CPU clk: 1536MHz
DDR channel setting: DDR0 Rank0+1 same
DDR0: 2048MB(auto) @ 912MHz(2T)-13
DataBus test pass!
AddrBus test pass!
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x000000b0
Load bl30 from eMMC, src: 0x00010200, des: 0x01000000, size: 0x00009ef0
Sending bl30........................................OK.
Run bl30...
Load bl301 from eMMC, src: 0x0001c200, des: 0x01000000, size: 0x000018c0
Wait bl30...Done
Sending bl301.......OK.
Run bl301...
 eMMC, src: 0x00020200, des: 0x10100000, size: 0x00011130


--- UART initialized after reboot ---
[Reset cause: unknown]
[Image: unknown, amlogic_v1.1.3046-00db630-dirty 2016-08-31 09:24:14 tao.zeng@droid04]
bl30: check_permit, count is 1
bl30: check_permit: ok!
chipid: ef Load bl33 from eMMC, src: 0x00034200, des: 0x01000000, size: 0x000a1d50
be ad de d f0 ad ba ef be ad de not ES chip
[0.213075 Inits done]
secure task start!
high task start!
low task start!
NOTICE:  BL3-1: v1.0(debug):4d2e34d
NOTICE:  BL3-1: Built : 17:08:35, Oct 29 2015
INFO:    BL3-1: Initializing runtime services
INFO:    BL3-1: Preparing for EL3 exit to normal world
INFO:    BL3-1: Next image address = 0x1000000
INFO:    BL3-1: Next image spsr = 0x3c9


U-Boot 2021.07-armbian (Nov 22 2021 - 11:48:10 +0000) odroid-c2

Model: Hardkernel ODROID-C2
SoC:   Amlogic Meson GXBB (S905) Revision 1f:c (0:1)
DRAM:  2 GiB
MMC:   mmc@72000: 0, mmc@74000: 1
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@c9410000
Hit any key to stop autoboot:  0
Card did not respond to voltage select! : -110
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
7895 bytes read in 1 ms (7.5 MiB/s)
## Executing script at 08000000
U-boot default fdtfile: amlogic/meson-gxbb-odroidc2.dtb
Current variant:
177 bytes read in 1 ms (172.9 KiB/s)
Current fdtfile after armbianEnv: amlogic/meson-gxbb-odroidc2.dtb
Mainline bootargs: root=UUID=3a21733d-df83-4e10-b6d2-be83306f3d3f rootwait rootfstype=ext4 console=ttyAML0,115200 console=tty1 consoleblank=0 coherent_pool=2M loglevel=1 ubootpart=1aca0000-01 libata.force=noncq usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u,0x1058:0x1130:u   cgroup_enable=memory swapaccount=1
13885905 bytes read in 311 ms (42.6 MiB/s)
26329600 bytes read in 589 ms (42.6 MiB/s)
38969 bytes read in 4 ms (9.3 MiB/s)
232 bytes read in 2 ms (113.3 KiB/s)
Applying kernel provided DT fixup script (meson-fixup.scr)
## Executing script at 32000000
## Loading init Ramdisk from Legacy Image at 13000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    13885841 Bytes = 13.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 04080000
   Booting using the fdt blob at 0x4080000
   Loading Ramdisk to 7b20f000, end 7bf4d191 ... OK
   Loading Device Tree to 000000007b19d000, end 000000007b20efff ... OK

Starting kernel ...


Armbian 21.08.6 Buster ttyAML0

odroidc2 login:

 

Difference I see between microSD cold boot vs. microSD reboot:

GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0;

vs.

GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:800;USB:8;

 

Link to comment
Share on other sites

Hello!

I watch this thread since a year, so far no update and the issue still exists in Bookworm for a Odroid-C2  booting into the current bookworm image on MicroSD ( as of writing this, that's Armbian 23.8 Bookworm ).

Is there any chance of this being solved? I tried with a Kingston (32GB), an Intenso (8GB), a Sandisk (16GB) and a Toshiba (64GB) MicoSD card.

If this cannot be solved...:

Any recommends where to get a Toshiba or Sandisk eMMC module?

I wasn't very lucky with the Odroid ones for my N2 and N2+, but didn't find any other compatible eMMC modules so far.

 

And I'm not planning on soldering some BGA chips out and in.

X(

 

 

Link to comment
Share on other sites

  • Solution
root@odroid:~# mount |grep mmc
/dev/mmcblk1p1 on / type ext4 (ro,noatime)
/dev/mmcblk0p1 on /data type ext4 (ro,noatime)
root@odroid:~# reboot 
Failed to connect to bus: No such file or directory
root@odroid:~# client_loop: send disconnect: Broken pipe
hje@prime:~$ 
hje@prime:~$ 
hje@prime:~$ 
hje@prime:~$ 
hje@prime:~$ ssh root@odroid
  ___      _           _     _    ____ ____  
 / _ \  __| |_ __ ___ (_) __| |  / ___|___ \ 
| | | |/ _` | '__/ _ \| |/ _` | | |     __) |
| |_| | (_| | | | (_) | | (_| | | |___ / __/ 
 \___/ \__,_|_|  \___/|_|\__,_|  \____|_____|
                                             
Welcome to Armbian 24.2.1 Bookworm with Linux 6.6.16-current-meson64

System load:   46%           	Up time:       0 min	
Memory usage:  7% of 1.82G  	IP:	       192.168.25.252
CPU temp:      28°C           	Usage of /:    66% of 3.0G 

 

fresh installation on emmc, reboot works fine.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines