• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 29 subscribers
  • Views 161 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.

Original question:

Unclear requirements for TMS570 initialization sequence

TMS570LS1227: Query regarding TMS570LS1227 initialization sequence

Vimal N
Prodigy 80 points
Part Number: TMS570LS1227
Other Parts Discussed in Thread: HALCOGEN, TMS570LC4357

Hi,

I am using the SPNA106D Application Report for initialization of the TMS570LS1227 controller and have queries regarding the following steps:

44. Verify that the dual-clock-comparator (DCC) module can actually detect and flag a frequency error
Would this involve setting the Counter0, Counter1 and Valid0 values so that the following error conditions are generated:
a. Counter1 counts down to 0 before Counter0 reaches 0
b. Counter1 does not reach 0 even when Counter0 and Valid0 have both reached 0

47. Run a background check on entire Flash using CRC and DMA
My understanding is this requires a CRC check on the entire Flash memory. Could you please clarify if this is correct and what role the DMA has here?

51. Set up the MPU for the bus masters
54. Configure desired access permissions for peripherals using the Peripheral Central Resource (PCR) controller registers
The Safety Manual states the API Name as "Not Applicable" with the Remark "Feature in Hardware". Does this mean that the above initialization steps are not applicable for the controller?

Would appreciate your help in this regard.

Thanks and Regards,
Vimal

  • +1
    TI__Guru**** 186236 points

    Hi Vimal,

    Vimal N said:
    Would this involve setting the Counter0, Counter1 and Valid0 values

    Yes. Clock1 must expire in the Valid window, otherwise generates an error.

    Vimal N said:
    Could you please clarify if this is correct and what role the DMA has here?

    CRC controller supports three operation modes: Auto, Semi-CPU, and Full-CPU.

    In Full-CPU mode, the CPU does the data patterns transfer and signature verification all by itself. The DMA controller is utilized to transfer data to PSA signature register, and CRC register in semi-CPU and Auto modes. Please refer to CRC chapter of TRM.

    Vimal N said:
    51. Set up the MPU for the bus masters

    You can setup the MPU (memory performance unit) using HALCOGen GUI.

    Vimal N said:
    54. Configure desired access permissions for peripherals using the Peripheral Central Resource (PCR) controller registers

    The clock to a peripheral can be gated using PCR Peripheral Power-Down Set Registers. The peripheral can also be programmed to be access in privilege mode only using PPROTSETx registers.

    Vimal N said:
    The Safety Manual states the API Name as "Not Applicable" with the Remark "Feature in Hardware". Does this mean that the above initialization steps are not applicable for the controller?

    which document? can I have the literature number, for example SPNU550A?

    Vimal N said:
    API Name as "Not Applicable"

    I think this means The SDL (Safeti Diagnostic Library) doesn't API for this safety mechanism. 

  • 0 in reply to QJ Wang
    Prodigy 80 points

    Hi QJ Wang,

    For steps 51 (the linked query (https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/402450/unclear-requirements-for-tms570-initialization-sequence) mentions setting up the MPU for each bus master) and 54, the SafeTI Diagnostic Library Software Safety Manual for Hercules Processors (SPNU592A) mentions the following with respect to the TMS570LS1227 controller:

    Does this imply that the steps are not applicable to TMS570LS1227?

    Thanks and Regards,

    Vimal

  • 0 in reply to Vimal N
    TI__Guru**** 186236 points

    HI Vimal,

    We use different documents. I read the device safety manual for TMS570LS12x (SPNU550B), but you referred to SDL SW Safety Manual (SPNU592A).

    Not Applicable means there is no API for those safety mechanisms.

  • +1 in reply to QJ Wang
    TI__Guru**** 186236 points

    Those safety features (DMA1, HET1, and INC2) are supported by TMS570LS12x device.

  • 0 in reply to QJ Wang
    Prodigy 80 points

    Hi QJ Wang,

    Thank you for your response.

    What does "Feature in Hardware" in the Remarks column mean? When I look at the same features (DMA1, HET1) for TMS570LC4357 in the SDL SW Safety Manual (SPNU592A), the API Name column contains "Not Applicable" (same as TMS570LS12x) but the Remarks say "Handled by the operating system and safety application". What the difference between the two?

    Thanks and Regards,

    Vimal

  • +1 in reply to Vimal N
    TI__Guru**** 186236 points

    Feature in hardware: the safety features present in hardware, and the diagnostics are done by hardware automatically.

    Handled by the operating system and safety application: decided by application if this feature is needed

    Not Applicable: no SDL API