• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 31 subscribers
  • Views 286 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:

LAUNCHXL2-570LC43: Time to toggle a GPIO pin

LAUNCHXL2-570LC43: Is Halcogen BSP errata compliant?

Durga Choudhury
Intellectual 380 points
Part Number: LAUNCHXL2-570LC43
Other Parts Discussed in Thread: HALCOGEN

Is the BSP generated by Halcogen compliant with, e.g. spnz232b for the TMS570LC43? Is it errata compliant with other members of the Hercules family (that are supported by Halcogen)? If so, is it fully compliant or are there gaps the designer is supposed to fill in by hand? Is it compliant both for stand alone BSP and FreeRSTOS BSP? If it is NOT compliant, is there any guidance available from TI as to how to make a Halcogen generated BSP compliant?

  • 0
    TI__Guru 69891 points

    Hi Durga Choudhury,

    It depends on the silicon revision you are using!

    If you use latest one then you can find what are the fixes of the errata they had done.

    So, please verify the corresponding datasheet.

    --

    Thanks & regards,
    Jagadish.

  • 0 in reply to jagadish gundavarapu
    Intellectual 380 points

    Hello Jagadish

    Thank you for your reply; however, this is not what my question was. Perhaps I did not make it clear enough.

    I am using silicon revision B. (I suppose revision A is too old and no supplier carries it anymore). Given that revision B *still* has an errata associated with it (as is described in document spnz232b), is the code generated by halcogen also generates code to satisfy the errata (and all the other similar questions I asked in the original post; I don't want to repeat them). I see one halcogen-generated file that takes into account the PLL stalling errata, but there are others also. I have not looked too closely, matching the generated code line for line with the errata, but I figured it would be faster to just ask the people who write the documents and the code generators.

  • 0 in reply to Durga Choudhury
    TI__Guru 69891 points

    Hi Durga,

    I forwarded to senior expert for help, please expect some delay in the response.

    --

    Thanks & regards,
    Jagadish.

  • 0 in reply to jagadish gundavarapu
    Intellectual 380 points

    Hi Jagadish

    Thank you for your help; I appreciate it and looking forward to the response from the senior engineer. For safety critical designs, this information matters a lot.

    Best regards

    Durga

  • +1 in reply to Durga Choudhury
    TI__Guru**** 196566 points

    HI Durga,

    The HALCOGen code doesn't implement the workarounds for all the bugs listed in the device errata. The application has to implement the workaround recommended in device errata. Several bugs don't have workaround, for example NHET nay bot capture small pulse correctly, so the application should not use the PCNT to capture a small pulse.

  • 0 in reply to QJ Wang
    Intellectual 380 points

    Thank you for the clarification, QJ.