• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 82 subscribers
  • Views 647 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:

TMS320F28379D: Question regarding Tamagawa ABS Encoder with BOOSTXL-POSMGR plug-in module

TMS320F28379D: CLB does not generate clock when use IDDK R2.2 developement board to evaluate t-format library

Feng CHEN
Expert 1670 points

Part Number: TMS320F28379D
Other Parts Discussed in Thread: CONTROLSUITE

Hi TI experts:

when i use IDDK R2.2 development board to evulate t-format library in position mananger, it dones not generate clk when runing ti example code, which is downloaded from controlsuite.

the example code is copied from c:\ti\controlSUITE\libs\app_libs\position_manager\v01_01_00_00\tformat\examples

i follow user' guide named sprui71 and sprui66.

let me describe my finding as below:

step1: run the example program, the program is halted at the line " while(fformatData.dataReady != 1) {}"

step2: then i debug the code step by step and measure C1-SPIB-CLK(that is GPIO7 pin), the GPIO7 will become HIGH after run the tformat_Init() function,

step3: then stepinto the function fformat_exCommands();  when run the function "PM_tformat_startOperation()", CLB should send signals out, right? but i can not see any clock in the pin of GPIO7.

i capturesome pieces of example code for your reference as below:

so, can anyone give me some suggestion how to handle this issue? many thanks...

  • 0
    TI__Mastermind 24095 points

    Hi,

    Did you observe any activity on the D+/D- pins when PM_tformat_startOperation() command is issued?
    One more thing to try is to power the encoder separately - do not source power from IDDK but power the encoder directly from an external power supply.

  • 0 in reply to Subrahmanya
    Expert 1670 points

    Dear Subrahmany,

    please refer to my reply as below:

    Did you observe any activity on the D+/D- pins when PM_tformat_startOperation() command is issued?

    a: Yes, bother D+/D- has no any data activity with HIGH level. 


    One more thing to try is to power the encoder separately - do not source power from IDDK but power the encoder directly from an external power supply.

    A: yes, actually it is already powered by an external power supply. if not, the program will be halted when calling the code"GpioDataRegs.GPBDAT.bit.GPIO32 = 1" in the function of tformat_Init().

    can you help me advise what is the next step to debug the issue? thanks a lot.

    Feng

  • 0 in reply to Subrahmanya
    Expert 1670 points
    and how can i know CLB works properly? is there any troubleshooting method you can give me?
  • 0 in reply to Feng CHEN
    TI__Mastermind 24095 points
    Hi,
    Did you place the jumpers on IDDK as described in sprui66 in section 4.2 Jumpers and Switches?
    When StartOperation() command is executed, there will be a clock on GPIO7 - which in turn is routed as SPICLK.
    Trigger on GPIO7 and look for this clock, it is generated by CLB.
    Earlier you mentioned "GPIO7 is held high". The expected behavior is that there will be few clock pulses and then it'll be high till the encoder responds back with data.
    Make sure that the frequency of the clock is 2.5MHz as well, encoder will not respond to other data rates.
  • 0 in reply to Subrahmanya
    Expert 1670 points

    Dear Subrahmanya,

    please see my reply in below:

    Did you place the jumpers on IDDK as described in sprui66 in section 4.2 Jumpers and Switches?

    A: yes, i double-check the setting and there are correct.


    When StartOperation() command is executed, there will be a clock on GPIO7 - which in turn is routed as SPICLK.
    Trigger on GPIO7 and look for this clock, it is generated by CLB.
    Earlier you mentioned "GPIO7 is held high". The expected behavior is that there will be few clock pulses and then it'll be high till the encoder responds back with data. 

    A: yes, GPIO7 becomes to HIGH after calling tformat_Init().  please see below figure, which is captured by trigger mode. i can not see any other few clock pulses on GPIO7.


    Make sure that the frequency of the clock is 2.5MHz as well, encoder will not respond to other data rates.

    A: As my understanding, if clock frequency does not match with 2.5M hz, although encoder will not respond to give out D+/D- data, but CLB should send out clock first on GPIO7. becuse CLB is a master and should send out clock first before encoder response. am i right?

    unfortunately, all the data activity on GPIO7 is shown as below figure. in other way, no any activity on GPIO7 happened when calling startOperation();

  • 0 in reply to Subrahmanya
    Expert 1670 points
    my ccs version is v7.4.0 and controlsuite version is v3.4.9.
    is the issue maybe caused by version mismatch problem?
  • 0 in reply to Subrahmanya
    Expert 1670 points

    PM_tformat_systemtest_v1.zipattached please my example code for your reference. can you please help run it in your PC based on IDDK R2.2 board to see whether it works or not? thanks

  • 0 in reply to Feng CHEN
    TI__Mastermind 24095 points
    Hi,
    I've run the example in the release directory on IDDK with an encoder and I do not see any issue.
    As per your project, it seems to be missing some files that are there in the released example and hence it's not compiling.
    For the purpose of debug, I suggest that you run the released code as it is from controlSuite and let me know the results.
  • 0 in reply to Subrahmanya
    Expert 1670 points

    Dear Subrahmanya,

    there is CLB cmd file missing in my project. now it works. thanks very much for your support.

    Feng