After reboot, everything ok, booted sucessfully. Im accessing the system via DEBUG UART.
After some seconds, system reboots out of no where (many logs about “link up” and down)
A603 seems a custom carrier board from SeeedStudio.
I think there may still be some custom design on your board and you(Or your vendor) have to customize them in BSP package before flash.
It may be caused from that NVMe SSD is not recognized on PCIe bus on your custom carrier board.
Sorry that we don’t support for yocto project. You may also ask for the 3rd-party vendor.
@KevinFFF Hi. I think the issue is resolved now, we might thing it was some sort of short circuit while we were moving things around, since the problem does not happen anymore. We have a different problem now which is, when booting with the ethernet cable in, we get the following errors:
I> CPUBL-params @ 0x472000000
I> Task: Ratchet update (0x5002a194)
W> Skip ratchet update - OPTIN fuse not set
I> Task: Prepare eeprom data (0x50019a78)
E> I2C: Timeout while polling for bus clear. Last value 0x00000000.
E> I2C: Failed to clear bus for instance 0.
E> I2C: Failed to clear bus for instance 0.
E> I2C_DEV: Failed to initialize instance 0.
E> eeprom: Can't get handle to eeprom device @160
C> Task 0x0 failed (err: 0x1414032a)
E> Top caller module: EEPROM, error module: EEPROM, reason: 0x2a, aux_info: 0x03
I> Busy Spin
I already changed cvb_eeprom_read_size to 0. I think this is a different issue.
However, if we boot without ethernet cable, it boots OK (but we are unable to use DEBUG ART for some reason, the input is not getting to the system, only output works in picocom)
EEPROM is optional on the custom carrier board.
If you don’t have it on your board, please refer to the following instruction to modify device tree. EEPROM Modifications
