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.

crc_table() error on full section.

I try to calculate the crc of the .version section. The section holds one variable witch fills the hole section (20 bytes)

    .version        :   crc_table(crc_table) > VERSION

compling (arm_15.12.2.LTS) shows the following error:

"../test.cmd", line 103: error #10099-D: program will not fit into available memory.  placement with alignment fails for section ".version" size 0x14 .  Available memory ranges:
   VERSION      size: 0x14         unused: 0x14         max hole: 0x14      
error #10010: errors encountered during linking; "test.out" not built

According to the linker error, the fiting should be able, or not? 0x14 bytes should fit into a 0x14 hole.
Compiling without crc_table is working fine. I figured out, I need 4 bytes more iside the section for the crc_table to work.

Is it a bug?

  • I am unable to reproduce this same behavior.  Reproducing linker issues tends to be a bit more difficult.  This may take more posts than is typical.  Let's start with: Please send me the linker command file you use.  Attach it to your next post.  Because the forum is very cautious about attaching files, you ought to add the extension ".txt" to it.

    Thanks and regards,

    -George

  • I made the changes to the hello sample application.

    This is the error:

    "../CC1310DK_7XD.cmd", line 82: error #10099-D: program will not fit into available memory.  placement with alignment fails for section ".version" size 0x14 .  Available memory ranges:

      VERSION      size: 0x14         unused: 0x14         max hole: 0x14      

    error #10010: errors encountered during linking; "hello_CC1310DK_7XD_TI_CC1310F128.out" not built

    Regards

    Armin

    6366.helloWithBug.tar.gz

  • Thank you for submitting a test case.  I can reproduce the same results.  I filed a entry in our bug tracking system to have this investigated.  We are presently transitioning to a new system.  When I know how you can view this report, I'll let you know.

    Thanks and regards,

    -George

  • The SDOWP ID for this issue is CODEGEN-25.  You are welcome to follow it with the SDOWP link below in my signature.

    Thanks and regards,

    -George