# LX2 honeycomb requires serial connection to boot, linux reboot fails

**URL:** <https://community.solid-run.com/t/lx2-honeycomb-requires-serial-connection-to-boot-linux-reboot-fails/224>\
**Category:** NXP LX2160\
**Created:** [January 19, 2022, 3:14pm UTC](https://community.solid-run.com/t/lx2-honeycomb-requires-serial-connection-to-boot-linux-reboot-fails/224 "2022-01-19T15:14:52Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![embeddedDeveloper](https://avatars.discourse-cdn.com/v4/letter/e/c4cdca/32.png) [@embeddedDeveloper](https://community.solid-run.com/u/embeddedDeveloper)\
**Post date:** [January 19, 2022, 3:14pm UTC](https://community.solid-run.com/t/lx2-honeycomb-requires-serial-connection-to-boot-linux-reboot-fails/224/1 "2022-01-19T15:14:52Z")

</div>

We have two LX2 honeycombs with 32 GB DDR2 3200 and 1 TB NVME M.2 in an NZXT case. I put the image lx2160acex7\_2000\_700\_3200\_8\_5\_2-bc46e34.img.xz on the micro-SD card and followed the instructions from " HoneyComb / ClearFog CX Installation and Tips" to flash the NVME M.2.

We are seeing two things on both LX2s:

1. Both require a serial connection to boot. Is this a configuration options somewhere?
2. Linux boots fine. The problem is when I issue a “reboot” from the Linux command line. The board fails to boot back into Linux (see output below). From a cold boot, the board boots fine.

[OK] Reached target Reboot.  
[235.273970] watchdog: watchdog0: watchdog did not stop!  
[236.371243] reboot: Restarting system  
NOTICE: BL2: v1.5(release):LSDK-20.12-8-g9115785  
NOTICE: BL2: Built : 19:24:37, Jun 15 2021  
NOTICE: UDIMM KHX3200C20S4/16GX  
ERROR: Read error = fffffffd  
ERROR: Failed to load 29 firmware.  
ERROR: Loading firmware failed (error code -2)  
ERROR: Calculating DDR PHY registers failed.  
PHY handshake timeout, ddr\_dsr2 = 0  
PHY handshake timeout, ddr\_dsr2 = 0

NOTICE: 32 GB DDR4, 64-bit, CL=20, ECC off, 256B, CS0+CS1  
ERROR: Read error = 1  
ERROR: BL2: Failed to load image (-2)  
Authentication failure

---

<div class="post-metadata">

**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\
**Post date:** [January 19, 2022, 3:23pm UTC](https://community.solid-run.com/t/lx2-honeycomb-requires-serial-connection-to-boot-linux-reboot-fails/224/2 "2022-01-19T15:23:48Z")

</div>

This looks like the uSDHC card is failing to reset properly on reboot. Can you try putting the firmware on a different uSDHC card?

---

<div class="post-metadata">

**Author:** ![embeddedDeveloper](https://avatars.discourse-cdn.com/v4/letter/e/c4cdca/32.png) [@embeddedDeveloper](https://community.solid-run.com/u/embeddedDeveloper)\
**Post date:** [January 19, 2022, 6:15pm UTC](https://community.solid-run.com/t/lx2-honeycomb-requires-serial-connection-to-boot-linux-reboot-fails/224/3 "2022-01-19T18:15:06Z")

</div>

I used a different uSDHC card and the linux “reboot” command works fine now. We purchased 2 of the following uSDHCs: SANDISK EDGE 16GB MICROSD CARD - A1 U1 CLASS 10 - BLANK. Neither work. Do you know why this would be?

---

<div class="post-metadata">

**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\
**Post date:** [January 20, 2022, 5:56am UTC](https://community.solid-run.com/t/lx2-honeycomb-requires-serial-connection-to-boot-linux-reboot-fails/224/4 "2022-01-20T05:56:13Z")

</div>

All though there are not many cards with this issue, we have found a few in our 10 years as a company just do not work well when used to boot firmware from them. Every SDHC card has its own microcontroller inside that manages the nand and has an OS. A few cards had issues resetting fast enough when doing a normal reboot and then loading the firmware from the card…for instance if the power pin is not held off long enough the card would crash on reboot’s because the firmware got stuck in an in between state.

Of course this issue can be mitigated by moving the firmware to the spi-nor flash or eMMC and using that as your firmware boot device.

---

<div class="post-metadata">

**Author:** ![embeddedDeveloper](https://avatars.discourse-cdn.com/v4/letter/e/c4cdca/32.png) [@embeddedDeveloper](https://community.solid-run.com/u/embeddedDeveloper)\
**Post date:** [January 20, 2022, 12:31pm UTC](https://community.solid-run.com/t/lx2-honeycomb-requires-serial-connection-to-boot-linux-reboot-fails/224/5 "2022-01-20T12:31:13Z")

</div>

Thanks for the information. One more question - is there configuration somewhere that is causing the board to require a serial connection to boot?

---

<div class="post-metadata">

**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\
**Post date:** [January 20, 2022, 2:10pm UTC](https://community.solid-run.com/t/lx2-honeycomb-requires-serial-connection-to-boot-linux-reboot-fails/224/6 "2022-01-20T14:10:22Z")

</div>

No, there is no requirement or setting that would require a serial connection to boot.
