Hi all, I have a new HoneyComb LX2 board that I don’t know how to troubleshoot because I simply cannot get any visual output from it.
I have followed the instructions on the quick start and serial connection docs. I tried flashing both the UEFI and U-boot images to an SD card. The boot select switches look right (off,on,on,on,off). My memory stick is a 32GB Micron MTA18ASF4G72HZ-3G2B1 with ECC.
I’ve tried multiple different machines and OS’s to get a serial connection, and in all cases, the device simply is not created. Nothing shows up via udev or dmesg either, as if no cable was even plugged in. I believe at this point that it’s the board (or how I am using it), not the laptop.
The hardware behaves slightly differently depending on whether I flashed UEFI or U-boot.
With U-boot, the Ethernet light flashes green (regardless of whether anything is plugged into it) and the CPU fan oscillates.
With UEFI, the Ethernet light is a solid green (again, even with nothing plugged in) and the fan is a constant high speed. If I plug in a bootable USB thumb drive, the light on that flashes as if the board is trying to boot from it – but still no console detected.
In the end this machine will not use a GPU, but I plugged one in anyway as a last resort. No output whatsoever, nothing detected by the monitor.
I am seeing the same issue with 2x brand new SoMs and 2x brand new ClearFog carriers.
There is no bootloader output from the serial console.
The fan speed oscillates
RJ45 Ethernet jack LED blinks
All recent pre-built images and images we’ve built using the lx2160a_build project have this issue and do not boot. Some of the older (2020) images seem to operate correctly.
I’ve tried with two configurations of supported / tested memory.
MTA4ATF1G64HZ-3G2E2
HX432S20IBK2/32
Older images (e.g. 6a1498d) do seem to work so it appears that something has broken in later images
Womble - if the fan oscillates when you try and boot from the sdcard, could it be that it was not flashed properly? When I’ve had what you are describing, it was due to trying to follow Solid-run’s flashing instructions. balena etcher was much easier.
We are looking into the reports regarding issues with the serial console. There have been no design changes regarding the hardware or software an recent releases or production runs. I will update threads as soon as we have more information.
I’m very confident that the issue is with the images rather than how I’m flashing them. All images before ed87dd1 boot normally. ed87dd1 and all subsequent images do not work on my hardware and show the oscillating fan symptom with no serial output. It would appear that a breaking change was introduced after 24990d3 (the last commit hash that works) which is causing the images not to boot on my hardware.
We’ve been having issues with the serial console as well. Re-powering the ClearFog board with the FTDI uart connected causes the UART to stop working with “ftdi_sio ttyUSB0: failed to get modem status: -71” repeated on my laptop dmesg output. This can be resolved by re-plugging the USB cable. Trying various USB cables didn’t fix this for me. The console issue seems to occur when the main board power is applied after the USB cable is connected. It doesn’t happen when the board is reset using the reset button.
I too am also investigating why my new CF board is not booting with latest the LSDK-21.08 (ed87dd1 & c0eea64). Yet if I switch to LSDK-20.12 all works fine (bc46e34 and back).
I suspect the problem lies in ATF as building ATF with DEBUG=1 LOG_LEVEL=50 I get the following output on the boot console
VERBOSE: Enable cluster time base
VERBOSE: NUM of cluster = 0x8, Cores per cluster = 0x2
INFO: Index = 0 with loc_nod=13 and input nod=13
VERBOSE: Value is successfully read from address 0x4080008.
INFO: Index = 0 with loc_nod=13 and input nod=13
VERBOSE: Value is successfully written at address 0x4080008.
INFO: Index = 0 with loc_nod=13 and input nod=30
INFO: Index = 1 with loc_nod=30 and input nod=30
VERBOSE: Value is successfully read from address 0x4090008.
INFO: Index = 0 with loc_nod=13 and input nod=30
INFO: Index = 1 with loc_nod=30 and input nod=30
VERBOSE: Value is successfully written at address 0x4090008.
INFO: Index = 0 with loc_nod=13 and input nod=13
VERBOSE: Value is successfully read from address 0x4080500.
INFO: Index = 0 with loc_nod=13 and input nod=13
VERBOSE: Value is successfully written at address 0x4080500.
INFO: Index = 0 with loc_nod=13 and input nod=30
INFO: Index = 1 with loc_nod=30 and input nod=30
VERBOSE: Value is successfully read from address 0x4090500.
INFO: Index = 0 with loc_nod=13 and input nod=30
INFO: Index = 1 with loc_nod=30 and input nod=30
VERBOSE: Value is successfully written at address 0x4090500.
INFO: Index = 0 with loc_nod=13 and input nod=13
VERBOSE: Value is successfully read from address 0x4080000.
INFO: Index = 0 with loc_nod=13 and input nod=13
VERBOSE: Value is successfully written at address 0x4080000.
INFO: Index = 0 with loc_nod=13 and input nod=30
INFO: Index = 1 with loc_nod=30 and input nod=30
VERBOSE: Value is successfully read from address 0x4090000.
INFO: Index = 0 with loc_nod=13 and input nod=30
INFO: Index = 1 with loc_nod=30 and input nod=30
VERBOSE: Value is successfully written at address 0x4090000.
INFO: Index = 0 with loc_nod=13 and input nod=13
VERBOSE: Value is successfully read from address 0x4080500.
INFO: Index = 0 with loc_nod=13 and input nod=13
VERBOSE: Value is successfully written at address 0x4080500.
INFO: Index = 0 with loc_nod=13 and input nod=30
INFO: Index = 1 with loc_nod=30 and input nod=30
VERBOSE: Value is successfully read from address 0x4090500.
INFO: Index = 0 with loc_nod=13 and input nod=30
VERBOSE: Enable cluster time base
VERBOSE: NUM of cluster = 0x8, Cores per cluster = 0x2
INFO: Index = 0 with loc_nod=13 and input nod=13
VERBOSE: Value is successfully read from address 0x4080008.
INFO: Index = 0 with loc_nod=13 and input nod=13
VERBOSE: Value is successfully written at address 0x4080008.
INFO: Index = 0 with loc_nod=13 and input nod=30
INFO: Index = 1 with loc_nod=30 and input nod=30
VERBOSE: Value is successfully read from address 0x4090008.
INFO: Index = 0 with loc_nod=13 and input nod=30
INFO: Index = 1 with loc_nod=30 and input nod=30
VERBOSE: Value is successfully written at address 0x4090008.
INFO: Index = 0 with loc_nod=13 and input nod=13
VERBOSE: Value is successfully read from address 0x4080500.
INFO: Index = 0 with loc_nod=13 and input nod=13
VERBOSE: Value is successfully written at address 0x4080500.
INFO: Index = 0 with loc_nod=13 and input nod=30
INFO: Index = 1 with loc_nod=30 and input nod=30
VERBOSE: Value is successfully read from address 0x4090500.
INFO: Index = 0 with loc_nod=13 and input nod=30
INFO: Index = 1 with loc_nod=30 and input nod=30
VERBOSE: Value is successfully written at address 0x4090500.
INFO: Index = 0 with loc_nod=13 and input nod=13
VERBOSE: Value is successfully read from address 0x4080000.
INFO: Index = 0 with loc_nod=13 and input nod=13
VERBOSE: Value is successfully written at address 0x4080000.
INFO: Index = 0 with loc_nod=13 and input nod=30
INFO: Index = 1 with loc_nod=30 and input nod=30
VERBOSE: Value is successfully read from address 0x4090000.
INFO: Index = 0 with loc_nod=13 and input nod=30
INFO: Index = 1 with loc_nod=30 and input nod=30
VERBOSE: Value is successfully written at address 0x4090000.
INFO: Index = 0 with loc_nod=13 and input nod=13
VERBOSE: Value is successfully read from address 0x4080500.
INFO: Index = 0 with loc_nod=13 and input nod=13
VERBOSE: Value is successfully written at address 0x4080500.
INFO: Index = 0 with loc_nod=13 and input nod=30
INFO: Index = 1 with loc_nod=30 and input nod=30
VERBOSE: Value is successfully read from address 0x4090500.
INFO: Index = 0 with loc_nod=13 and input nod=30
INFO: Index = 1 with loc_nod=30 and input nod=30
VERBOSE: Value is successfully written at address 0x4090500.
INFO: Index = 0 with loc_nod=4 and input nod=17
INFO: Index = 1 with loc_nod=7 and input nod=17
INFO: Index = 2 with loc_nod=10 and input nod=17
INFO: Index = 3 with loc_nod=17 and input nod=17
VERBOSE: Value is successfully read from address 0x4910500.
INFO: Index = 0 with loc_nod=4 and input nod=17
INFO: Index = 1 with loc_nod=7 and input nod=17
INFO: Index = 2 with loc_nod=10 and input nod=17
INFO: Index = 3 with loc_nod=17 and input nod=17
VERBOSE: Value is successfully written at address 0x4910500.
INFO: RCW BOOT SRC is SD
INFO: SoC workaround for Errata A050426 was applied
INFO: SoC workaround for DDR Errata A011396 was applied
INFO: SoC workaround for DDR Errata A050450 was applied
INFO: SoC workaround for DDR Errata A050958 was applied
VERBOSE: Generic delay timer configured with mult=1 and div=25
INFO: RCW BOOT SRC is SD
INFO: esdhc_emmc_init
INFO: Card detected successfully
INFO: init done:
INFO: Flexspi driver: Version v1.0
INFO: Flexspi: Default MCR0 = 0xffff80c0, before reset
VERBOSE: Flexspi: Resetting controller…
INFO: Flexspi: After MCR0 = 0xffff0000,
VERBOSE: In func fspi_setup_LUT
VERBOSE: fspi_unlock_LUT 0x2
VERBOSE: fspi_unlock_LUT 0x2
VERBOSE: FSPI_NOR_CMD_READ_4B offset = 0x200
VERBOSE: FSPI_NOR_CMD_FASTREAD_4B offset = 0x260
VERBOSE: FSPI_NOR_CMD_PP_4B offset = 0x220
VERBOSE: FSPI_NOR_CMD_WREN offset = 0x210
VERBOSE: FSPI_NOR_CMD_SE_64K_4B offset = 0x230
VERBOSE: FSPI_NOR_CMD_SE_4K_4B offset = 0x270
VERBOSE: FSPI_NOR_CMD_BE offset = 0x250
VERBOSE: FSPI_NOR_CMD_RDSR offset = 0x240
VERBOSE: fspi_lock_LUT 0x2
VERBOSE: fspi_lock_LUT 0x1
INFO: Flexspi: Init done!!
VERBOSE: In func xspi_sector_erase
INFO: F_SECTOR_ERASE_SZ: 0x00020000, num_sector: 1
VERBOSE: In func xspi_wren Addr=0xc0000
VERBOSE: In func fspi_sec_er
INFO: In [fspi_sec_er][755] Erase address 0xc0000
VERBOSE: In func is_flash_busy
VERBOSE: In func is_flash_busy
VERBOSE: In func fspi_ahb_invalidate 270
VERBOSE: In func fspi_ahb_invalidate 276
INFO: Value of warm_reset flag = 0xff
INFO: Value of WDT flag = 0xff
VERBOSE: Memory seen by this BL image: 0x1800d000 - 0x1803b000
ERROR: mmap_add_region_check() failed. error -1
ASSERT: lib/xlat_tables_v2/xlat_tables_core.c:790:false
BACKTRACE: START: assert
0: EL3: 0x18019fa4
1: EL3: 0x1801d328
2: EL3: 0x1801c868
3: EL3: 0x1801bf30
4: EL3: 0x1801b9d0
5: EL3: 0x180195cc
6: EL3: 0x1800d0e0
BACKTRACE: END: assert
I am continuing to try and figure out the differences but thought I’d share my current status just in case it triggers something.
Interestingly with the about change to ATF I am seeing console output on minicom without having to disconnect, reconnect and reset the board after power is applied. But I am still getting these in the log
[Tue May 10 13:10:12 2022] usb 1-8.2: clear tt 1 (9301) error -71
[Tue May 10 13:10:12 2022] usb 1-8.2: clear tt 1 (9301) error -71
[Tue May 10 13:10:12 2022] usb 1-8.2: clear tt 1 (9301) error -71
[Tue May 10 13:10:12 2022] usb 1-8.2: clear tt 1 (9301) error -71
[Tue May 10 13:10:12 2022] usb 1-8.2: clear tt 1 (9301) error -71
[Tue May 10 13:10:12 2022] usb 1-8.2: clear tt 1 (9301) error -71
[Tue May 10 13:10:12 2022] usb 1-8.2: clear tt 1 (9301) error -71
