Hi,
I am using TMS320c5515 development kit with ccs version 4. I have used TCF file to create tasks, semaphores and mutex and also using Tcf I am creating a buffer pool of different sizes and trying to allocate the memory from this pool using BUF_alloc. Memory heap has been enabled. Memory model selected is large. While Linking I am getting these warnings and errors.
warning: creating output section ".vector" without a SECTIONS specification
warning: creating output section "vector" without a SECTIONS specification
"./simple_plaincfg.cmd", line 268: error: placement fails for object ".text", size 0x20c0b (page 0). Available ranges: DARAM size: 0xfe40 unused: 0x1808 max hole: 0x1802
"./simple_plaincfg.cmd", line 322: error: placement fails for object "GROUP_1", size 0x1227a (page 0). Available ranges: DARAM size: 0xfe40 unused: 0x1808 max hole: 0x1802
warning: entry-point symbol other than "_c_int00" specified: "reset_isr"
error: errors encountered during linking; "Simple_Application.out" not built
Can anyone please help me out with the answers for it?
Thanks and Regards,
Taranum
Hi Taranum,
These errors indicate that the memory segment DARAM is all used up. According to the message, the ".text" section is size 0xfe40; however there is only 0x1802 bytes left in in DARAM.
In order to fix this, you should try re-arranging various sections into other memory segments. This can be done in your *.tcf file in the MEM manager properties:
(I'm having trouble attaching a screen shot so I'll reply to this post with one...)
Steve
Hi Steve,
Thank you for the answer. It solved the problem of text section. But how about this problem "placement fails for object GROUP1"? Does this also mean the same thing? If so how and which segment should i select for this?
Taranum,
I think the GROUP_1 is coming from your linker command file (simple_plaincfg.cmd). Can you check to see what GROUP_1 shows in that file? (It should list some memory sections inside a block called "GROUP_1").
Once you see the memory sections listed in it, you can place those ones into a different memory segment in a similar way as you did for .text.
I selected SARAM section for .CONST and .printf section and this group_1 error was resolved. Thank you so much for your guidance.
And also what do these warnings represent? For the first warning, should I specify a memory section for .vector? If yes, then which section should i go for .vector?
Regards,
Are you using a custom linker command file? If so, can you please attach it?
Taranum Sultanawarning: creating output section ".vector" without a SECTIONS specification
This is probably caused because your linker command file does not specify which memory segment the ".vector" section should be placed into.
Taranum Sultanawarning: entry-point symbol other than "_c_int00" specified: "reset_isr"
Typically the entry point for a program is at the symbol "_c_int00". This warning is telling you that it has been changed to be the symbol "reset_isr". Perhaps you made this change intentionally? If so, this should be OK
Hi steve,
Here is the linker command file.
Thank you for attaching the linker command file. But, has your problem been resolved? I see that you marked my previous post as "verified".
I am extremely sorry that. That problem is not yet resolved.
Can you please guide me for those .vector section warnings?
I'm not sure what the .vector section is, but this warning means that you need to ensure that the .vector section is being placed into a memory segment.
For example, the TMS320C55x Assembly Language Tools v 4.4User's Guide (http://www.ti.com/lit/ug/spru280i/spru280i.pdf)
shows this example of default placement. I suspect you need something similar.
Example 9-18. Default Allocation for TMS320C55x Devices
MEMORY{ROM (RIX) : origin = 0100h, length = 0FEFFhVECTOR (RIX) : origin = 0FFFF00h, length = 0100hRAM (RWIX) : origin = 010100h, length = 0FFFFh}SECTIONS{.text > ROM.switch > ROM.const > ROM.cinit > ROM.vectors > VECTOR.data > RAM.bss > RAM.sysmem > RAM.stack > RAM.sysstack > RAM.cio > RAM}
It may be helpful to attach your *.map file at this point, as well.
Hi Steve,Here is the *.map file.Regards,Taranum
Are you building for the MSP430? I see from the map file that the .vector coming from from an msp430 UART file:SECTION ALLOCATION MAP(Addresses surrounded by []'s are displayed for convenience only!)output attributes/section page orgn(bytes) orgn(words) len(bytes) len(words) input sections-------- ---- ----------- ----------- ---------- ---------- --------------.....vector 0 0000e6fe [ 0000737f ] 000005d7 * 0000e6fe [ 0000737f ] 000005d6 * msp430_uart.obj (.vector:_isr) 0000ecd4 [ 0000766a ] 00000001 * --HOLE-- [fill = 20]vector 0 0000ed00 [ 00007680 ] 00000100 * 0000ed00 [ 00007680 ] 00000100 * vector.obj (vector).hwi_vec 0 0000ff00 [ 00007f80 ] 00000100 * 0000ff00 [ 00007f80 ] 00000100 * simple_plaincfg.obj (.hwi_vec)Do you know where that file is coming from?Steve
I am using vector.asm file for uart isr. And that MSP430_uart.c file is replaced for c5515 functionality. Now when I am trying to debug the code (single step) I am getting JVM heap detected low ( You can Increase the JVM heap by changing the XMX option in eclips.ini file, after which the ccsv4 stops responding. Earlier it was xmx256m, now I have changed it to xmx512m. Is that correct?
I think you just need to add a SECTIONS specification to your linker command file that places the ".vector" section into the memory segment that you want in order to get rid of the warning.
For more information about linker command files, please refer to the following doc in Section 7.5:
http://www.ti.com/general/docs/lit/getliterature.tsp?baseLiteratureNumber=spru186&fileType=pdf,
Regarding the JVM heap issue, yes I believe you have changed the heap size correctly. Note that I saw another post a customer recommnded the following website for tuning eclipse:
http://www.eclipsezone.com/eclipse/forums/t61618.html