• State Resolved
  • Locked Locked
  • Replies 12 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 1039 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.

TMS320F28379S: F28377s vs F28379s, and Biss/Endat Library

A GIR
Genius 3615 points
Part Number: TMS320F28379S
Other Parts Discussed in Thread: C2000WARE, CONTROLSUITE

Hello,

we produce servo drive based on F28377s. The software is based on the IDDK exemple.

Now, we want add the Biss/Endat possibility.

To do this, we will use the TI Biss and endat library which use the CLB.

As I seen on this forum (10 september), datasheet was updated to explain the CLB and a configuration tool will coming soon.


I just seen the CLB block is not available on F28377s, but only on the F28379s.

-1) Is F28377s software and hardware are fully compliant if we replace the microcontroller by a F28379s? (CCS IDE project option need change target from 77 to 79, but it is the only change to do?)

-2) Biss/Endat library exemple are given for the F2837xD.  I think the library work also on the F28379S version?


Thenk

  • 0
    TI__Mastermind 24095 points

    Hi,

    A GIR said:

    As I seen on this forum (10 september), datasheet was updated to explain the CLB and a configuration tool will coming soon.



    Yes - the CLB configuration tool will be available at end of Sep in the C2000ware release.

    A GIR said:
    -1) Is F28377s software and hardware are fully compliant if we replace the microcontroller by a F28379s? (CCS IDE project option need change target from 77 to 79, but it is the only change to do?)



    CLB is not available on F28377s. It's available on F28379s. Rest of the software would be compatible as F28379s configuration is super set of F28377s.

    A GIR said:
    2) Biss/Endat library exemple are given for the F2837xD.  I think the library work also on the F28379S version?


    The library example has been developed for F2837xD Launchpad but I expect it to work on F2837xS if you are using the same package and pinout as the library had a fixed pinout definition.

  • 0 in reply to Subrahmanya
    Genius 3615 points

    OK

    In fact I change the Pinout

    SPI goes to GPIO63 to 66,  (MUX configuration changed only, no other configuration done into library?)

    And GPIO 34 used in OUTPUTXBAR1 is moved to GPIO 24. Then the only change is in the init time. Instead of configure the GPIO34 to MUX=1, we configure GPIO24. I hope no other reference to this GPIO is done into the library?

  • 0 in reply to A GIR
    TI__Mastermind 24095 points

    Hi,

    Please refer to the library user guide for the corresponding interface.
    These are available at C:\ti\controlSUITE\libs\app_libs\position_manager\v01_02_00_00\<endat/biss>\Doc
    The document has a section titled "Resource Requirements". If the resource is dedicated - then the pin configuration can't be changed.
    SPI seems to be fine, but GPIO34 is listed as a dedicated resource.

  • 0 in reply to Subrahmanya
    Genius 3615 points

    Hi,

    I seen this documentation.

    The documentation seem say that e can't change it.

    This should be true if library use also the GPIO34 as GPIO, because if it use only as OUTPUTXBAR, the configuration of the MUX on the any GPIO having this function should be ok.

    could I have a sure answer from Texas Instrument, perhaps directly from the team in charge of the development of this library?


    In case it is imperative to use the GPIO34, could Texas Insturment generate a library using the GPIO24?

    Thank

  • 0 in reply to A GIR
    TI__Mastermind 24095 points

    Hi,

    Since it's marked as dedicated resource you've to use GPIO34 only.
    TI doesn't have a plan to release an updated library for different IO configuration.
    However, We are releasing a tool to configure CLB by end of this month.
    With this tool customers can design their own logic using CLB and configure IOs as needed.
    Later, we also plan to release all the source code and example using this tool, for EnDat, BiSS-C etc.
    Customers will be able to tweak these configurations, unlike the libraries which come with pre-defined resource requirements.
    Release dates have not been finalized yet for these  EnDat, BiSS-C examples based on CLB tool - current plan is to have them available early next year.

  • 0 in reply to Subrahmanya
    Genius 3615 points

    Hi,

    I understand your position and not tale a risk to indicate to me if whe can use GPIO24 as OUTPUT XBAR instead of GPIO34.

    But on my side, the impact very important.

    Effectively, it is maked as "Dedicated" ressource. But if we take the Figure p6, GPIO34 is onmy the output of XBAR. So according this, we could map the OUTPUTXABR to any other pin which accept this configuration  via its MUX configuration.

    The only case where this can cause problem is if the library get the state of this pin by reading the GPxDAT register...

    If anybody in Texas Instrument has access to the source code, could be saiy me if the software library manage this pin or if it let OUTPUT XBAR.

    I know that my request is not trivial.
    The other solution will be to try, but the time for me to have all the necessary, it will be too late then to change anything to the design of the card. (Knowing that these changes will be very problematic anyway)
    Thank
  • 0 in reply to A GIR
    TI__Mastermind 24095 points

    Hi,

    I'll check the source or test this and get back to you in 2 days.
    Can you confirm which version of the software you are looking at, in the controlSuite?
    Is it position_manager\v01_02_00_00?

  • 0 in reply to Subrahmanya
    Genius 3615 points

    Yes, this is this version.
    I will be very grateful to you for doing this.
    I look forward to seeing you here again.

  • 0 in reply to Subrahmanya
    Genius 3615 points

    Hello,

    Have you some new for me?

    Thank

  • 0 in reply to A GIR
    TI__Mastermind 24095 points

    Hi,

    Not yet - will update you by end of day today.

  • 0 in reply to Subrahmanya
    TI__Mastermind 24095 points

    Hi,
    I've checked that the GPIO34 can be remapped to other locations with OUTPUTXBAR1 if you are using position_manager\v01_02_00_00.
    So, yes, you can use the mapping the way you had it above.

  • 0 in reply to Subrahmanya
    Genius 3615 points

    Hello,

    I'm very happy to hear that!

    Thank for your test.