AnsweredAssumed Answered

Change IMX6UL BSP From 512MB(256x16) to 256M(128x16)

Question asked by Nacho Diz on Jul 20, 2017
Latest reply on Jul 20, 2017 by Yuri Muhin

Dear all,

 

Our First Custom I.MX6UL PCB was using Micron 512 MB (As the EVK Board), also updating calibration Results Board Was Working Very Fine

 

Now, our Second PCB version haves Alliance Memory AS4C128M16D3L-12BIN 256MB to reduce costs, but after inserting the same SD card that we was using with first pcb version it hangs Loading Kernel ...

 

We are updating again the DDR confics at uboot but we see that original BSP is created only for 512MB

 

What aditional changes do we need to perform to tell linux and uboot that we only have 256MB?

 

Something like this perhaps? (1u * 256 * 1024 * 1024) ???

 

 

 

NOTE WE HAVE 128X16 (256MB)

 

U-Boot 2016.03 (May 18 2017 - 23:33:32 +0300)

 

CPU:   Freescale i.MX6UL rev1.1 528 MHz (running at 396 MHz)
CPU:   Industrial temperature grade (-40C to 105C) at 47C
Reset cause: POR
Board: MX6UL 14x14 EVK
I2C:   ready
DRAM:  512 MiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
*** Warning - bad CRC, using default environment

 

Display: TFT43AB (480x272)
Video: 480x272x24
In:    serial
Out:   serial
Err:   serial
switch to partitions #0, OK
mmc0 is current device
Net:   FEC1
Error: FEC1 address not set.

 

Normal Boot
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
switch to partitions #0, OK
mmc0 is current device
reading boot.scr
* Unable to read file boot.scr *
reading zImage
5293984 bytes read in 247 ms (20.4 MiB/s)
Booting from mmc ...
reading imx6ul-14x14-evk.dtb
37198 bytes read in 29 ms (1.2 MiB/s)
Kernel image @ 0x80800000 [ 0x000000 - 0x50c7a0 ]
## Flattened Device Tree blob at 83000000
   Booting using the fdt blob at 0x83000000
   Using Device Tree in place at 83000000, end 8300c14d
Modify /soc/aips-bus@02000000/bee@02044000:status disabled
ft_system_setup for mx6

 

Starting kernel ...

Outcomes