From datasheet of Creating a Second-Level Bootloader for FLASH Bootloading on C6000, I see that:

What about C6747? Does somebody have an example of C6747 boot from flash?
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.
From datasheet of Creating a Second-Level Bootloader for FLASH Bootloading on C6000, I see that:

What about C6747? Does somebody have an example of C6747 boot from flash?
jc said:Please see the Bootloader Application Report on the product page for the C6747 boot process.
Jeff
Do you mean the document( Using the TMS320C6747/45/43 Bootloader)? I only find this. In this document, there is:

So I think C6747 DMA copies 16KB from 0x11800000. When compression optios is used, it copies 64KB. I don't know whether what I understand is right or not, and What does compression mean?
In some second-level codes, I see there are .option, .length and .width commands. For What they are used?
Can you give me some more information on your application?
1) What boot mode are you using?
2) What silicon revision are you using? You can use this GEL file: http://processors.wiki.ti.com/index.php/OMAP-L1x_Debug_Gel_Files
Jeff
jc said:Can you give me some more information on your application?
1) What boot mode are you using?
2) What silicon revision are you using? You can use this GEL file: http://processors.wiki.ti.com/index.php/OMAP-L1x_Debug_Gel_Files
Jeff
1). I am using NAND FLASH(8 bit).
2). What is silicon revision?
for NAND FLASH(8 bit), Is it right that C6747 DMA copies 16KB from 0x11800000? My application program is ok using JTAG. But when I burn it to flash, the program can't run. I don't know why.
Are you using the GEL file to perform some device initialization that is not happening in your standalone application? That might be the issue.
Did the bootloader complete and jump to execute your application, or was there an error during the loading process? Please provide a printout of the GEL output when connecting after booting so we can determine this.
You can also load the symbols for your app, put a break point at the start, and reset the board. This should let you step through the code.
Jeff
Actually, my codes can run from nand flash. I just don't know how bootloader of C6747 works and how many codes are copied when the bootloader is working. Thank you all the same.
This device does not support direct NAND booting. The bootloader will copy the entire boot image to memory and execute from there. If you are having an issue, it could either be because the image did not copy correctly or that the image executed and did not initialize something like it should have. The debug GEL file will let you know the answer to that question.
Jeff
Hi,
Below is described in SPRABB1C.
NOTE: The compression option is only available for devices with the d800k001 ROM revision. See
the introduction for instructions to check your device’s ROM revision.
Using the TMS320C6747/45/43 Bootloader (Rev. C)
http://www.ti.com/lit/an/sprabb1c/sprabb1c.pdf
9 Boot Requirements, Constraints and Default Settings
Is my understanding below correct?
For the d800k003 and later ROM revision, the memory which is 64 KB of DSP L2 RAM starting from 0x11830000 is not used by the bootloader.
This memory can be used by any section of the user application.
Best regards,
Daisuke