• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 79 subscribers
  • Views 1101 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.

LP-MSPM0C1104: EEPROM emulation SDK

Kenley
Intellectual 1805 points
Part Number: LP-MSPM0C1104
Other Parts Discussed in Thread: LP-MSPM0G3507, MSPM0L1306, SYSCONFIG

Hi team,

My customer is evaluating LP-MSPM0C1104 and want to use EEPROM Emulation SDK but they could only find the SDK inside LP-MSPM0G3507 launchpad SDK.

Could they use the SDK in LP-MSPM0G3507 and use it on their LP-MSPM0C1104?

What kind of modification they need to use it ?

Note: they are mainly using uart_echo_interrupts_standby.c SDK and want to add the EEPROM emulation function inside it.

Thank you in advance.

Best regards,

Kenley

  • 0
    TI__Mastermind 39835 points

    Please refer to this:

    Device Migration Recommendations

    This project was developed for a superset device included in the LP_MSPM0L1306 LaunchPad. Please visit the CCS User’s Guide for information about migrating to other MSPM0 devices.

    I would suggest they move the uart example code into EEPROM emulation. It will be much easy, as they don't need to handle the data structure.

  • 0 in reply to Eason Zhou
    TI__Intellectual 1805 points

    Hi Eason,

    Thank you for your support.

    Do you mean this part in the CCS user's guide ?

    Sorry but could you please elaborate more on the following ? 

    Eason Zhou said:
    I would suggest they move the uart example code into EEPROM emulation. It will be much easy, as they don't need to handle the data structure.

    Thank you in advance.

    Best regards,

    Kenley

  • +1 in reply to Kenley
    TI__Mastermind 39835 points

    Hi Kenley,

    I look into more details of the code example of EEPROM. I think the easiest way is to load the EEPROM library into the UART example, because the EEPROM example don't have sysconfig.

    The key point is that, you may need to update the address to put the EEPROM at the last of the memory, in order to avoid the code will overwrite the EEPROM area. As the default EEPROM_EMULATION_SECTOR_ACCOUNT is 2, that means the used memory is 2KB. 

    Eason

  • 0 in reply to Eason Zhou
    TI__Intellectual 1805 points

    Hi Eason,


    Thank you for your support.

    I am going to recommend customer to move UART SDK to EEPROM.

    It would be much appreciated if you could give a guide to customer on how to move it ?

    In my understanding, we need to move the driverlib to the EEPROM.

    Thank you in advance.

    Best regards,

    Kenley

  • 0 in reply to Kenley
    TI__Mastermind 39835 points

    Please check my latest comment is " I think the easiest way is to load the EEPROM library into the UART example". 

    For how to load the EEPROM library, please refer to the eeprom_emulation_type_a/eeprom_emulation_type_b

    If they meet any more problem, we can help them solve it.

  • 0 in reply to Eason Zhou
    TI__Intellectual 1805 points

    Hi Eason,

    Noted. Thank you.

    1. By the way i want to confirm too about the EEPROM Type B SDK.
    I have tried to debug it and it stopped in the reset handler as shown as the following.
    it won't move on to the main.c.
    Is it right behavior for this SDK ?

    2. And in the readme.html inside the SDK, it is written that it will be stopped in the breakpoint so we could verify the values.
    However as I clicked resume button, it never stops in the breakpoint as said in the example usage.
    Should i set the breakpoint manually ? if yes, which line should i set the breakpoint so i could verify the value as mentioned ?

    Thanks.

    Regards,
    Kenley

  • 0 in reply to Kenley
    TI__Intellectual 1805 points

    Hi Eason,

    I successfully move to main.c but after i move on to SYSCFG_DL_init();,

    suddently default_handler is being called and can not get out of the loop.

    When i commented out the following function, it could go back again to main and proceed the code.

    SYSCFG_DL_initPower();

    And i found out that after the following function is called, it will go to default_handler.

    Best regards,

    Kenley

  • 0 in reply to Kenley
    TI__Mastermind 39835 points

    Can you share your project. I can check for you.

**Attention** This is a public forum