• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 39 subscribers
  • Views 1261 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Enabling Driverlib in ROM

Fadleen Sidek
Prodigy 120 points
Other Parts Discussed in Thread: CC3200

Hi All,

I have 3 qns.

1. Are the examples provided  eg blinky,PWM utilizing driverlib from RAM or ROM?

2. How do i use the driverlib from ROM in my project? The documentation states to put TARGET_IS_CC3200 in the project file. Does it mean i need to put a #define statement in my main.c file and also define the statement in the Linker and Compiler section(under Options) of EWARM?

3. Will the .bin img be smaller as compared to using driver lib from RAM?

Thanks in advance..

  • 0
    TI__Expert 5660 points

    Hi Fadleen,

    Currently all the examples provided link to driverlib from RAM. Next SDK release will have one example which demonstrates linking to ROM.  Note that the current pre-production device ES 1.32 would have older ROM so lot of API's might need to be patched in order to match the API's in RAM. So You should try linking with ROM driverlib from production device ES1.33 onwards. Next SDK release will also have list of API's that need to patched for the ES 1.33 Device ROM.

    Refer to section "6.2 CC3200 Peripheral Driver Library Services in ROM" of CC3200-Programmers_Guide.pdf for details about ROM driverlib linking.

    Yes output.bin generated by linking with ROM driverlib would be smaller than the one generated by linking with RAM driverlib.

    Thanks and Regards,

    Siddaram 

  • 0 in reply to Siddaram Mathapathi
    Prodigy 120 points

    Hi Siddaram,

    Thank you for the detailed response.

    Just to verify. The device i have is currently ES1.32. Does this mean that in order to run driverlib from ROM without patching, the new SDK must be eg 0.5.3 or 0.6.0.(I dunno)..+ silicon ver 1.33?

    The new sdk + ES1.32 wont work? Still requires patching?

    Cheers,

    Fadleen....

  • 0 in reply to Fadleen Sidek
    TI__Expert 5660 points

    Hi Fadleen,

    We plan to support the ROM driverlib as below

    Take a purely hypothetical case that Driverlib version x.y.1 was added to the ES 1.33 ROM and the driverlib which is part of SDK is version x.y.9. The delta between x.y.1 to x.y.9 was that 20 API's were changed/fixed. If we want to use ES 1.33 ROM driverlib then these 20 API's need to be patched. The patching infrastructure works such that bug fixed 20 API's would be linked from RAM and rest all API's would be linked from ROM. In the next SDK we will support this Patch list corresponding to ES 1.33 ROM. To put it in other words.

    SDK latest driverlib = ES 1.33 ROM driverlib + Patch list corresponding to ES 1.33 ROM

    In theory it is possible to make the below equation work as well, However the patch list corresponding to ES 1.32 ROM would be long and we never planned to support it.

    SDK latest driverlib = ES 1.32 ROM driverlib + Patch list corresponding to ES 1.32 ROM

    Please see if this helps.

    Thanks and Regards,

    Siddaram

  • 0 in reply to Siddaram Mathapathi
    Prodigy 120 points

    Hi Siddaram,

    Noted and thanks..

    Fadleen..