This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OMAP-L137: Problem to run bootload under I2C0 Master mode

Part Number: OMAP-L137
Other Parts Discussed in Thread: XDS510, TMS320C28346

1. Product development based on OMAP-L137 (hereinafter referred to as L137 or C674X)
1.1 L137 hardware resource usage 

C674X on L137 is used, ARM on L137 is not used;
24C512 based on I2C communication interface for The external code memory adopts;
No external NAND Flash based on EMIFA interface is configured;
There is no external SDRAM based on the EMIFB interface.

1.2 Software
Self-developed software based on C674X, Linux/OS from TI not used.

1.3 Development status
It runs well under the XDS510 emulator and CCS4 environment.

2. Problem
Can not run the BootLoad based on I2C0 Master mode, can not run separately without using the simulator and CCS4 environment.
2.1 Startup mode
I2C0 Master;
2.2 BOOTCFG (address ox01c14020) value
The value read by BOOTCFG is 0x0000F370, which is consistent with the requirements of I2C0 Master mode;
2.3 Feedback on debugging
By tracking the startup code running (entry address 0x11700000), it is found that it may be based on I2C
The code data on the external 24C512 memory of the interface is not loaded into the internal RAM.
2.4 Reference
TMS320C28346 is also used on the same product, which also uses an external I2C interface
The 24C512 memory is capable of boot loading and self-starting operation.

3. Problem solving
Based on OMAP-L137 products, after years of development and investment of a large amount of resources, the research and development has been completed and the production will be soon.
At present, only the BootLoad of L137 C674X has not been solved. Hope this problem can be solved as soon as possible.


4. Reference materials
4.1 C6000_20211011.out
C674X-based execution code compiled by ccs4;
4.2 C6000_20211011.bin
Convert C6000_20211011.out to .bin format on AISgen for D800K005
Files loaded on I2C EPROM.
4.3 OutToBin.jpg
The conversion environment from .out to .bin.
Note: Reading the data at position 0x11700008 shows that L137 is the D800K003 version, so the version parameter setting
As shown in the file. The environmental parameters have also been set in other ways, and none of them have realized self-starting operation after testing.
4.4 L137.cmd
The cmd file under ccs4.
4.5 evmomapl137_dsp.gel
The initialized .gel file actually re-initializes the hardware after entering the software code.
The gel file basically didn't work.

Note: if the problem can be solved by using C6747 instead of OMAP-L137, we would likt to try that too.

Really appreciate if any comments or help. Tons of thanks.

  • Hello Shawn,

    A few questions to help me understand your situation:

    Can not run the BootLoad based on I2C0 Master mode, can not run separately without using the simulator and CCS4 environment.

    Did you mean here that you can load and run your program using CCS and JTAG emulator?

    Files loaded on I2C EPROM.

    What tool did you use to write your program to EPROM?

    4.5 evmomapl137_dsp.gel
    The initialized .gel file actually re-initializes the hardware after entering the software code.
    The gel file basically didn't work.

    Were you talking about development phase using CCS and JTAG, or production phase when booting from I2C? If it's the production phase, you should not use .gel file.

    Thanks and regards,

    Jianzhong