- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Hi team,
Boot using SPI norflash, which is able to boot when the program is running in SL2. However, when the program is running on DDR, the boot fails.
1) The project used is the UART routine in 7242.K1_STK_v1.1. When DDR is not used, data can be output through the serial port after burning and re-powering up.
2) Add spiboot.c in C6657_directROM_Boot_example in the UART project, i.e. add the field configuration for emif4Cfg. Also add the appropriate configuration to the cmd file, as shown in the following figure:
However, after a successful build, DDR_CFG is not used and the program still cannot run though it has been burned.
Could you help look into this case? Thanks.
Best Regards,
Cherry
Hi Leonard,
Thank you for the support.
What processor is this for?
tms320c6672.
And please let me elaborate more on the issue now:
1) The previous register configuration for DDR register addresses DDR (0x21000000 to 0x21000020) was not correct because the customer used DDR with a configurator table of 6657, two more UINT32 types of data. The register configuration for DDR (0x21000000 to 0x21000020) after the change is ok.
2) But the 4 registers at the beginning of 0x02620330 do not match the values initialized with gel, causing the program to now burn in but not start. Here are the configurations for DDR:
3) Is the PLL configuration for DDR configured with the values pllPrediv, pllMult, pllPostDiv above? Customer's DDR reference clock is 66.667 MHz. However, the program burned in does not start at this time (the program runs in DDR). While it is ok to start the program when it is running in SL2. The following is the cmd file configuration when running in DDR:
Thanks and regards,
Cherry
