• Locked Locked
  • Replies 11 replies
  • Subscribers 56 subscribers
  • Views 2513 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

About build errors in ccs

Megha shree
Prodigy 60 points
Other Parts Discussed in Thread: TM4C1294NCPDT

Hello,

I am not able to build a project which i created.I am getting gmake error.However,when I import a project from example codes i am able to build the project without any error.Please do suggest me as what might be the error.

  • TI__Guru**** 473001 points
    Hello,
    Have you seen the below link regarding gmake errors?
    processors.wiki.ti.com/.../Build_Errors_in_CCS

    If the suggestions in the link above do not apply, please provide more details about your error and environment.

    Thanks
    ki
  • Prodigy 60 points

    Hi,

    I am implementing 1-wire commynication protocol using CCSv6 as IDE and TIVA(TM4c1294NCPDT)controller.

    There are no build errors,But when i start debugging my code...step into n step over are working correctly..But at  some point of line of code,CPU will stop and ll get message as "NO source available for "0x1009fe2"..and in the disassembly window it will show "memory map prevented reading 0x1009fe2".One more thing is wen give full run..ll get directly dis message..wen step into ll get d message at some point of line in the code...

    What mite be the problem??Can u please help me out??

  • in reply to Megha shree
    Guru 42215 points
    What optimization level are you running? Turn it all off, rebuild and try again.
  • in reply to Megha shree
    TI__Guru**** 473001 points

    Megha shree said:
    "NO source available for "0x1009fe2

    This is not really an error but simply a message that the debugger did not find any related source code at the address the program counter is halted at. Whether or not this is an issue depends on your application and if you are expecting to have source code correlation at that address

    Megha shree said:
    "memory map prevented reading 0x1009fe2"

    The debugger memory map (what is a debugger memory map? See: http://processors.wiki.ti.com/index.php/Memory_map) is blocking debugger access to 0x1009f32. The debugger memory map has been configured so that it thinks that address is not a valid readable address. Often this happens when your applition hits some exception and "goes off into the weeds". Check your application and see if this is indeed a valid address and if not, why it is going out there

    Megha shree said:
    One more thing is wen give full run..ll get directly dis message..wen step into ll get d message at some point of line in the code...

    When you run, it will hit the exception and end up at that address. Single stepping will simply see all the actions that occur before the exception occur. By singles stepping, it should help you debug your application.

    Thanks

    ki

  • in reply to Ki
    Guru 92251 points

    Ki-Soo Lee said:
    The debugger memory map (what is a debugger memory map? See: http://processors.wiki.ti.com/index.php/Memory_map) is blocking debugger access to 0x1009fe2. The debugger memory map has been configured so that it thinks that address is not a valid readable address. Often this happens when your applition hits some exception and "goes off into the weeds". Check your application and see if this is indeed a valid address and if not, why it is going out there

    On a TM4C1294NCPDT with ROM revision 0x301 the address 0x1009fe2 is in the ROM_UARTCharPut function, and is therefore a valid address. Note that if the original poster is using a TM4C1294NCPDT with a different ROM revision the function at address 0x1009fe2 may be different.

    The ccsv7\ccs_base\emulation\gel\tm4c1294ncpdt.gel file in CCS 7.1.0.00016 defines the range of the ROM as:

        GEL_MapAddStr(0x01000000, 0, 0x00008c00, "R", 0);  /* ROM */

    The size of the ROM of 0x00008c00 bytes specified in the tm4c1294ncpdt.gel seems too small, as the ROM_UARTCharPut function which starts at address 0x1009fdc is beyond the size of the ROM specified in the GEL file.

    Based upon running a test on the TM4C1294NCPDT with ROM revision 0x301 I would say the actual ROM size is 0xe700 bytes, since when trying to read the ROM starting at address 0x01000000 a bus fault occurred at address 0x100e700.

    Should the memorymap_init() in the CCS GEL files for the TM4C129 devices be updated to match the actual ROM size?

    I have attached a test project used to report the address of the TM4C129 ROM API functions and ROM size. TM4C1294NCPDT_ROM_addresses.zip

  • in reply to Chester Gillon
    Prodigy 60 points
    Thanks for the suggestions Ki-soo lee and Chester gillon.
    I will try the above mentioned suggestions...
  • in reply to Megha shree
    Prodigy 60 points
    Hello Chester,
    How to knw the ROM version of TM4C1294NCPDT controller?
  • in reply to Megha shree
    Guru 92251 points

    Megha shree said:
    How to knw the ROM version of TM4C1294NCPDT controller?

    You can use the ROM_VERSION macro in the TivaWare driverlib/rom.h include file.

    The TM4C1294NCPDT_ROM_addresses.zip example project I attached above displays the value of the ROM_VERSION, along with the address of the the ROM functions.

  • in reply to Chester Gillon
    TI__Guru**** 473001 points

    Chester Gillon said:

    The ccsv7\ccs_base\emulation\gel\tm4c1294ncpdt.gel file in CCS 7.1.0.00016 defines the range of the ROM as:

        GEL_MapAddStr(0x01000000, 0, 0x00008c00, "R", 0);  /* ROM */

    The size of the ROM of 0x00008c00 bytes specified in the tm4c1294ncpdt.gel seems too small, as the ROM_UARTCharPut function which starts at address 0x1009fdc is beyond the size of the ROM specified in the GEL file.

    Based upon running a test on the TM4C1294NCPDT with ROM revision 0x301 I would say the actual ROM size is 0xe700 bytes, since when trying to read the ROM starting at address 0x01000000 a bus fault occurred at address 0x100e700.

    Should the memorymap_init() in the CCS GEL files for the TM4C129 devices be updated to match the actual ROM size?

    This is a good question and I don't have the knowledge for this device to comment definitely. I'll flag this for the TM4 folks to take a look

    Thanks

    ki

  • in reply to Ki
    Prodigy 60 points

    Hi,This is Megha.

    I am working on 1-wire communication protocol using TM4C1294NCPDT microcontroller and DS18B20 as temp sensor.I want to read 16-bit temperature data stored in the temperature register which has 2 separate registers for lsb bytes and msb bytes.Is there any built in function in CCS compiler for TM4C1294NCPDT controller, where i can combine the 2 8-bit temp data into one 16-bit data?