What changes have to be made in the source while migrating from 1GB DDR SOM to 512 MB SOM?

cancel
Showing results for 
Search instead for 
Did you mean: 

What changes have to be made in the source while migrating from 1GB DDR SOM to 512 MB SOM?

190 Views
Contributor V

I'm using an imx6slevk board with yocto bsp with 1GB SOM. 

In a previous project I had used android kitkat with a 512 MB som now I wish to flash my yocto images to this board but the board freezes while flashing rootfs

I'm flashing using mfg tool into emmc.

Kernel and u-boot seem to flash without a problem but then there is no progress in rootfs.

I tried changing the dts file memory node in kernel

imx6sl-evk.dts

memory

{

reg = <0x80000000 0x40000000>;
};

to

memory {
reg = <0x80000000 0x20000000>;
 };

but there is no effect. 

What should I modify for this?

Labels (2)
0 Kudos
5 Replies

41 Views
NXP TechSupport
NXP TechSupport

Hello,

 

   use Chapter 3 (Porting U-Boot) of "i.MX_BSP_Porting_Guide.pdf".

In particular - section 3.2.1 (Changing the DCD table for i.MX DDR initialization).

https://www.nxp.com/webapp/Download?colCode=L4.14.78_1.0.0_LINUX_DOCS 

Have a great day,

Yuri

 

 

-------------------------------------------------------------------------------

Note:

- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored

Please open a new thread and refer to the closed one, if you have a related question at a later point in time.

0 Kudos

41 Views
Contributor V

Hi yuri

These are the steps I did for ddr callibration.

1. Ran ddr test tool to get ddr_callibration(log is as below)


 MMDC registers updated from calibration

Read calibration
MPRDDLCTL PHY0 (0x021b0848) = 0x4644484A

Write calibration
MPWRDLCTL PHY0 (0x021b0850) = 0x3A363A30

2. changes in imximage.cfg file:

DATA 4 0x021b0848 0x4646484a //changed to test for 512:old value 0x4241444a
DATA 4 0x021b0850 0x3a343a30 //changed to test for 512:old value 0x3030312b

3. dts file in uboot and kernel

memory {
reg = <0x80000000 0x20000000>; //it was 0x40000000 changed for 512 Mb
};

4. Build (u-boot kernel rfs) and flash to device

Log while flashing:

U-Boot 2017.03-imx_v2017.03_4.9.88_2.0.0_ga+ge88a4b5270 (Sep 23 2019 - 15:50:48 +0530)

CPU: Freescale i.MX6SL rev1.2 996 MHz (running at 792 MHz)
CPU: Commercial temperature grade (0C to 95C) at 49C
Reset cause: WDOG
Model: Freescale i.MX6 SoloLite EVK Board
Board: MX6SLEVK
DRAM: 1 GiB
Initializing for QP4720 bona 2P8 display
Initializing for bona 2P8 display
PMIC: PFUZE100! DEV_ID=0x10 REV_ID=0x21
MMC: FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
gpio@020ac000: get_value: error: gpio GPIO5_0 not reserved
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Net:
Error: ethernet@02188000 address not set.
No ethernet found.
Boot from USB for mfgtools
Use default environment for mfgtools
Run bootcmd_mfg: run mfgtool_args;if test ${tee} = yes; then bootm ${tee_addr} ${initrd_addr} ${fdt_addr}; else bootz ${loadaddr} ${initrd_add;
Hit any key to stop autoboot: 0
Kernel image @ 0x80800000 [ 0x000000 - 0x5edac0 ]
## Loading init Ramdisk from Legacy Image at 83800000 ...
Image Name: fsl-image-mfgtool-initramfs-imx6
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 8594034 Bytes = 8.2 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 83000000
Booting using the fdt blob at 0x83000000
Using Device Tree in place at 83000000, end 8300c538
switch to ldo_bypass mode!

Starting kernel ...

But the rootfs still doesn't flash it just hangs at kernel 

I tried bitbake fsl-image-mfgtool-initramfs and it created a 

fsl-image-mfgtool-initramfs-imx6slevk-20190923104008.rootfs.cpio.gz.u-boot file

but even this doesn't help in flashing. 

am I missing something?

0 Kudos

41 Views
NXP TechSupport
NXP TechSupport

Hello,

  can You try to create boot SD card for i.MX6SL on Linux host?

It does not require MFG.

Regards,

Yuri.

0 Kudos

41 Views
Contributor V

Hi Yuri

It's a specific requirement to use mfg tool from the customer.. what can I do?

0 Kudos

41 Views
NXP TechSupport
NXP TechSupport

 At least it is needed to check if new memory settings are working.

~Yuri. 

0 Kudos