Dear igorpadykov
Can I ask you to do me a favour? I already fill in LPDDR2 parameters into "imximage.cfg" refer to "linux/board/freescale/mx7ulp_arm2 imximage_lpddr2.cfg" as you mentioned previously, but now I face another problem is the u-boot stuck and it doesn't show any message at UART port on my_customer board during boot stage.
Because my_customer board is boot from uSD-Card, so I measured both "CLK" and "DATA0" signals on uSD-card to confirm u-boot process is fail.
I find that "CLK" and "DATA0" signals will continue normal active on NXP-EVB during boot stage (fig 1.) ,but both these two signal on my_ customer board only active at the beginning during boot stage and then will STOP (fig 2.) .
fig 1 . Red : DATA0 Green: CKL on NXP -EVB during boot stage.
fig 2 . Red : DATA0 Green: CKL on MY- Board during boot stage.
these are what I modified in BSP as below :
1. change setting in "mx7ulp_evk.c" uart port to match my_customer board design.
2. imx7ulp.dtsi(in U-boot) (for match my_customer design)
3. imx7ulp-evk.dts(in U-boot) (for match my_customer design)
4. imximage.cfg.
5. And I re-build "bitbake u-boot-imx" with no error.
My question is shown as below :
1. Actually ,relate to porting DDR process in the "i.MX BSP Porting Guide" only mention in chapter "3.2.1 Changing the DCD table for i.MX DDR initialization " , it's just indicate that we need to modify my_board.cfg.
I really want to known is HOW should I do to fill in DCD table parameters refer to RealView.inc ?
Is these any document can show more detail about modify the DCD table?
2. Whether the modified of device tree in u-boot source file will cause a u-boot fail?
( The modified "u-boot-imx" image doesn't show any error message when I re-build it . )
3. According to fig 2. wave form ,could you give me some tips about this case ? Is the DCD table configuration mistake cause this case ?or device tree configuration mistake in u-boot source code?
Thanks.
