Issues about DDR porting on MX6DL

[tony_l_cai]

Dear all,

     we are porting Android 5.0 on MX6DL, and we found the changes from Android 4.2 to Android 5 in DDR porting.

     1 In Android 4.2, we use the Flash_header.S for DDR porting. the configuration is enclosed. But in Android 5.0, we port it by cfg file, and maybe it is applied in project yocto?(we havent worked in project yocto before.) So could you give me some info about porting DDR by cfg?  I found the main deference between cfg and flash_header.s is that the addtional configure for setting the default clock gate to save power in cfg file. Please help me to re-check the DDR config settings from flash_header.S to cfg file. 3Q~

     2. I also found obvious diffences between "bootable\bootloader\uboot-imx\board\freescale\mx6sabresd\mx6sabresd.c" and "bootable\bootloader\uboot-imx\board\freescale\mx6q_sabresd\mx6q_sabresd.c"，So does this changes will impact on the u-boot.bin excute?

     The reason why I asked all these questions is  that our uboot porting cannot go when I download the u-boot to the board and jump to OS. But the same way can succeeded in Android 4.2.  the question see also  https://community.freescale.com/message/534587?sr=search&searchId=a7876968-3eb5-45ce-b606-d7e3323853...

3Q~

Original Attachment has been moved to: flash_header.S.zip

Original Attachment has been moved to: EM70_Lollipop_DDR3.cfg.zip

[igorpadykov]

HI tony

for custom board one also needs to rebuild mfg tools firmware, refer to attached

Yocto Guide sect.6.2 The Manufacturing Tool, MFGTool, then replace

files in mfg tools folder /firmware

L3.10.53_1.1.0_iMX6QDLS_Bundle

In general for testing one can build minimal linux image and try to flash it

with mgf tools.

Best regards

igor

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

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

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

[tony_l_cai]

Dear igorpadykov​

     Maybe these problems are irrelevent with the MFG Tool Firmware, Because we just download the uboot.bin and jump to OS, the content of the  uc2.xml is as below:( we are now just testing the uboot)

<LIST name="eMMC-Android-IMX6DL-SabreSD" desc="Choose eMMC as media">

  <CMD state="BootStrap" type="boot" body="BootStrap" file ="firmware/u-boot.bin">Loading U-boot</CMD>

  <CMD state="BootStrap" type="jump" > Jumping to OS image. </CMD>

  </LIST>

[igorpadykov]

Sorry, I do not think so.

In any way you can test suggestion and check if this helps.

[tony_l_cai]

Hi，igor

     In my current stage ,I dont use the initramfs.cpio.gz.uboot at all,and just test u-boot.bin. Why do I need to rebuild it? Could you help me to sweep the confusion, Thank you very much.

     And if convenient, could give me the way for rebuilding initramfs.cpio.gz.uboot in detail, Thanks a lot.

[igorpadykov]

if you are using mfg tools, it uses initramfs.cpio.gz.uboot

Also I would suggest to apply for i.MX6 training

i.MX 6 Series Processors Seminar|Freescale

Best regards

igor

[tony_l_cai]

Hi, igor

we use the same way to test uboot.bin in our custom board (Android 4.2), it can succeed to test u-boot.bin, but Android 5.0 cannot.

UL2.xml content is as below:

<LIST name="eMMC-Android-IMX6DL-SabreSD" desc="Choose eMMC as media">

  <CMD state="BootStrap" type="boot" body="BootStrap" file ="firmware/u-boot.bin">Loading U-boot</CMD>

  <CMD state="BootStrap" type="jump" > Jumping to OS image. </CMD>

  </LIST>

[igorpadykov]

you should rebuild all files in firmware folder firmware/u-boot.bin,

with specific settings for custom board.

~igor