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.

TMS570LC4357 MibSPI groups Control register

Other Parts Discussed in Thread: TMS570LC4357, HALCOGEN

Hi all,

The TMS570LC4357 reference manual states there are 16 transfert groups for MibSPI peripheral

The registers view in CCS6 confirms this (tg0ctrl to tg15ctrl are listed in mibSPIx register set).

But when trying to initialise all of TGxCTRL registers, only the 8 first ones are correctly written

the 8 remaining ones stay with a null content. Moreover, with HalCoGen, the graphical menu

only permit to set-up 8 groups and the mibspiInit() function generated set-up only the first 8

TGxCTRL registers with a consistent value and the 9th TGxCTRL with a "special value".

Does that mean that only 8 transfert groups are actually available in TMS570LC4357 ?

NB: I just tested this on MibSPI1

Thanks for your answer

Regards,

Sylvain Balssa

  • Each of the MibSPI on the TMS570LC4357 has only 8 transfer groups. I will have a table added to the datasheet (SPNS195A). Where is the reference to 16 transfer groups? Is it in the TRM (SPNU563)? Which page?
  • HI Bob

    Thanks for your fast answer..

    I must admit that I did not looked into datasheet SPNS195A to check if number of TG was

    mentionned. We understand that chapter 28 of TRM says many times that number of TG varies

    per device. That why we tried to know how many TG were present. We only deduced from the TRM,

    in table 28-8 that since memory space allocated to TGxCTRL registers corresponds to 16 32 bits registers,

    there are 16 TG. Moreover, the NOTE below table 28-41 (page 1523) mentions TG15, which for us

    was an implicit confirmation of 16 possible TG. But we were wrong !

    OK, the number of TG is 8, which is not a problem for our use of MibSPI (we plan to use five as a

    maximum) but we are still wondering why code generated by HalCoGen (when mibSPI driver option

    in ticked ON) still do a write in  TGCTRL[8] (file HL_mibspi.c, function mibspiInit()) like this

     "  mibspiREG1->TGCTRL[8U] = (uint32)(2U+0U+0U+0U+0U+0U+0U+0U) << 8U;   "

    (2 is because we set a length of two words for a unique TG at init)

    Never mind, the code we wrote is OK and mibSPI works fine for us.

    Regards

    Sylvain Balssa

  • Sylvain,

    I must admit that it is not clear in the datasheet. The ambiguity is our fault. I am working on adding a table to the datasheet now. Luckily a revised version of this datasheet is about to be released. Thank you for bringing this to my attention. if you don't mind, please click the "Verify Answer" box on my original response so this thread will show as answered.
  • Thanks a lot for your help

    Best regards
    Sylvain Balssa