• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 99 subscribers
  • Views 197 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.

LP-AM263P: Issue Running LEVEL 2 Example on AM263x LP with DRV8316REVM (No SPI)

Shahar Cohen
Intellectual 331 points
Part Number: LP-AM263P
Other Parts Discussed in Thread: LP-AM263, DRV8316REVM, TIDM-02018, SYSCONFIG

Tool/software:

Dear TI Expert,

I'm trying to run the universal_motorcontrol_am263x_r5fss0-0_nortos_ti-arm-clang_3phGaN LEVEL 2 example on the TI LaunchPad Sitara AM263x (LP-AM263) with the DRV8316REVM, configured for DRV8316T in hardware mode (no SPI module).

DRV8316REVM Hardware Configuration (No SPI Mode):

  • R9/R12 - DNP
  • R40/R45 - Tied to AGND
  • R37/R42 - Hi-Z
  • R38/R43 - Hi-Z
  • R41/R46 - Hi-Z
  • R39/R44 - Tied to AGND

Pin Configuration (Following Custom Board Example):

Configuration DRV8316REVM:

  • DRVOFF - GND
  • MCUVREF - 3.3V
  • NFAULT - 3.3V
  • NSLEEP - 3.3V

Issue Encountered:

After building and running the example, when I set motorVars_M1.flagEnableRunAndIdentify = 1, the motor gets stuck with high current and does not move. Additionally:

  • For the first ~5 minutes of operation, the encoder resets instantly before eventually counting as expected. After it count as expected.
  • I predefine the MOTOR1_ENC, and have the encoder set by default in AM263_3phGaN_3SC.syscfg (my encoder post here)

Additional Observation:

This same DRV8316REVM (No SPI) configuration runs successfully with the universal_motorcontrol_lab_f28002x example on the F280025C LaunchPad, without any issues.

I would greatly appreciate any expert help in resolving this issue.

Video:



Count ad expected(After ~5min):

Best regards,
SC

  • 0
    TI__Guru*** 135355 points

    Hello Shahar,

    You already have an open thread on this topic with an expert supporting you, please continue to work this issue through that thread: LP-AM263: Assistance Needed: Module Overcurrent Issue with AM263x & DRV8316 - Processors forum - Processors - TI E2E support forums

    Best Regards,

    Ralph Jacobi

  • 0 in reply to Ralph Jacobi
    Intellectual 331 points

    Hi Ralph,

    I appreciate your response, but please read my post carefully. The issue I’m facing here is completely different from the one discussed in the previous thread.

    I reiterated the full setup because, in the last discussion, the expert was unaware that the DRV8316REVM can operate in No-SPI mode. This new issue is not related to overcurrent—that problem was already resolved in the previous thread.

    I would really appreciate expert assistance in troubleshooting this new issue.

    Thank you,
    Shahar

  • 0 in reply to Shahar Cohen
    TI__Guru*** 135355 points

    Hello Shahar,

    I've discussed this topic with an expert. The design you are referencing does not use the DRV8316REVM and while it is no problem to use it on no-SPI mode and work it into your application that way, we are not in a position to provide detailed support to handle the migration process and address issues with that.

    Section 4.6 of the Design Guide for TIDM-02018 provides detailed step-by-step directions on how to go through this process. 

    Please review all the details there and compared them to your project settings to find the cause of the issue you are facing. 

    Best Regards,

    Ralph Jacobi

  • 0 in reply to Ralph Jacobi
    Intellectual 331 points

    Hi Ralph,

    In level 2, the issue was resolved by removing the debug log method used to monitor the live position. Now, the EQEP no longer resets after setting the motorVars_M1.flagEnableRunAndIdentify to 1 (before still reset not accur in the universal_motorcontrol_lab_f28002x) however, while the variable motorVars_M1.speedRef_Hz is set to 60, I'm receiving a value of -60. What could be causing this discrepancy?

    More importantly, in level 3 the EQEP resets again, and the motor remains stationary. What might be the cause of this behavior?

    EQEP setup:

    It's also worth noting that on the F280025C LaunchPad, the same EQEP operates without any issues.

  • 0 in reply to Shahar Cohen
    Intellectual 331 points

    I notice that the adcData.offset_v_sf stay zero 
    what can be the cause?

    Ty

  • 0 in reply to Shahar Cohen
    TI__Guru*** 135355 points

    Hello Shahar,

    I would recommend prioritizing reviewing the SysConfig and HAL configurations per the guidance of the design guide to make sure each step has been properly adapted for this particular DRV board.

    The AM26x device has a very different SysConfig than the F280025C LaunchPad, so you can't really point to that LaunchPad working and assume the steps to make that happen is equivalent to making it work on AM26x. You have to treat AM26x as an unrelated device to the F280025C MCU and work through each step independently.

    Best Regards,

    Ralph Jacobi

  • 0 in reply to Ralph Jacobi
    Intellectual 331 points

    Hi Ralph Jacobi,

    I mentioned the use of the F280025C MCU to highlight that the motor and encoder are functioning correctly. I fully understand that the AM26x is a different MCU, and I am proceeding step by step accordingly.

    If possible, could you please check my Universal Motor Lab Level 3 post?

    Thanks!