• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 415 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.

TMS320F28379D: BissC supports by C2000Ware

U-SK
Genius 5840 points
Part Number: TMS320F28379D
Other Parts Discussed in Thread: C2000WARE, CONTROLSUITE, BOOSTXL-POSMGR

Hello,

Could you tell me when C2000Ware supports BissC?

I would like to run BissC and PTO at the same time.

But I can't link BissC library to latest PTO project because BissC library is included in controlSUITE and it is Legacy COFF formatt.

Legacy PTO project that is Legacy COFF format has different I/O configuration from latest PTO Project, so it can't be used with BOOSTXL-POSMGR.

Can we change PTO I/O(Pulses,Direction) in order to adapt BOOSTXL-POSMGR in following project?

C:\ti\controlSUITE\libs\app_libs\position_manager\v01_02_00_00\pto\examples\PM_pto_pulsegen_test

Or, are there any way to combine following project?

C:\ti\controlSUITE\libs\app_libs\position_manager\v01_02_00_00\pto\examples\PM_pto_pulsegen_test

C:\ti\c2000\C2000Ware_MotorControl_SDK_3_00_00_00\libraries\position_sensing\pto\ccs\f2837x

Regards,

U-SK

Regards,

  • 0
    TI__Guru* 92140 points

    U-SK said:

    But I can't link BissC library to latest PTO project because BissC library is included in controlSUITE and it is Legacy COFF formatt.

    Legacy PTO project that is Legacy COFF format has different I/O configuration from latest PTO Project, so it can't be used with BOOSTXL-POSMGR.

    Hello, U-SK,

    All of the code is provided for the PTO project in the motor control SDK.  I suggest modifying this code so that it does not conflict with the BiSS library that you want to incorporate.  

    I just rebuilt the PTO in the SDK for COFF and here are the steps to do so:

    1) Library: under "General" change "output format" to legacy COFF.  

    2) rebuild the library

    3) System Example

    • Under "General" change "output format" to legacy COFF.  
    • under Linker, File Search Path Change rts2800_fpu32_eabi.lib to libc.a.   libc.a is an index library and will direct the linker to the correct RTS library for the build.

    4) rebuild the system example

    We are working on moving BiSS-C to the motor-control SDK but it will not be generally available until late this year or 1Q 2021.

    Regards

    Lori

  • 0 in reply to Lori Heustess
    Genius 5840 points

    Hi Lori,

    Thank you for your reply.

    I could combine following project and error disappeared thanks to your advice!

    controlSUITE\development_kits\BOOSTXL_POSMGR\v01_01_00_00\bissc-F28379DLpad-S2\examples\PM_bissc_SystemTest

    C2000Ware_MotorControl_SDK_2_01_00_00\solutions\boostxl_posmgr\f2837xd\ccs\pto_pulsegen

    But BissC function seems not to work...

    Because single BissC project worked well, so I think PTO function and BissC function conflicted.

    I think BissC library uses CLB tile3, tile4, and pto library uses CLB tile 1.

    Could you tell me what is conflicting in detail?

    Regards,

    U-SK

  • 0 in reply to U-SK
    TI__Guru* 92140 points

    Hello U-SK,

    Excellent.  I'm glad you have been able to build a combination project.

    I've not tried this combination myself so I don't know what the exact conflict is.  The PTO source is all included in the SDK so it can be modified as needed.  I believe you are correct on the tile usage.  The conflict may be an IO, or XBAR.  Do you see any activity on the pins from the C28x?

    Regards

    Lori

  • 0 in reply to Lori Heustess
    Genius 5840 points

    Hi Lori,

    Thank you for your cooperation!

    PTO function(both of pulse and direction) works fine on combination project.

    But BissC function does not work absolutely.

    Biss-C function works on library and source is not offered, so I think CLB configuration can't be seen.

    Is there a way to check the CLB Configuration of BissC?

    Regards,

    U-SK

  • 0 in reply to U-SK
    TI__Guru* 92140 points

    U-SK said:
    Is there a way to check the CLB Configuration of BissC?

    You can inspect the CLB registers in the CCS register window.   This should enable you to confirm that tile3 and tile4 are being used by the BiSS reference. 

    Regards

    Lori

  • 0 in reply to Lori Heustess
    Genius 5840 points

    Hi Lori,

    Thank you for your reply.

    I confirmed CLB registers at CLB reference project.

    As a result,

    　CLB3&4： CfgRegs and CtlRegs field is not reset value, and DataExchange Regs is reset value at all.

    Also,

    　CLB1&2：CfgRegs and CtlRegs is reset value, and DataExchange Regs value is not reset value at all.

    In PTO project I referenced,

    　CLB1：All register value is not reset value.

    　CLB2：Only DataExchange Regs value is not reset value.

    My understanding that PTO does not use CLB2, so DataExchange Regs value of CLB2 should be reset value.

    Could you tell me the reason why also DataExchange Regs value of CLB2 is changed in PTO project?

    According to result, does BissC referece project also use part of CLB1 and CLB2?

    Regards,

    U-SK

  • 0 in reply to U-SK
    TI__Guru* 92140 points

    U-SK,

    Apologies for the delay. I will need to look at this closer to make sure I don't give you incorrect information. I will get back to you by end of Wednesday US time.  For the DataExchangeRegisters - I recall that they are random at power-on/reset unless cleared using the CLB_clearFIFOs() function.  

    Regards

    Lori

  • 0 in reply to U-SK
    TI__Guru* 92140 points

    U-SK,

    I confirmed that the Data Exchange PUSH/PULL registers do not reset to 0.  Right after the clocks are enabled you can see data in these registers, before the CLB initialization routine.   

    Best Regards

    Lori