topic U-boot commands not working when running NOR and eMMC in Layerscape

U-boot commands not working when running NOR and eMMC

yellapu_anishkh — Fri, 20 Jan 2023 13:24:26 GMT

Hi Team,

I am working on a custom board based on RDB3, where we are using different DDR from Micron.

Generated code, with DDR DQ swapping changes and include in BSP33 and BSP34 for our custom board.

In both case u-boot is running and stopping at command prompt it taking input, but not able to execute any command including "help".

Log:

CPU: NXP S32G399A rev. 1.1

Model: NXP S32G399A-RDB3

DRAM: 3.5 GiB

MMC: FSL_SDHC: 0

Loading Environment from MMC... OK

In: serial@401c8000

Out: serial@401c8000

Err: serial@401c8000

##board specific logs##

Board revision: RDB

Net: Emac 0 not initialized

Invalid sgmii configuration for emac index 0

No ethernet found.

Hit any key to stop autoboot: 0

Unknown command '' - try 'help'

=> printenv

Unknown command 'printenv' - try 'help'

from cli "commands" not working. working when executed from source code.

Thanks in advance

#s32g3 #u-boot

Re: U-boot commands not working when running NOR and eMMC

Daniel-Aguirre — Mon, 23 Jan 2023 19:01:06 GMT

Hi,

Is this behavior happening with the provided NXP BSP? Or is this also a custom build?

Have you followed the Linux User Guide for this build? Have you verified that the DDR PHY is under the required specifications?

If we understand correctly, this is happening only in NOR and eMMC, running from SD is not causing this behavior?

We have a platform booting from NOR Flash which can accept commands in u-boot.

Please, let us know.

Re: U-boot commands not working when running NOR and eMMC

stadium_aquino — Tue, 24 Jan 2023 17:55:50 GMT

Make sure your terminal emulator or serial adapter is not inserting extra characters. Try modifying cmd_process in common/command.c to dump the hex code of what U-Boot thinks is the command. It's likely that a non-printable character has snuck in somewhere.

Re: U-boot commands not working when running NOR and eMMC

yellapu_anishkh — Tue, 31 Jan 2023 15:26:05 GMT

Issue is resolved after upgrading the UART to USB chip driver, used for console.