[U-Boot] i.Mx6q u-boot stuck

From: Fausto Sessego <fausto.sessego@infomob.it>
To: u-boot@lists.denx.de
Subject: [U-Boot] i.Mx6q u-boot stuck
Date: Tue, 11 Apr 2017 11:29:36 +0200	[thread overview]
Message-ID: <CAAbSMk=FuFrSO-6jxGxWLJYeZPj2VgpVN3V682TtWqU9jfjoBQ@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5DpcLtL5rCaJu41UChT8ZoZwXDphAixbUpsKwTu4Y=cCw@mail.gmail.com>

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.
>