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.
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.
load address of uninitialized section ramfuncs ignored
hi! i'm gaton and i have a ezdsk 28335, i try to run a simple program ("hello world") and when a compile this error apears, somebody knows what to do? the add files are: rts.2800_mLeh.lib, F28335.cmd and the c source #include <stdio.h> // include the standard I/O functions void main() { printf("Hello World\n"); } Thanks
I suspect you get this warning because your linker command file defines a section "ramfuncs" for functions that are to be copied from flash to RAM before they are used. Your example project does not have any functions assigned to that section. You can get rid of that warning by commenting out the corresponding lines in F28335.cmd.
I don't know how you managed to get your code linked to that address. 0x388a66 does not belong to an address region with RAM or Flash. It's marked 'reserved'.
I'd suggest you google for sprc530 and try to make those examples work according to the guide that comes with sprc530.
i'm new in this, could you tell how can i do this program, because i
don't know how to make the .cmd. I search in the web for examples, but
i'm interesting in build it. With the c source i don't have problems,
and the library add from the folder code composer (c2000).
it seems you modified the cmd linker file and made the linker link the code at a wrong address, maybe just a type mismatch: FLASHA sector start from 0x338000 not 0x388000, later the programmer tried to program that address and failed the verify step cause actually no code could be flashed at that location.
You can use the cmd file you got with the ezdsp evaluation board as a template to build your own: you can find good explanations on how the linker works in the assembly and language tools manuals.
Usually the cmd linker file you get with the evaluations board works as is but is intended to link all the compiler generated code sections in FLASHA sector which become quickly too small as your application code grows. Build a very simple application even an empty main function can be enough so you don't have to care about where the printf function in your "hello world" program is allocated, build it with the original cmd file and have it linked properly with no warnings then try to modify cmd sections until you can have the code running from the address you choose. With some simple tries you can understand how things works and have your own cmd file.
Code can be allocated almost anywhere into the flash address space, just check if the boot loader code entry point is set the jump to the correct starting location. Though if you are planning to use some of the code libraries and examples provided as support, some conventions are used: as far as I know, FLASHD sector is usually used to store code that will be executed from ram and FLASHC is used to store IQmath functions. Of course nothing prevent you from moving them around too.
If you are planning to run your code from flash without using the CCS running as degugging tool check if the linker autoinitialization options is set properly, otherwise program variables won't be initialized and probably you won't be able to have your code running properly. While using the CCS for debugging the initialization and the setting of the code start are done under the hood so it took me a while to understand what was missing the first time I tried to run the code from flash on a stand alone target board.
