Hi Manish,
I tried changing the device from F28035 to F28027 with the TMDSSOLARUINVKIT application from Controlsuite and getting some errors like , 'program will not fit into available memory etc.
Could you look into this.
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.
Hi Manish,
I tried changing the device from F28035 to F28027 with the TMDSSOLARUINVKIT application from Controlsuite and getting some errors like , 'program will not fit into available memory etc.
Could you look into this.
Hi Prasanna,
Prasanna Nambi said:I tried changing the device from F28035 to F28027 with the TMDSSOLARUINVKIT application from Controlsuite and getting some errors like , 'program will not fit into available memory etc.
There is a quite possibility that code developed for F28035 would not fit into F28027 as Flash memory in F28035 is double (128KB) than that in F28027 (64KB).
Regards,
Gautam
Gautam Iyer said:There is a quite possibility that code developed for F28035 would not fit into F28027 as Flash memory in F28035 is double (128KB) than that in F28027 (64KB).
Let's not speculate , please check the .map file of F28035 from my attachment and can see that the flash memory space utilized is still <64K.
name origin length used unused attr fill
---------------------- -------- --------- -------- -------- ---- --------
PAGE 0:
RAML3 00009000 00001000 00000abf 00000541 RWIX
OTP 003d7800 00000400 00000000 00000400 RWIX
FLASHH 003e8000 00002000 00000000 00002000 RWIX
FLASHG 003ea000 00002000 00000000 00002000 RWIX
FLASHF 003ec000 00002000 00000000 00002000 RWIX
FLASHE 003ee000 00002000 00000000 00002000 RWIX
FLASHD 003f0000 00002000 00000abf 00001541 RWIX
FLASHC 003f2000 00002000 00000000 00002000 RWIX
FLASHA 003f6000 00001f80 00001359 00000c27 RWIX
Hi Prasanna,
Prasanna Nambi said:Let's not speculate , please check the .map file of F28035 from my attachment and can see that the flash memory space utilized is still <64K.
I just checked your project and here are my observations:
1. The project includes "28027_RAM_lnk.cmd" file, which clearly mentions:
Whereas in the main.c you're using memcopy to copy contents to flash. So please work on this!
2. Your Target Configuration file is "xds100v1_F28035.ccxml" whereas you're building a project for F28027. So, debugging would never succeed.
3. Also, you're using "SolarMicroInv-DevInit_F2803x.c" file for Device initialization; please check whether F28027 is compatible to this or not.
4. If you check "SolarMicroInv-Settings.h" it mentions ePWM5,6,7 that doesn't even exist in F28027!
In short, I would like you to study F28027 controller thoroughly with sample examples and then try porting the code.
Regards,
Gautam
Gautam Iyer said:
These are actually two variants, one for the flash and the other for the RAM
Gautam Iyer said:3. Also, you're using "SolarMicroInv-DevInit_F2803x.c" file for Device initialization; please check whether F28027 is compatible to this or not.
This is the same file name carried over as but code have been modified to reflect the F28027.
Gautam Iyer said:4. If you check "SolarMicroInv-Settings.h" it mentions ePWM5,6,7 that doesn't even exist in F28027!
I believe you are referring to init file here , if you carefully look into the code you can see that
#ifndef DSP2802x_DEVICE_H
SysCtrlRegs.PCLKCR1.bit.EPWM5ENCLK = 1; // ePWM5
SysCtrlRegs.PCLKCR1.bit.EPWM6ENCLK = 1; // ePWM6
#endif
Also in the .h let us not be concerned about the ADCTRIG_EPWM6_SOCA, 7 etc the definitions doesn’t have to be deleted .That is not the answer to the issue we have here.
Gautam Iyer said:In short, I would like you to study F28027 controller thoroughly with sample examples and then try porting the code.
While I really appreciate your quick responses iam now concerned you are becoming a bottleneck for me in getting the right responses from TI experts.
The idea of posting an issue in the forum is to avoid reinventing the wheel, if you know something precisely you can support solve that issue.That is great,otherwise its better to refrain from jumping into a thread rather than providing half baked solutions
Prasanna,
I will suggest trying only the porting for FLASH only, I could not see the FLASH Cmd file in your attached document,
Post the FLASH Linker command and the exact errors you are getting, we can suggest some edits based on that..
Regards
Manish Bhardwaj
Thanks Manish, Attached the FLASH Linker command and error msg along with the modified project file.
1256.F28027_FLASH_SolarMicroInv.CMD.zip
Prasana,
Use FLASHC for the followings section
ramfuncs : LOAD = FLASHA,
RUN = progRAM,
Post the console error.. it will have description of exactly which section did not fit and by how much..
When I change the build option to closed loop (3) in settings i encounter error again
available memory. run placement with alignment/blocking fails for section
"ramfuncs" size 0x8d0 page 0. Available memory ranges:
progRAM size: 0x800 unused: 0x800 max hole: 0x800
Prasanna,
you can modify the following
progRAM : origin = 0x008000, length = 0x000900
..
dataRAM : origin = 0x008900, length = 0x000700
hopefully it will work..