• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 171 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.

Original question:

IWR1843BOOST: Understanding mmWave SDK exceptions

IWR1843AOP: mmWave SDK exceptions

ML
Prodigy 30 points
Part Number: IWR1843AOP
Other Parts Discussed in Thread: SYSBIOS

Tool/software:

I am still struggling with understanding TI RTOS exceptions on mmWave SDK 3.6.2 LTS. I made a post here a while ago:

https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1460694/iwr1843boost-understanding-mmwave-sdk-exceptions

But now I have been getting error in module 44. Unfortunately the workaround I found does not help because 44 does not exist in the configuration package. I have used ChatGPT in some occasions and it knows some modules by number, but not this.

I must say that it has been very frustrating experience of developing software on TI mmWave devices. I cannot understand how could anybody work on the platform which does not have a proper documentation of the error codes and only way to get issues solved is to do trial & error and revert the changes. It takes ages to develop.

  • 0
    TI__Mastermind 19450 points

    Hello.

    As I noted in the previous E2E thread, these are not SDK specific errors but rather errors associated with SysBIOS.  You may be hard faulting or dealing with another type of error.  I would recommend you step through your code via CCS debug to see where it is getting stuck to get a better idea of the error you are dealing with.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Prodigy 30 points

    Unbeliavable. How can you not explain your own system?

    Yet again, I found a better way myself: Build system generates run-time analysis (RTA) file called config\configPkg\package\cfg\target_per4ft.rta.xml which contains module identifiers and names in XML format. The 44 i looked for is an exception handler module:

    <modMap key="ti.sysbios.family.arm.exc.Exception">
      <id>44</id>
      <logger>null</logger>
      <diagsMask>0000110000000000</diagsMask>
    </modMap>

    Of course analysing the errors with debugger is better, but that's only possible in the lab, not on field.

  • 0 in reply to ML
    TI__Mastermind 19450 points

    Hello.

    I understand your frustration; however, let me clarify that this is NOT a mmWave error but a SYS/BIOS error and is beyond the scope of the mmWave SDK.

    SDK 3.6.2 uses an older version of the TI-RTOS kernel called SYS/BIOS.  These are XDC/SYSBIOS exceptions not mmWave SDK exceptions.  In addition, it is better to debug all these errors you are encountering in the lab before sending it out into the field for testing; we cannot support core-level or RTOS-level crashes but if you are able to run the debugger we will be able to at least see where your code is crashing and determining what changes may have caused a problem that resulted in this exception. 

    If you really want to dig into the exceptions that you are encountering, you can look in the bios_6_73_01_01/docs/ folder, which should be installed along with your SDK 3.6, for any information.  However, at a preliminary glance it doesn't seem to have the information you are looking for; the file generated from your build may be more useful.  Again, as I emphasized last time, please try running your code using CCS Debug so that I can have a better understanding of what changes you made that may have generated these errors.

    Sincerely,

    Santosh