* [U-Boot] i.Mx6q u-boot stuck
@ 2017-04-10 10:54 Fausto Sessego
2017-04-10 14:45 ` Fabio Estevam
0 siblings, 1 reply; 24+ messages in thread
From: Fausto Sessego @ 2017-04-10 10:54 UTC (permalink / raw)
To: u-boot
Hi,
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?
------------------------------
*Ing. Fausto Sessego*
*R&D Hardware & Software Engineer*
info
mob
>
*Tecnologie Wireless per la logistica e la sicurezza*
<http://www.infomob.it>
*a:* Parco scientifico e tecnologico della Sardegna, Edificio 1 Loc.
Piscinamanna - 09010 Pula (CA)
<https://www.google.it/maps/place/Sardegna+Ricerche/@38.9899811,8.9280376,17z/data=!3m1!4b1!4m2!3m1!1s0x12e7274e0b4c4191:0x1a9e7f06456bbd3>
*p:* +39 070 92432952
*e:* fausto.sessego at infomob.it
*w:* www.infomob.it
^ permalink raw reply [flat|nested] 24+ messages in thread* [U-Boot] i.Mx6q u-boot stuck 2017-04-10 10:54 [U-Boot] i.Mx6q u-boot stuck Fausto Sessego @ 2017-04-10 14:45 ` Fabio Estevam 2017-04-10 15:29 ` Fausto Sessego 0 siblings, 1 reply; 24+ messages in thread From: Fabio Estevam @ 2017-04-10 14:45 UTC (permalink / raw) To: u-boot Hi Fausto, On Mon, Apr 10, 2017 at 7:54 AM, Fausto Sessego <fausto.sessego@infomob.it> wrote: > Hi, > > 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 CONFIG_HUSH_PARSER=y is enabled in many mx6 boards without issues. It is difficult to see what is wrong without seeing your patch adding the support for your board. Make sure you are using the latest U-Boot code and check what other mx6 boards are doing. ^ permalink raw reply [flat|nested] 24+ messages in thread
* [U-Boot] i.Mx6q u-boot stuck 2017-04-10 14:45 ` Fabio Estevam @ 2017-04-10 15:29 ` Fausto Sessego 2017-04-10 19:18 ` Fabio Estevam 0 siblings, 1 reply; 24+ messages in thread From: Fausto Sessego @ 2017-04-10 15:29 UTC (permalink / raw) To: u-boot Hi Fabio, in attachment there are my configuration files. I started from SabreSD and i changed very minimal parts.7 Could you check if you see any error in my files? thanks ------------------------------ *Ing. Fausto Sessego* *R&D Hardware & Software Engineer* info mob > *Tecnologie Wireless per la logistica e la sicurezza* <http://www.infomob.it> *a:* Parco scientifico e tecnologico della Sardegna, Edificio 1 Loc. Piscinamanna - 09010 Pula (CA) <https://www.google.it/maps/place/Sardegna+Ricerche/@38.9899811,8.9280376,17z/data=!3m1!4b1!4m2!3m1!1s0x12e7274e0b4c4191:0x1a9e7f06456bbd3> *p:* +39 070 92432952 *e:* fausto.sessego at infomob.it *w:* www.infomob.it 2017-04-10 16:45 GMT+02:00 Fabio Estevam <festevam@gmail.com>: > Hi Fausto, > > On Mon, Apr 10, 2017 at 7:54 AM, Fausto Sessego > <fausto.sessego@infomob.it> wrote: > > Hi, > > > > 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 > > CONFIG_HUSH_PARSER=y is enabled in many mx6 boards without issues. > > It is difficult to see what is wrong without seeing your patch adding > the support for your board. > > Make sure you are using the latest U-Boot code and check what other > mx6 boards are doing. > -------------- next part -------------- A non-text attachment was scrubbed... Name: mx6board_common.h Type: text/x-chdr Size: 4752 bytes Desc: not available URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170410/f31d4ee2/attachment.h> -------------- next part -------------- A non-text attachment was scrubbed... Name: mx6qboard_defconfig Type: application/octet-stream Size: 916 bytes Desc: not available URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170410/f31d4ee2/attachment.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: mx6board.h Type: text/x-chdr Size: 2243 bytes Desc: not available URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170410/f31d4ee2/attachment-0001.h> ^ permalink raw reply [flat|nested] 24+ messages in thread
* [U-Boot] i.Mx6q u-boot stuck 2017-04-10 15:29 ` Fausto Sessego @ 2017-04-10 19:18 ` Fabio Estevam [not found] ` <2007927372.113767.1491854856064@pim.register.it> 0 siblings, 1 reply; 24+ messages in thread From: Fabio Estevam @ 2017-04-10 19:18 UTC (permalink / raw) To: u-boot On Mon, Apr 10, 2017 at 12:29 PM, Fausto Sessego <fausto.sessego@infomob.it> wrote: > Hi Fabio, > > in attachment there are my configuration files. > > I started from SabreSD and i changed very minimal parts.7 > > Could you check if you see any error in my files? > It would be better to submit a proper support for your mx6 board. You seem to call it mx6board, but in your defconfig you have: CONFIG_TARGET_MX6BAORD=y Looks like a typo. ^ permalink raw reply [flat|nested] 24+ messages in thread
[parent not found: <2007927372.113767.1491854856064@pim.register.it>]
* [U-Boot] i.Mx6q u-boot stuck [not found] ` <2007927372.113767.1491854856064@pim.register.it> @ 2017-04-10 20:14 ` Fabio Estevam 2017-04-11 9:29 ` Fausto Sessego 0 siblings, 1 reply; 24+ messages in thread From: Fabio Estevam @ 2017-04-10 20:14 UTC (permalink / raw) To: u-boot On Mon, Apr 10, 2017 at 5:07 PM, Fausto Sessego <fausto.sessego@infomob.it> wrote: > It is right because it is a custom board designed by my self. > > I renamed CONFIG_TARGET_MX6BOARD=y > > Do you have any hint? You can try removing the line ""mmcbooterror=echo Boot from mmc ERROR!!; " from your CONFIG_EXTRA_ENV_SETTINGS. ^ permalink raw reply [flat|nested] 24+ messages in thread
* [U-Boot] i.Mx6q u-boot stuck 2017-04-10 20:14 ` Fabio Estevam @ 2017-04-11 9:29 ` Fausto Sessego 2017-04-11 10:51 ` Fabio Estevam 0 siblings, 1 reply; 24+ messages in thread From: Fausto Sessego @ 2017-04-11 9:29 UTC (permalink / raw) To: u-boot I tryed to remove it but the result was the same. I have another straing problem: if i enable the macro #define DEBUG in my mx6board.h the system stuck U-Boot 2016.07 (Apr 11 2017 - 11:19:23 +0200) initcall: 1780b930 U-Boot code: 17800000 -> 17847A3C BSS: -> 178928E8 initcall: 17801cb4 CPU: Freescale i.MX6Q rev1.5 996 MHz (running at 792 MHz) CPU: Extended Commercial temperature grade (-20C to 105C)malloc_simple: size=10, ptr=ec, limit=400: 93fbdc uclass_find_device_by_seq: 0 -1 uclass_find_device_by_seq: 0 0 - -1 -1 - not found at 27C Reset cause: POR initcall: 1780be60 Board: i.MX6Q SIBIRI Support: http://www.infomob.it/ initcall: 1780b974 I2C: ready initcall: 1780b95c DRAM: initcall: 17802db0 gd->ram_size: 1073741824 initcall: 17802dd8 DRAM test not implemented! initcall: 1780bbb4 Monitor len: 000928E8 Ram size: 40000000 Ram top: 50000000 initcall: 1780b75c initcall: 1780b8d8 TLB table from 4fff0000 to 4fff4000 initcall: 1780b774 initcall: 1780b88c Reserving 586k for U-Boot at: 4ff5d000 initcall: 1780b85c Reserving 10248k for malloc() at: 4f55b000 initcall: 1780ba8c Reserving 80 Bytes for Board Info at: 4f55afb0 initcall: 1780b77c initcall: 1780b828 Reserving 248 Bytes for Global Data at: 4f55aeb8 initcall: 1780b7c4 initcall: 1780b798 initcall: 1780bc34 initcall: 1780bb8c initcall: 1780bae4 RAM Configuration: Bank #0: 10000000 1 GiB DRAM: 1 GiB initcall: 1780b7a8 New Stack Pointer is: 4f55ae90 initcall: 1780ba50 initcall: 1780b9e4 Relocation Offset is: 3875d000 Relocating to 4ff5d000, new gd at 4f55aeb8, sp at 4f55ae90 initcall: 4ff68c80 initcall: 4ff68c88 Could it be a problem of ram configuration? Thanks ------------------------------ *Ing. Fausto Sessego* *R&D Hardware & Software Engineer* info mob > *Tecnologie Wireless per la logistica e la sicurezza* <http://www.infomob.it> *a:* Parco scientifico e tecnologico della Sardegna, Edificio 1 Loc. Piscinamanna - 09010 Pula (CA) <https://www.google.it/maps/place/Sardegna+Ricerche/@38.9899811,8.9280376,17z/data=!3m1!4b1!4m2!3m1!1s0x12e7274e0b4c4191:0x1a9e7f06456bbd3> *p:* +39 070 92432952 *e:* fausto.sessego at infomob.it *w:* www.infomob.it 2017-04-10 22:14 GMT+02:00 Fabio Estevam <festevam@gmail.com>: > On Mon, Apr 10, 2017 at 5:07 PM, Fausto Sessego > <fausto.sessego@infomob.it> wrote: > > It is right because it is a custom board designed by my self. > > > > I renamed CONFIG_TARGET_MX6BOARD=y > > > > Do you have any hint? > > You can try removing the line ""mmcbooterror=echo Boot from mmc > ERROR!!; " from your CONFIG_EXTRA_ENV_SETTINGS. > ^ permalink raw reply [flat|nested] 24+ messages in thread
* [U-Boot] i.Mx6q u-boot stuck 2017-04-11 9:29 ` Fausto Sessego @ 2017-04-11 10:51 ` Fabio Estevam 2017-04-11 11:20 ` Fausto Sessego 0 siblings, 1 reply; 24+ messages in thread From: Fabio Estevam @ 2017-04-11 10:51 UTC (permalink / raw) To: u-boot On Tue, Apr 11, 2017 at 6:29 AM, Fausto Sessego <fausto.sessego@infomob.it> wrote > > > > Could it be a problem of ram configuration? > Yes, this could be the problem. ^ permalink raw reply [flat|nested] 24+ messages in thread
* [U-Boot] i.Mx6q u-boot stuck 2017-04-11 10:51 ` Fabio Estevam @ 2017-04-11 11:20 ` Fausto Sessego 2017-04-11 13:01 ` Fabio Estevam 0 siblings, 1 reply; 24+ messages in thread From: Fausto Sessego @ 2017-04-11 11:20 UTC (permalink / raw) To: u-boot what do you suggest? How can i check if the ram configuration is right? Thanks ------------------------------ *Ing. Fausto Sessego* *R&D Hardware & Software Engineer* info mob > *Tecnologie Wireless per la logistica e la sicurezza* <http://www.infomob.it> *a:* Parco scientifico e tecnologico della Sardegna, Edificio 1 Loc. Piscinamanna - 09010 Pula (CA) <https://www.google.it/maps/place/Sardegna+Ricerche/@38.9899811,8.9280376,17z/data=!3m1!4b1!4m2!3m1!1s0x12e7274e0b4c4191:0x1a9e7f06456bbd3> *p:* +39 070 92432952 *e:* fausto.sessego at infomob.it *w:* www.infomob.it 2017-04-11 12:51 GMT+02:00 Fabio Estevam <festevam@gmail.com>: > > > On Tue, Apr 11, 2017 at 6:29 AM, Fausto Sessego <fausto.sessego@infomob.it > > wrote >> >> >> >> Could it be a problem of ram configuration? >> > > Yes, this could be the problem. > > ^ permalink raw reply [flat|nested] 24+ messages in thread
* [U-Boot] i.Mx6q u-boot stuck 2017-04-11 11:20 ` Fausto Sessego @ 2017-04-11 13:01 ` Fabio Estevam 2017-05-05 10:50 ` Fausto Sessego 0 siblings, 1 reply; 24+ messages in thread From: Fabio Estevam @ 2017-04-11 13:01 UTC (permalink / raw) To: u-boot On Tue, Apr 11, 2017 at 8:20 AM, Fausto Sessego <fausto.sessego@infomob.it> wrote: > what do you suggest? > > How can i check if the ram configuration is right? > https://community.nxp.com/docs/DOC-331930 https://community.nxp.com/docs/DOC-105652 ^ permalink raw reply [flat|nested] 24+ messages in thread
* [U-Boot] i.Mx6q u-boot stuck 2017-04-11 13:01 ` Fabio Estevam @ 2017-05-05 10:50 ` Fausto Sessego 2017-05-05 11:38 ` Fabio Estevam 0 siblings, 1 reply; 24+ messages in thread From: Fausto Sessego @ 2017-05-05 10:50 UTC (permalink / raw) To: u-boot Ok, now it seems to work fine. I have another question: the define #define CONFIG_MMCROOT "/dev/mmcblk0p2" what does it mean? I have 2 sd card in my custom board: 1) SD3 used like mass storage 2) SD4 used to load the SO thanks ------------------------------ *Ing. Fausto Sessego* *R&D Hardware & Software Engineer* info mob > *Tecnologie Wireless per la logistica e la sicurezza* *address:* Parco scientifico e tecnologico della Sardegna, Edificio 1 Loc. Piscinamanna - 09010 Pula (CA) <https://www.google.it/maps/place/Sardegna+Ricerche/@38.9899811,8.9280376,17z/data=!3m1!4b1!4m2!3m1!1s0x12e7274e0b4c4191:0x1a9e7f06456bbd3> *phone:* +39 070 92432952 *email:* fausto.sessego at infomob.it *skype:* fausto.sessego.infomob *web:* www.infomob.it 2017-04-11 15:01 GMT+02:00 Fabio Estevam <festevam@gmail.com>: > > > On Tue, Apr 11, 2017 at 8:20 AM, Fausto Sessego <fausto.sessego@infomob.it > > wrote: > >> what do you suggest? >> >> How can i check if the ram configuration is right? >> > > https://community.nxp.com/docs/DOC-331930 > > https://community.nxp.com/docs/DOC-105652 > > ^ permalink raw reply [flat|nested] 24+ messages in thread
* [U-Boot] i.Mx6q u-boot stuck 2017-05-05 10:50 ` Fausto Sessego @ 2017-05-05 11:38 ` Fabio Estevam 2017-05-05 11:51 ` Fausto Sessego 0 siblings, 1 reply; 24+ messages in thread From: Fabio Estevam @ 2017-05-05 11:38 UTC (permalink / raw) To: u-boot On Fri, May 5, 2017 at 7:50 AM, Fausto Sessego <fausto.sessego@infomob.it> wrote: > Ok, > > now it seems to work fine. > Ok, great! > > I have another question: > > the define > #define CONFIG_MMCROOT "/dev/mmcblk0p2" > > what does it mean? > > I have 2 sd card in my custom board: > 1) SD3 used like mass storage > 2) SD4 used to load the SO > This option specifies the location of the rootfs. A better approach is to use PARTUUID instead. Please check: http://git.denx.de/?p=u-boot.git;a=commitdiff;h= ca4f338e2efece5196eb2178e5f7d07be828da6e;hp=375d19c9114c1aca722f22fca937ae c70e6feecf ^ permalink raw reply [flat|nested] 24+ messages in thread
* [U-Boot] i.Mx6q u-boot stuck 2017-05-05 11:38 ` Fabio Estevam @ 2017-05-05 11:51 ` Fausto Sessego 2017-05-05 11:56 ` Fabio Estevam 0 siblings, 1 reply; 24+ messages in thread From: Fausto Sessego @ 2017-05-05 11:51 UTC (permalink / raw) To: u-boot Ok. I have the problem the Kernel Stucks at startup "Starting Kernel .... " Could it depend on boot configuration (the macro CONFIG_MMCROOT) ? ------------------------------ *Ing. Fausto Sessego* *R&D Hardware & Software Engineer* info mob > *Tecnologie Wireless per la logistica e la sicurezza* *address:* Parco scientifico e tecnologico della Sardegna, Edificio 1 Loc. Piscinamanna - 09010 Pula (CA) <https://www.google.it/maps/place/Sardegna+Ricerche/@38.9899811,8.9280376,17z/data=!3m1!4b1!4m2!3m1!1s0x12e7274e0b4c4191:0x1a9e7f06456bbd3> *phone:* +39 070 92432952 *email:* fausto.sessego at infomob.it *skype:* fausto.sessego.infomob *web:* www.infomob.it 2017-05-05 13:38 GMT+02:00 Fabio Estevam <festevam@gmail.com>: > > > On Fri, May 5, 2017 at 7:50 AM, Fausto Sessego <fausto.sessego@infomob.it> > wrote: > >> Ok, >> >> now it seems to work fine. >> > > Ok, great! > > >> >> I have another question: >> >> the define >> #define CONFIG_MMCROOT "/dev/mmcblk0p2" >> >> what does it mean? >> >> I have 2 sd card in my custom board: >> 1) SD3 used like mass storage >> 2) SD4 used to load the SO >> > > This option specifies the location of the rootfs. > > A better approach is to use PARTUUID instead. Please check: > http://git.denx.de/?p=u-boot.git;a=commitdiff;h=ca4f338e2efe > ce5196eb2178e5f7d07be828da6e;hp=375d19c9114c1aca722f22fca937aec70e6feecf > > ^ permalink raw reply [flat|nested] 24+ messages in thread
* [U-Boot] i.Mx6q u-boot stuck 2017-05-05 11:51 ` Fausto Sessego @ 2017-05-05 11:56 ` Fabio Estevam 2017-05-24 16:29 ` Fausto Sessego 0 siblings, 1 reply; 24+ messages in thread From: Fabio Estevam @ 2017-05-05 11:56 UTC (permalink / raw) To: u-boot On Fri, May 5, 2017 at 8:51 AM, Fausto Sessego <fausto.sessego@infomob.it> wrote: > Ok. > > I have the problem the Kernel Stucks at startup "Starting Kernel .... " > > Could it depend on boot configuration (the macro CONFIG_MMCROOT) ? > No, the rootfs will be mounted at a much later stage. ^ permalink raw reply [flat|nested] 24+ messages in thread
* [U-Boot] i.Mx6q u-boot stuck 2017-05-05 11:56 ` Fabio Estevam @ 2017-05-24 16:29 ` Fausto Sessego 2017-05-24 20:56 ` Fabio Estevam 2017-05-25 8:57 ` Anatolij Gustschin 0 siblings, 2 replies; 24+ messages in thread From: Fausto Sessego @ 2017-05-24 16:29 UTC (permalink / raw) To: u-boot Ok. The Kernel doesn't start. U-Boot 2016.07 (May 24 2017 - 17:11:18 +0200) CPU: Freescale i.MX6Q rev1.2 at 792MHz CPU: Industrial temperature grade (-40C to 105C) at 20C Reset cause: POR Board: i.MX6Q TIBIDABO Support: http://www.infomob.it/ I2C: ready DRAM: gd->ram_size: 2147483648 DRAM test not implemented! 2 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 reading imx6q-tibidabo.dtb 29640 bytes read in 22 ms (1.3 MiB/s) reading uImage 6621928 bytes read in 324 ms (19.5 MiB/s) ## Booting kernel from Legacy Image at 12000000 ... Image Name: Linux-4.1.38 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 6621864 Bytes = 6.3 MiB Load Address: 10008000 Entry Point: 10008000 Verifying Checksum ... OK Loading Kernel Image ... OK Starting kernel ... Can it depend on u-boot version? I'm using u-boot 2016.07 and kernel 4.1-1.0.x. I get u-boot and kernel directly from yocto, so i think the matching is right. I tried many procedures but i did'nt found any solution. Thanks ------------------------------ *Ing. Fausto Sessego* *R&D Hardware & Software Engineer* info mob > *Tecnologie Wireless per la logistica e la sicurezza* *address:* Parco scientifico e tecnologico della Sardegna, Edificio 1 Loc. Piscinamanna - 09010 Pula (CA) <https://www.google.it/maps/place/Sardegna+Ricerche/@38.9899811,8.9280376,17z/data=!3m1!4b1!4m2!3m1!1s0x12e7274e0b4c4191:0x1a9e7f06456bbd3> *phone:* +39 070 92432952 *email:* fausto.sessego at infomob.it *skype:* fausto.sessego.infomob *web:* www.infomob.it 2017-05-05 13:56 GMT+02:00 Fabio Estevam <festevam@gmail.com>: > > > On Fri, May 5, 2017 at 8:51 AM, Fausto Sessego <fausto.sessego@infomob.it> > wrote: > >> Ok. >> >> I have the problem the Kernel Stucks at startup "Starting Kernel .... " >> >> Could it depend on boot configuration (the macro CONFIG_MMCROOT) ? >> > > No, the rootfs will be mounted at a much later stage. > > ^ permalink raw reply [flat|nested] 24+ messages in thread
* [U-Boot] i.Mx6q u-boot stuck 2017-05-24 16:29 ` Fausto Sessego @ 2017-05-24 20:56 ` Fabio Estevam 2017-05-24 21:00 ` Fabio Estevam 2017-05-25 8:57 ` Anatolij Gustschin 1 sibling, 1 reply; 24+ messages in thread From: Fabio Estevam @ 2017-05-24 20:56 UTC (permalink / raw) To: u-boot Hi Fausto, Please do not top post in mailing lists. On Wed, May 24, 2017 at 1:29 PM, Fausto Sessego <fausto.sessego@infomob.it> wrote > > > I tried many procedures but i did'nt found any solution. > Try to do: make menuconfig Kernel hacking ---> [*] Kernel low-level debugging functions (read help!) Kernel low-level debugging port (i.MX6Q/DL Debug UART) (1) i.MX Debug UART Port Selection (NEW) [*] Early printk In this example the console port is at UART1. If you have the console on another UART then adjust it properly. Then pass 'earyprintk' in the kernel command line as well. This would help you to see where the kernel is hanging. Hope it helps. ^ permalink raw reply [flat|nested] 24+ messages in thread
* [U-Boot] i.Mx6q u-boot stuck 2017-05-24 20:56 ` Fabio Estevam @ 2017-05-24 21:00 ` Fabio Estevam 0 siblings, 0 replies; 24+ messages in thread From: Fabio Estevam @ 2017-05-24 21:00 UTC (permalink / raw) To: u-boot On Wed, May 24, 2017 at 5:56 PM, Fabio Estevam <festevam@gmail.com> wrote: > Then pass 'earyprintk' in the kernel command line as well. I meant "earlyprintk". ^ permalink raw reply [flat|nested] 24+ messages in thread
* [U-Boot] i.Mx6q u-boot stuck 2017-05-24 16:29 ` Fausto Sessego 2017-05-24 20:56 ` Fabio Estevam @ 2017-05-25 8:57 ` Anatolij Gustschin 2017-05-26 10:39 ` Fausto Sessego 1 sibling, 1 reply; 24+ messages in thread From: Anatolij Gustschin @ 2017-05-25 8:57 UTC (permalink / raw) To: u-boot On Wed, 24 May 2017 18:29:50 +0200 Fausto Sessego fausto.sessego at infomob.it wrote: ... > The Kernel doesn't start. > > U-Boot 2016.07 (May 24 2017 - 17:11:18 +0200) > > CPU: Freescale i.MX6Q rev1.2 at 792MHz > CPU: Industrial temperature grade (-40C to 105C) at 20C > Reset cause: POR > Board: i.MX6Q TIBIDABO > Support: http://www.infomob.it/ > I2C: ready > DRAM: gd->ram_size: 2147483648 > DRAM test not implemented! > 2 GiB > MMC: FSL_SDHC: 0, FSL_SDHC: 1 > *** Warning - bad CRC, using default environment you didn't save the environment, so the default environment is used. > In: serial > Out: serial > Err: serial > Net: FEC [PRIME] > Error: FEC address not set. > > Hit any key to stop autoboot: 0 > reading imx6q-tibidabo.dtb > 29640 bytes read in 22 ms (1.3 MiB/s) > reading uImage > 6621928 bytes read in 324 ms (19.5 MiB/s) > ## Booting kernel from Legacy Image at 12000000 ... > Image Name: Linux-4.1.38 > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 6621864 Bytes = 6.3 MiB > Load Address: 10008000 > Entry Point: 10008000 > Verifying Checksum ... OK > Loading Kernel Image ... OK > > Starting kernel ... Please check 'bootargs' environment variable (print bootargs). It should contain "console=ttymxc0,115200" among other values. Probably this is not set in the default environment and is missing. Ensure that you are passing the correct console string for your board in bootargs. I'm not sure if ttymxc0 is correct, please test it first. -- Anatolij ^ permalink raw reply [flat|nested] 24+ messages in thread
* [U-Boot] i.Mx6q u-boot stuck 2017-05-25 8:57 ` Anatolij Gustschin @ 2017-05-26 10:39 ` Fausto Sessego 2017-05-26 12:04 ` Lothar Waßmann 2017-05-26 12:36 ` Fabio Estevam 0 siblings, 2 replies; 24+ messages in thread From: Fausto Sessego @ 2017-05-26 10:39 UTC (permalink / raw) To: u-boot Hi, here you are my configuration: #define CONFIG_EXTRA_ENV_SETTINGS \ "image=zImage\0" \ "console=" CONFIG_CONSOLE_DEV "\0" \ "fdt_file=imx6q-tibidabo.dtb\0" \ "fdt_addr=0x14000000\0" \ "mmcdev="__stringify(CONFIG_SYS_MMC_ENV_DEV)"\0" \ "mmcpart=" __stringify(CONFIG_SYS_MMC_IMG_LOAD_PART) "\0" \ "mmcroot=" CONFIG_MMCROOT " rootwait rw\0" \ "mmcautodetect=yes\0" \ "mmcargs=setenv bootargs console=${console},${baudrate} earlyprintk " \ "root=${mmcroot}\0" \ "loadimage=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${image}\0" \ "loadfdt=fatload mmc ${mmcdev}:${mmcpart} ${fdt_addr} ${fdt_file}\0" \ #define CONFIG_BOOTCOMMAND \ "run mmcargs; " \ "run loadfdt; " \ "run loadimage; " \ "bootz ${loadaddr} - ${fdt_addr}; "\ it is easy. I tried to put earlyprintk but i didn't see any output. ------------------------------ *Ing. Fausto Sessego* *R&D Hardware & Software Engineer* info mob > *Tecnologie Wireless per la logistica e la sicurezza* *address:* Parco scientifico e tecnologico della Sardegna, Edificio 1 Loc. Piscinamanna - 09010 Pula (CA) <https://www.google.it/maps/place/Sardegna+Ricerche/@38.9899811,8.9280376,17z/data=!3m1!4b1!4m2!3m1!1s0x12e7274e0b4c4191:0x1a9e7f06456bbd3> *phone:* +39 070 92432952 *email:* fausto.sessego at infomob.it *skype:* fausto.sessego.infomob *web:* www.infomob.it 2017-05-25 10:57 GMT+02:00 Anatolij Gustschin <agust@denx.de>: > On Wed, 24 May 2017 18:29:50 +0200 > Fausto Sessego fausto.sessego at infomob.it wrote: > ... > > The Kernel doesn't start. > > > > U-Boot 2016.07 (May 24 2017 - 17:11:18 +0200) > > > > CPU: Freescale i.MX6Q rev1.2 at 792MHz > > CPU: Industrial temperature grade (-40C to 105C) at 20C > > Reset cause: POR > > Board: i.MX6Q TIBIDABO > > Support: http://www.infomob.it/ > > I2C: ready > > DRAM: gd->ram_size: 2147483648 > > DRAM test not implemented! > > 2 GiB > > MMC: FSL_SDHC: 0, FSL_SDHC: 1 > > *** Warning - bad CRC, using default environment > > you didn't save the environment, so the default environment is > used. > > > In: serial > > Out: serial > > Err: serial > > Net: FEC [PRIME] > > Error: FEC address not set. > > > > Hit any key to stop autoboot: 0 > > reading imx6q-tibidabo.dtb > > 29640 bytes read in 22 ms (1.3 MiB/s) > > reading uImage > > 6621928 bytes read in 324 ms (19.5 MiB/s) > > ## Booting kernel from Legacy Image at 12000000 ... > > Image Name: Linux-4.1.38 > > Image Type: ARM Linux Kernel Image (uncompressed) > > Data Size: 6621864 Bytes = 6.3 MiB > > Load Address: 10008000 > > Entry Point: 10008000 > > Verifying Checksum ... OK > > Loading Kernel Image ... OK > > > > Starting kernel ... > > Please check 'bootargs' environment variable (print bootargs). > It should contain "console=ttymxc0,115200" among other values. > Probably this is not set in the default environment and is missing. > Ensure that you are passing the correct console string for your > board in bootargs. I'm not sure if ttymxc0 is correct, please > test it first. > > -- > Anatolij > ^ permalink raw reply [flat|nested] 24+ messages in thread
* [U-Boot] i.Mx6q u-boot stuck 2017-05-26 10:39 ` Fausto Sessego @ 2017-05-26 12:04 ` Lothar Waßmann 2017-05-27 11:00 ` Fausto Sessego 2017-05-26 12:36 ` Fabio Estevam 1 sibling, 1 reply; 24+ messages in thread From: Lothar Waßmann @ 2017-05-26 12:04 UTC (permalink / raw) To: u-boot Fausto Sessego <fausto.sessego@infomob.it> wrote: > Hi, > > here you are my configuration: > > #define CONFIG_EXTRA_ENV_SETTINGS \ > "image=zImage\0" \ > "console=" CONFIG_CONSOLE_DEV "\0" \ > "fdt_file=imx6q-tibidabo.dtb\0" \ > "fdt_addr=0x14000000\0" \ > "mmcdev="__stringify(CONFIG_SYS_MMC_ENV_DEV)"\0" \ > "mmcpart=" __stringify(CONFIG_SYS_MMC_IMG_LOAD_PART) "\0" \ > "mmcroot=" CONFIG_MMCROOT " rootwait rw\0" \ > "mmcautodetect=yes\0" \ > "mmcargs=setenv bootargs console=${console},${baudrate} earlyprintk " \ > "root=${mmcroot}\0" \ > "loadimage=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${image}\0" \ > "loadfdt=fatload mmc ${mmcdev}:${mmcpart} ${fdt_addr} ${fdt_file}\0" \ > > > #define CONFIG_BOOTCOMMAND \ > "run mmcargs; " \ > "run loadfdt; " \ > "run loadimage; " \ > "bootz ${loadaddr} - ${fdt_addr}; "\ > > it is easy. > > I tried to put earlyprintk but i didn't see any output. > > Please do not top-post! (put your own comments _after_ the quoted portion of the original mail you are responding to just like everyone else on this mailing list). Your SDRAM size is 2GiB. That means U-Boot will relocate the FDT outside reach for the kernel. Try setting 'fdt_high=0xffffffff' (or ${fdt_addr}), to prevent U-Boot from relocating the FDT. Lothar Waßmann -- ___________________________________________________________ Ka-Ro electronics GmbH | Pascalstraße 22 | D - 52076 Aachen Phone: +49 2408 1402-0 | Fax: +49 2408 1402-10 Geschäftsführer: Matthias Kaussen Handelsregistereintrag: Amtsgericht Aachen, HRB 4996 www.karo-electronics.de | info at karo-electronics.de ___________________________________________________________ ^ permalink raw reply [flat|nested] 24+ messages in thread
* [U-Boot] i.Mx6q u-boot stuck 2017-05-26 12:04 ` Lothar Waßmann @ 2017-05-27 11:00 ` Fausto Sessego 2017-05-27 12:50 ` Fabio Estevam 0 siblings, 1 reply; 24+ messages in thread From: Fausto Sessego @ 2017-05-27 11:00 UTC (permalink / raw) To: u-boot 2017-05-26 14:04 GMT+02:00 Lothar Waßmann <LW@karo-electronics.de>: > Fausto Sessego <fausto.sessego@infomob.it> wrote: > > > Hi, > > > > here you are my configuration: > > > > #define CONFIG_EXTRA_ENV_SETTINGS \ > > "image=zImage\0" \ > > "console=" CONFIG_CONSOLE_DEV "\0" \ > > "fdt_file=imx6q-tibidabo.dtb\0" \ > > "fdt_addr=0x14000000\0" \ > > "mmcdev="__stringify(CONFIG_SYS_MMC_ENV_DEV)"\0" \ > > "mmcpart=" __stringify(CONFIG_SYS_MMC_IMG_LOAD_PART) "\0" \ > > "mmcroot=" CONFIG_MMCROOT " rootwait rw\0" \ > > "mmcautodetect=yes\0" \ > > "mmcargs=setenv bootargs console=${console},${baudrate} earlyprintk " \ > > "root=${mmcroot}\0" \ > > "loadimage=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${image}\0" \ > > "loadfdt=fatload mmc ${mmcdev}:${mmcpart} ${fdt_addr} ${fdt_file}\0" \ > > > > > > #define CONFIG_BOOTCOMMAND \ > > "run mmcargs; " \ > > "run loadfdt; " \ > > "run loadimage; " \ > > "bootz ${loadaddr} - ${fdt_addr}; "\ > > > > it is easy. > > > > I tried to put earlyprintk but i didn't see any output. > > > > > Please do not top-post! (put your own comments _after_ the quoted > portion of the original mail you are responding to just like everyone > else on this mailing list). > > Your SDRAM size is 2GiB. That means U-Boot will relocate the FDT > outside reach for the kernel. Try setting 'fdt_high=0xffffffff' (or > ${fdt_addr}), to prevent U-Boot from relocating the FDT. > > > Lothar Waßmann > -- > ___________________________________________________________ > > Ka-Ro electronics GmbH | Pascalstraße 22 | D - 52076 Aachen > Phone: +49 2408 1402-0 | Fax: +49 2408 1402-10 > Geschäftsführer: Matthias Kaussen > Handelsregistereintrag: Amtsgericht Aachen, HRB 4996 > > www.karo-electronics.de | info at karo-electronics.de > ___________________________________________________________ > I finally found the error enabling "earlyprintk" U-Boot 2016.07 (May 27 2017 - 01:17:11 +0200) CPU: Freescale i.MX6Q rev1.2 at 792MHz CPU: Industrial temperature grade (-40C to 105C) at 30C Reset cause: POR Board: i.MX6Q TIBIDABO I2C: ready DRAM: gd->ram_size: 2147483648 DRAM test not implemented! 2 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 reading imx6q-tibidabo.dtb 29636 bytes read in 22 ms (1.3 MiB/s) reading uImage 6622920 bytes read in 324 ms (19.5 MiB/s) ## Booting kernel from Legacy Image at 12000000 ... Image Name: Linux-4.1.38 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 6622856 Bytes = 6.3 MiB Load Address: 10008000 Entry Point: 10008000 Verifying Checksum ... OK Loading Kernel Image ... OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Error: unrecognized/unsupported machine ID (r1 = 0x000015b3). Available machine support: ID (hex) NAME ffffffff Generic DT based system ffffffff Freescale i.MX6 Quad/DualLite (Device Tree) ffffffff Freescale i.MX6 SoloLite (Device Tree) ffffffff Freescale i.MX6 SoloX (Device Tree) ffffffff Freescale i.MX6 Ultralite (Device Tree) ffffffff Freescale i.MX7 Dual (Device Tree) ffffffff Freescale i.MX50 (Device Tree Support) ffffffff Freescale i.MX53 (Device Tree Support) ffffffff Freescale Vybrid VF5xx/VF6xx (Device Tree) Please check your kernel config and/or bootloader. There is the error "Error: unrecognized/unsupported machine ID" I read many post but i didn't found any solution. PS: is it ok if i answer this way? thank ^ permalink raw reply [flat|nested] 24+ messages in thread
* [U-Boot] i.Mx6q u-boot stuck 2017-05-27 11:00 ` Fausto Sessego @ 2017-05-27 12:50 ` Fabio Estevam 2017-05-29 8:37 ` Fausto Sessego 0 siblings, 1 reply; 24+ messages in thread From: Fabio Estevam @ 2017-05-27 12:50 UTC (permalink / raw) To: u-boot On Sat, May 27, 2017 at 8:00 AM, Fausto Sessego <fausto.sessego@infomob.it> wrote: > Starting kernel ... > > Uncompressing Linux... done, booting the kernel. > > Error: unrecognized/unsupported machine ID (r1 = 0x000015b3). > > Available machine support: > > ID (hex) NAME > ffffffff Generic DT based system > ffffffff Freescale i.MX6 Quad/DualLite (Device Tree) > ffffffff Freescale i.MX6 SoloLite (Device Tree) > ffffffff Freescale i.MX6 SoloX (Device Tree) > ffffffff Freescale i.MX6 Ultralite (Device Tree) > ffffffff Freescale i.MX7 Dual (Device Tree) > ffffffff Freescale i.MX50 (Device Tree Support) > ffffffff Freescale i.MX53 (Device Tree Support) > ffffffff Freescale Vybrid VF5xx/VF6xx (Device Tree) > > Please check your kernel config and/or bootloader. > > There is the error "Error: unrecognized/unsupported machine ID" > > I read many post but i didn't found any solution. You are probably missing: CONFIG_OF_LIBFDT=y in your defconfig file. Just looked at your defconfig and it has: #CONFIG_OF_LIBFDT=y So you need to remove the "#" in front of it. This will tell U-Boot that it will boot a kernel + dtb. ^ permalink raw reply [flat|nested] 24+ messages in thread
* [U-Boot] i.Mx6q u-boot stuck 2017-05-27 12:50 ` Fabio Estevam @ 2017-05-29 8:37 ` Fausto Sessego 0 siblings, 0 replies; 24+ messages in thread From: Fausto Sessego @ 2017-05-29 8:37 UTC (permalink / raw) To: u-boot 2017-05-27 14:50 GMT+02:00 Fabio Estevam <festevam@gmail.com>: > On Sat, May 27, 2017 at 8:00 AM, Fausto Sessego > <fausto.sessego@infomob.it> wrote: > > > Starting kernel ... > > > > Uncompressing Linux... done, booting the kernel. > > > > Error: unrecognized/unsupported machine ID (r1 = 0x000015b3). > > > > Available machine support: > > > > ID (hex) NAME > > ffffffff Generic DT based system > > ffffffff Freescale i.MX6 Quad/DualLite (Device Tree) > > ffffffff Freescale i.MX6 SoloLite (Device Tree) > > ffffffff Freescale i.MX6 SoloX (Device Tree) > > ffffffff Freescale i.MX6 Ultralite (Device Tree) > > ffffffff Freescale i.MX7 Dual (Device Tree) > > ffffffff Freescale i.MX50 (Device Tree Support) > > ffffffff Freescale i.MX53 (Device Tree Support) > > ffffffff Freescale Vybrid VF5xx/VF6xx (Device Tree) > > > > Please check your kernel config and/or bootloader. > > > > There is the error "Error: unrecognized/unsupported machine ID" > > > > I read many post but i didn't found any solution. > > You are probably missing: > CONFIG_OF_LIBFDT=y > > in your defconfig file. > > Just looked at your defconfig and it has: > #CONFIG_OF_LIBFDT=y > > So you need to remove the "#" in front of it. > > This will tell U-Boot that it will boot a kernel + dtb. > Now it's working and i'm able to load the kernel. Thank you ^ permalink raw reply [flat|nested] 24+ messages in thread
* [U-Boot] i.Mx6q u-boot stuck 2017-05-26 10:39 ` Fausto Sessego 2017-05-26 12:04 ` Lothar Waßmann @ 2017-05-26 12:36 ` Fabio Estevam 2017-05-26 13:12 ` Fausto Sessego 1 sibling, 1 reply; 24+ messages in thread From: Fabio Estevam @ 2017-05-26 12:36 UTC (permalink / raw) To: u-boot Hi Fausto, On Fri, May 26, 2017 at 7:39 AM, Fausto Sessego <fausto.sessego@infomob.it> wrote: > > > #define CONFIG_BOOTCOMMAND \ > "run mmcargs; " \ > "run loadfdt; " \ > "run loadimage; " \ > "bootz ${loadaddr} - ${fdt_addr}; "\ > The bootz command expects a zImage type of kernel. In your previous message you were passing uImage, so what you should do is: 1.Pass a zImage and use it with bootz or 2. Pass a uImage and use it with bootm. Hope this helps. ^ permalink raw reply [flat|nested] 24+ messages in thread
* [U-Boot] i.Mx6q u-boot stuck 2017-05-26 12:36 ` Fabio Estevam @ 2017-05-26 13:12 ` Fausto Sessego 0 siblings, 0 replies; 24+ messages in thread From: Fausto Sessego @ 2017-05-26 13:12 UTC (permalink / raw) To: u-boot Hi Fabio, i tried both solutions without any output. ------------------------------ *Ing. Fausto Sessego* *R&D Hardware & Software Engineer* info mob > *Tecnologie Wireless per la logistica e la sicurezza* *address:* Parco scientifico e tecnologico della Sardegna, Edificio 1 Loc. Piscinamanna - 09010 Pula (CA) <https://www.google.it/maps/place/Sardegna+Ricerche/@38.9899811,8.9280376,17z/data=!3m1!4b1!4m2!3m1!1s0x12e7274e0b4c4191:0x1a9e7f06456bbd3> *phone:* +39 070 92432952 *email:* fausto.sessego at infomob.it *skype:* fausto.sessego.infomob *web:* www.infomob.it 2017-05-26 14:36 GMT+02:00 Fabio Estevam <festevam@gmail.com>: > Hi Fausto, > > On Fri, May 26, 2017 at 7:39 AM, Fausto Sessego <fausto.sessego@infomob.it > > wrote: > >> >> >> #define CONFIG_BOOTCOMMAND \ >> "run mmcargs; " \ >> "run loadfdt; " \ >> "run loadimage; " \ >> "bootz ${loadaddr} - ${fdt_addr}; "\ >> > > The bootz command expects a zImage type of kernel. > > In your previous message you were passing uImage, so what you should do is: > > 1.Pass a zImage and use it with bootz > > or > > 2. Pass a uImage and use it with bootm. > > Hope this helps. > ^ permalink raw reply [flat|nested] 24+ messages in thread
end of thread, other threads:[~2017-05-29 8:37 UTC | newest]
Thread overview: 24+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-04-10 10:54 [U-Boot] i.Mx6q u-boot stuck Fausto Sessego
2017-04-10 14:45 ` Fabio Estevam
2017-04-10 15:29 ` Fausto Sessego
2017-04-10 19:18 ` Fabio Estevam
[not found] ` <2007927372.113767.1491854856064@pim.register.it>
2017-04-10 20:14 ` Fabio Estevam
2017-04-11 9:29 ` Fausto Sessego
2017-04-11 10:51 ` Fabio Estevam
2017-04-11 11:20 ` Fausto Sessego
2017-04-11 13:01 ` Fabio Estevam
2017-05-05 10:50 ` Fausto Sessego
2017-05-05 11:38 ` Fabio Estevam
2017-05-05 11:51 ` Fausto Sessego
2017-05-05 11:56 ` Fabio Estevam
2017-05-24 16:29 ` Fausto Sessego
2017-05-24 20:56 ` Fabio Estevam
2017-05-24 21:00 ` Fabio Estevam
2017-05-25 8:57 ` Anatolij Gustschin
2017-05-26 10:39 ` Fausto Sessego
2017-05-26 12:04 ` Lothar Waßmann
2017-05-27 11:00 ` Fausto Sessego
2017-05-27 12:50 ` Fabio Estevam
2017-05-29 8:37 ` Fausto Sessego
2017-05-26 12:36 ` Fabio Estevam
2017-05-26 13:12 ` Fausto Sessego
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.