Part Number:TMS320F280049
Hello,
customer has following questions
a) linker file:
- what is the reason of following instruction:
RESET : origin = 0x3FFFC0, length = 0x000002 als MEMORY und unter SECTIONS:
.reset : > RESET, PAGE = 0, TYPE = DSECT /* not used, */
b) linker file:
BOOT_RSVD : origin = 0x000002, length = 0x0000F3
- Customer want to change the length to 0x100 because of customer application alignment.
- Is this ok for the initialisation of MemCfgRegs.DxINIT? Because M0, M1 will be erased with INIT?
- Can it be used later in the application?
c) *headers_nonbios.cmd
- What is use of the GROUP with EmuKeyVar, EmuBModeVar, EmuKey FlashCallbackVar, FlashScalingVar?
- There is no different in the .out file if you comment it.
d) What is use of .reset in the boot28.asm file?
- there is no differences in the out file if you erase it in the linker memory and section part.
e) What is the use of the reserved PieVectTable [0, 1, 2]?
In the code example stands "Do not write over..."
f) in the C-examples you execute first InitSysPll() and then InitFlash().
- can the order be changes to InitRAM() (Eraser MemCfgRegs.DxINIT, copy ClaCode, copy RamFunc) then InitFlash and then InitSysPll()?
g) Customer has an own bootloader which is an own project.
- the bootloader program starts at 0x08‘0000 with own _c_int00() at 0x08‘1xxx. Then a CAN command leads to a jump to the application at _c_int00() at 0x08‘4000.
- Does it make sense to run through the complete init (c_init00(), InitRam, InitFlash, InitSysPll) again?
- or should the system init be locked in the bootloader?
If you like we can also discuss all this points in a confcall with the customer.
Regards, Holger
(Please visit the site to view this file)