Jump to content
  • 0

Issue with eMMC + NVMe


Константин Литвинов
 Share

Question

Hello,

Devices: RockPi 4b v1.5 + remotable eMMC + NVMe KingSpec M.2 NMVe SSD NE 2280 512 GB

I am using instructions to erase SPI https://wiki.radxa.com/Rockpi4/dev/spi-install

$ sudo rkdeveloptool ld
DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=103 Maskrom

$ sudo rkdeveloptool db ./rk3399_loader_spinor_v1.20.126.bin
Downloading bootloader succeeded.

$ dd if=/dev/zero of=./zero.img bs=1M count=4
4+0 records in
4+0 records out
4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.0160027 s, 262 MB/s

$ sudo rkdeveloptool wl 0 ./zero.img
Write LBA from file (100%)

$ sudo rkdeveloptool td
Test Device OK.

$ sudo rkdeveloptool rd
Reset Device OK.

After that, insert eMMC and use instruction to write image to eMMChttps://wiki.radxa.com/Rockpi4/dev/usb-install

$ sudo rkdeveloptool ld
DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=103 Maskrom

$ sudo rkdeveloptool db ./rk3399_loader_v1.20.119.bin
Downloading bootloader succeeded.

$ sudo rkdeveloptool wl 0 ./Armbian_22.08.8_Rockpi-4b_bullseye_current_5.15.76.img
Write LBA from file (100%)

$ sudo rkdeveloptool rd
Reset Device OK.

After reboot device work fine.

But if I insert NVMe the system not booting, blue led just blinking and that all.

I tryed several images:

Armbian_22.11.0-trunk_Rockpi-4b_bullseye_current_5.15.76_minimal.img

Armbian_22.08.8_Rockpi-4b_bullseye_current_5.15.76.img

rockpi-4b-debian-bullseye-xfce4-arm64-20221101-0519-gpt.img

rockpi-4b-debian-buster-xfce4-arm64-20220401-0335-gpt.img

The main goal is system on eMMC and stored data on NVMe (like mini NAS)

Also if I use armbian-install have the same issue.


Any help with it ?

Link to comment
Share on other sites

9 answers to this question

Recommended Posts

Search Before Posting!

  • 0
On 11/23/2022 at 2:45 PM, Константин Литвинов said:

The main goal is system on eMMC and stored data on NVMe (like mini NAS)


It is difficult to say what is wrong, but if you are using Armbian you should follow Armbian documentation, not something in between. It can be very different. Vendors are usually using binary boot loaders and proprietary tools they got from chip vendor, while we use open source tools we and community developed.

After you erase or disable (connecting pin 23 and 25) SPI, you don't need to do anything else then booting from SD card and using standard armbian-install utility to flash to eMMC boot/eMMC root or eMMC boot/NVME root. We invested a lot of efforts to keep the same install procedure on very different methods ... If there are any hacks needed, they are exposed at download pages https://www.armbian.com/rockpi4/ 

 

If you have eMMC to SD card adaptor, that you flash directly and it should work. But like I said, without logs we are in the dark ...

Link to comment
Share on other sites

  • 0

The method used to transfer an image byte by byte to a target device is not important. It does not change the function of the transferred code as long as no transmission errors occur. Due to the detailed description of the procedure and the confirmation

On 11/23/2022 at 2:45 PM, Константин Литвинов said:

After reboot device work fine.

 that the system is working, it is proven that nothing has been done wrong so far. The problem only arises when the NVME device comes into play. The use of different images also proves that there seems to be a fundamental issue that seems worth investigating further. But a basic prerequisite are meaningful logs, and without them it is hopeless from the beginning. The excuse of not having a suitable USB serial adapter available to provide logs is mood. Every reasonably assorted electronics shop offers these for little money. Choose whatever your host system with which you want to use the adapter supports, make sure that the operating voltage of the RX/TX lines matches that of the SBC and the adapter supports a baud rate of 1500000 and you are ready to go. Tinkering with SBCs sooner or later requires access to the serial console for one reason or another. If you don't want that and have a turnkey system, an SBC isn't the right choice.

Link to comment
Share on other sites

  • 0
4 часа назад, usual user сказал:

Every reasonably assorted electronics shop offers these for little money.


I live in a small town in a not very normal country, so unfortunately I don't have the opportunity to go to any store and buy this cable. As well as ordering it inside the country via the Internet. So for now, I'll be waiting for him from China.
Sorry for that (

Link to comment
Share on other sites

  • 0
18 часов назад, Igor сказал:

But like I said, without logs we are in the dark


Thanks for your reply. I understand the importance of console logs, but unfortunately I can't provide them yet... But

I continue research until cable come to me. I tried the next solutions:
Fully erase eMMC and NVMe

1. Use Armbian_22.08.8_Rockpi-4b_bullseye_current_5.15.76.img - write it to uSD; erase SPI, eMMC and NVMe
2. Remove NVMe and start boot from uSD
3. Install Armbian to eMMC, for file systen use btrfs (not sure if it matters)
4. Configure /boot/armbianEnv.txt to verbosity=7 
5. Reboot system and all work fine.
6. Power off the system from console - sudo poweroff.

Insert empty NVMe and try to start bourd: 
The board looks like start but start not complitle - blue lite just blinken, no HDMI output, keyboard like work (NumLock on/off)
So I remove power and remove NVMe and start system again.
After that I try to reserch logs 'journalctl -b' and find next issue:
```
Nov 25 10:44:14 rockpi-4b kernel: rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
Nov 25 10:44:14 rockpi-4b kernel: rockchip-pcie: probe of f8000000.pcie failed with error -110
```

Going to search in internet and find next MR: https://github.com/armbian/build/pull/4308
As I understand it's will applied only in 6.0.x so I try start with Armbian_22.11.0-trunk_Rockpi-4b_sid_edge_6.0.9.img
- boot from uSD with empty eMMC + empty NVMe

fdisk -l output: 

Disk /dev/mmcblk0: 59.48 GiB, 63864569856 bytes, 124735488 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x08f2b9a2

Device         Boot Start       End   Sectors  Size Id Type
/dev/mmcblk0p1      32768 123469824 123437057 58.9G 83 Linux


Disk /dev/mmcblk1: 57.62 GiB, 61865984000 bytes, 120832000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk1boot0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk1boot1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: NE-512                                  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

 

So we can figure out the system is working and all devices are working too. A trable in detect of NVMe during boot. 

I was happy before I try to reboot. Then system rebooting I have the same issue - blue light just blinking, no HDMI output, keyboard like work (NumLock on/off)

Any new ideas?

Link to comment
Share on other sites

  • 0
39 minutes ago, Константин Литвинов said:

Any new ideas?

 

We came this far, we tried with workaround, it doesn't work well, but from here on a slow and painful research needs to be done. We have done our part, more we can't afford. 

Link to comment
Share on other sites

  • 0
4 часа назад, Igor сказал:

We came this far, we tried with workaround, it doesn't work well, but from here on a slow and painful research needs to be done. We have done our part, more we can't afford.


I didn't quite understand your answer. Will the console logs help or is this sufficient research and it 's just unclear what to do next ?

Link to comment
Share on other sites

  • 0
20 minutes ago, Константин Литвинов said:

Will the console logs help


No, problem is identified, but we don't have resources / money to proceed from here. For us, this is 24/7, for you - when something breaks down. 

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
Answer this question...

×   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...
 Share

×
×
  • Create New...