# HoneyComb LX2 no console or GPU output
**URL:** https://community.solid-run.com/t/honeycomb-lx2-no-console-or-gpu-output/310
**Category:** NXP LX2160
**Created:** [May 8, 2022, 11:34am UTC](https://community.solid-run.com/t/honeycomb-lx2-no-console-or-gpu-output/310 "2022-05-08T11:34:21Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@the\_n00b](https://community.solid-run.com/u/the_n00b)
#### Post date: [May 8, 2022, 11:34am UTC](https://community.solid-run.com/t/honeycomb-lx2-no-console-or-gpu-output/310/1 "2022-05-08T11:34:21Z")
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.
Suggestions? TIA!
---
### Author:  [@jnettlet](https://community.solid-run.com/u/jnettlet)
#### Post date: [May 9, 2022, 4:31am UTC](https://community.solid-run.com/t/honeycomb-lx2-no-console-or-gpu-output/310/2 "2022-05-09T04:31:30Z")
Have you tried a different USB cable? You should see the device detected in dmesg or via lsusb regardless if the board is booted or not.
---
### Author:  [@womble](https://community.solid-run.com/u/womble)
#### Post date: [May 9, 2022, 11:03am UTC](https://community.solid-run.com/t/honeycomb-lx2-no-console-or-gpu-output/310/3 "2022-05-09T11:03:03Z")
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
---
### Author:  [@wick](https://community.solid-run.com/u/wick)
#### Post date: [May 9, 2022, 1:40pm UTC](https://community.solid-run.com/t/honeycomb-lx2-no-console-or-gpu-output/310/4 "2022-05-09T13:40:21Z")
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](https://www.balena.io/etcher/) was much easier.
---
### Author:  [@jnettlet](https://community.solid-run.com/u/jnettlet)
#### Post date: [May 9, 2022, 1:42pm UTC](https://community.solid-run.com/t/honeycomb-lx2-no-console-or-gpu-output/310/5 "2022-05-09T13:42:52Z")
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.
---
### Author:  [@the\_n00b](https://community.solid-run.com/u/the_n00b)
#### Post date: [May 9, 2022, 3:13pm UTC](https://community.solid-run.com/t/honeycomb-lx2-no-console-or-gpu-output/310/6 "2022-05-09T15:13:24Z")
Well, _my_ issue was indeed a bad cable. Having tested two already, both of which worked fine for charging, I was skeptical… but there you go. 😅
FWIW I also confirmed @womble’s issue. The older 6a1498d image seems to work, with no fan oscillations or other weird stuff.
---
### Author:  [@womble](https://community.solid-run.com/u/womble)
#### Post date: [May 9, 2022, 4:06pm UTC](https://community.solid-run.com/t/honeycomb-lx2-no-console-or-gpu-output/310/7 "2022-05-09T16:06:50Z")
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.
---
### Author:  [@OfficerDribble](https://community.solid-run.com/u/OfficerDribble)
#### Post date: [May 10, 2022, 12:11pm UTC](https://community.solid-run.com/t/honeycomb-lx2-no-console-or-gpu-output/310/8 "2022-05-10T12:11:44Z")
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
The plot thickens.
---
### Author:  [@jnettlet](https://community.solid-run.com/u/jnettlet)
#### Post date: [May 11, 2022, 3:19pm UTC](https://community.solid-run.com/t/honeycomb-lx2-no-console-or-gpu-output/310/9 "2022-05-11T15:19:00Z")
I have diagnosed the issue and you can find the solution here.
> [@U-Boot (ATF) failure LDSK-21.08 on ClearFog LX2](https://community.solid-run.com/t/u-boot-atf-failure-ldsk-21-08-on-clearfog-lx2/316/7):
>
> I just did a fresh clone and test build and was unable to replicate the BL2 image bloat you were seeing. However on my test machine I found that this patch was causing my machine to not boot from the usdhc card. Can you try and revert this commit from your build/rcw and test the image again? lx2160acex7: mode 8: use external PLLs If you are still having the bloat issue I can also share my patch that switches to gcc-10
I will work with the team to get new images built by our CI.
---
### Author:  [@jnettlet](https://community.solid-run.com/u/jnettlet)
#### Post date: [May 11, 2022, 5:39pm UTC](https://community.solid-run.com/t/honeycomb-lx2-no-console-or-gpu-output/310/10 "2022-05-11T17:39:19Z")
The latest images at [SolidRun Images](https://images.solid-run.com/LX2k/lx2160a_build) have the offending commit reverted and should solve the reported images.