i.Mx6q u-boot stuck

cancel
Showing results for 
Search instead for 
Did you mean: 

i.Mx6q u-boot stuck

857 Views
faustosessego1
Contributor III

Hi all,

i have a problem with my custom board.

I created my custom u-boot and, now, i would like load automatically the kernel by CONFIG_BOOTCOMMAND.

#define CONFIG_BOOTCOMMAND \

    "mmc dev ${mmcdev};"  \

    "if mmc rescan; then "  \

    "echo test1; "  \

    "else echo test2; fi; "

Because i have the "if" condition, i enabled the CONFIG_HUSH_PARSER=y into deconf file.

Adding this CONFIG, the u-boot stuck

CPU: Freescale i.MX6Q rev1.5 996 MHz (running at 792 MHz)
CPU: Extended Commercial temperature grade (-20C to 105C) at 26C
Reset cause: POR
I2C: ready
DRAM: gd->ram_size: 1073741824
DRAM test not implemented!
1 GiB

Whitout the definition CONFIG_HUSH_PARSER=y i have the following result:


CPU: Freescale i.MX6Q rev1.5 996 MHz (running at 792 MHz)
CPU: Extended Commercial temperature grade (-20C to 105C) at 28C
Reset cause: POR
I2C: ready
DRAM: gd->ram_size: 1073741824
DRAM test not implemented!
1 GiB

1 GiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Net: FEC [PRIME]
Error: FEC address not set.

Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1 is current device
Unknown command 'if' - try 'help'
Unknown command 'then' - try 'help'
Unknown command 'else' - try 'help'
Unknown command 'fi' - try 'help'

Custimized_board>

Why, if i enable the CONFIG_HUSH_PARSER=y, the u-boot stuck?

Labels (2)
0 Kudos
2 Replies

155 Views
igorpadykov
NXP TechSupport
NXP TechSupport

Hi Fausto

please refer to attached Porting Guide and use nxp uboot

http://git.freescale.com/git/cgit.cgi/imx/uboot-imx.git/tree/?h=imx_v2016.03_4.1.15_2.0.0_ga

Also as this is specific uboot question it may be posted on uboot mail list

WebHome < U-Boot < DENX 

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos

155 Views
faustosessego1
Contributor III

Ok, i posted into u-boot mailing list my problem.
I have another question:
I configured all peripehricals / IO into u-boot.
I know there is the possibility to call the number 0x80000000 into kernel to get the previous setting:

for example

&iomuxc {      pinctrl-names = "default";      pinctrl-0 = <&pinctrl_hog>;       hog {           pinctrl_hog: hoggrp {           fsl,pins = <                 /* gpio-leds */                MX6QDL_PAD_EIM_D28__GPIO3_IO28 0x80000000                MX6QDL_PAD_EIM_A25__GPIO5_IO02 0x80000000                 /* J11 pins 32, 34, 36, 38 */                MX6QDL_PAD_CSI0_DAT8__GPIO5_IO26     8                MX6QDL_PAD_CSI0_DAT9__GPIO5_IO27     8                MX6QDL_PAD_KEY_COL1__GPIO4_IO08          8                MX6QDL_PAD_KEY_ROW1__GPIO4_IO09          8           >;           };      }; };

In this way, i avoid to configure again the IO.


What do you suggest?

To configure all pin into u-boot and after to call 0x80000000 for all IO into kernel, or to configure again?

What is it the correct procedure?

thank you

0 Kudos