• State Resolved
  • Locked Locked
  • Replies 12 replies
  • Subscribers 54 subscribers
  • Views 248 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.

CC1312R: 1312 15.4 collector oad Migration Issues

faker wang
Intellectual 446 points
Part Number: CC1312R

Hi guys:

I have used the architecture pattern of CC1312 15.4 protocol stack collector and sensor, and adopted the latest official SDK. I have basically completed my business, and currently there is one last function point that I need your help with:

I have already ported the load related logic of the sensor to the collector off chip load function, but I have attempted to port the cc13x2 of the sensor_ Cc26x2_ OAD_ Offship_ Tirtos7.cmd file and cc13x2 in collector_ Cc26x2_ Porting the differences in the tirtos7.cmd file to the collector project,

But if I directly download the out file compiled by the collector project in CCS, it will cause the development board to fail to enter the system correctly after power failure_ Burning the BIM project and collector. bin together into the development board can cause even more abnormal situations in the system, such as UART printing CUI related logs (I have disabled the CUI function)

May I know how to port CC13x2_ Cc26x2_ OAD_ Offship_ Is the tirtos7.cmd file sufficient to ensure proper load functionality for collectors? Here is a screenshot of the file I ported. Please give me some help, thank you

  • 0
    TI__Mastermind 20402 points

    Hi,

    Do I understand correctly that the customer wants to generate a collector OAD image? that the customer wants to update a collector over OAD?

    If this is the case, we do not support this. 

    Regards,

    Sid

  • 0 in reply to Sid
    Intellectual 446 points

    Hi:

    Yes, the customer wishes to generate an OAD image and update the collector's code through UART, making it easier to dynamically add or update functions to the collector after deployment to the on-site environment，

    Hope to provide some help

    Regard

  • 0 in reply to faker wang
    TI__Mastermind 20402 points

    Hi ,

    Is it necessary to use BIM? or do you just want to use the Serial bootloader?

    https://www.ti.com/lit/an/swra466d/swra466d.pdf

    Regards,
    Sid

  • 0 in reply to Sid
    Intellectual 446 points

    Hi Sid:

    Thank you for your prompt reply. I have read the document you provided.

    Our scenario is a complex factory scenario, and there will be many collectors connected to our embedded gateway in the on-site environment. In the future, we hope that the collectors can switch to sensor nodes in certain specific situations. In this case, BIM's solution seems to be more suitable for our scenario.

    Regards

  • 0 in reply to faker wang
    TI__Mastermind 20402 points

    Hi, 

    The changes between OAD and non OAD projects are as you correctly pointed out, linker file to locate the OAD headers and accommodate BIM.

    So, I would suggest you to diff the linker cmd files of Sensor and sensor_oad_offchip to get the difference and apply the same on the collector example.

    If the OAD headers are applied to the collector image, I would assume that the BIM should be able to evaluate the image and boot into it. So this procedure should be same as the sensor example. 

    Please make sure that there is sufficient Flash space to accommodate BIM+collector image on the device.

    faker wang said:
    But if I directly download the out file compiled by the collector project in CCS, it will cause the development board to fail to enter the system correctly after power failure_ Burning the BIM project and collector. bin t

    In this case, could you debug and identify if the system is executing BIM or if it is failing even earlier than that?

    Regards,
    Sid 

  • 0 in reply to Sid
    Intellectual 446 points

    Hi Sid:

    I have already ported the load related functions of the sensor to the collector, and the cmd file has also been successfully ported,,

    After completing the load process, I have already received a prompt of Completed Successfully

    But after the device restarts, it still applies to the old code (I observed that the SOFTWARE_VER version number in load_image_header.app is still the version number before the upgrade). How should I locate the problem in this situation? Can you provide some assistance?

    Regards

  • +1 in reply to faker wang
    TI__Mastermind 20402 points

    Hi,

    That is great that you have been able to load the images already. 

    faker wang said:
    But after the device restarts, it still applies to the old code (I observed that the SOFTWARE_VER version number in load_image_header.app is still the version number before the upgrade).

    If you are not getting the new image to load, this is something that the BIM decides. 

    you can try debugging the BIM project. While debugging, in the debug configuration, select the option to only load symbols so that the bim + collector image is not overwritte. 

    You can right click the project -> debug as -> debug configurations. In the Program sub window, select load symbols only. 

    Debug the project. You can then check what is happening in the function Bim_checkImages. 

    This should give you an idea about why it is failing to boot into the collector image. 

    Regards,

    Sid

  • 0 in reply to Sid
    Intellectual 446 points

    Hi Sid:

    I debugged the BIM project, Will return a failure at the extFlashVerifyPart() function

    For some unknown reason, I am unable to place the breakpoint on line 311 (it will automatically cancel and help me place it on line 312)

    I checked the data on line 312, and the value of pFlashInfo ->deviceSize is 0. It can be seen in the memory browsing on the right as well,

    1. May I ask which piece of content is this function used to compare?

    2. If the optimization level is changed to 0, there will be no issue of inaccurate rows during debugging. However, the modification will prompt an error. Is this error caused by insufficient flash space reserved in the BIM project? But if I modify the flash size in the cmd file, it seems to cause a chain reaction (so my main project also needs to be modified). Can you give me some help? Thank you

  • 0 in reply to faker wang
    Intellectual 446 points

    Hi sid:

    Supplementary text

    My code returns false in extFlashOpen() in the checkImagesExtFlash function

  • 0 in reply to faker wang
    Intellectual 446 points

    Hi sid:

    Solved. Thank you for your support

    Regards

  • 0 in reply to faker wang
    TI__Mastermind 20402 points

    Hi,

    Thank you for the update. Please can you mention what was the issue?

    Regards,

    Sid

  • 0 in reply to Sid
    Intellectual 446 points

    Hi:

    Our external flash model for the device is optional, so I have modified it here

    Thank you for providing the ideas

    Regards