TMS320F28388D: The question of ESC_LED_ERR pin

Luke Chen

Part Number: TMS320F28388D
Other Parts Discussed in Thread: C2000WARE

Tool/software:

Hi champs,

According to TRM, the ESC_LED_ERR pin should be driven by software and not the ESC on this device, below are the questions,

Should GPIO145 be configured as a GPIO output pin or ESC_LED_ERR pin?
What does it mean this pin should be driven by software? What should users do so that this ERR pin works well?

Please advise, thanks for your support.

Regards,

Luke

over 1 year ago

0 Luke Jones over 1 year ago

TI__Mastermind 28580 points

Hi Luke,

For the ESC_LED_ERR signal to drive the output, the GPIO should be configured as ESC_LED_ERR, not a generic GPIO.

I'll loop in an ETHERCAT expert for additional information on the ESC_LED_ERR signal.

Thank you,

Luke

0 Benjamin Collier over 1 year ago

TI__Mastermind 36526 points

Hi Luke,

Please look in the EtherCAT examples to see how the ESC_LED_ERR pin is used.

Best Regards,

Ben Collier

0 Luke Chen over 1 year ago in reply to Benjamin Collier

TI__Expert 5090 points

Hi Ben,

Which example project did you mean please?

Regards,

Luke

0 Benjamin Collier over 1 year ago in reply to Luke Chen

TI__Mastermind 36526 points

Luke,

The customer can look through the EtherCAT Loopback solution files. It can be found in C2000WARE/libraries/communication/F2838x/examples

Please find the instructions for the example in C2000WARE/libraries/communication/F2838x/doc/

The example requires you to use the Beckhoff slave stack files, which are not included in C2000WARE by default. This is covered in the instructions.

Best Regards,

Ben Collier

0 Luke Chen over 1 year ago in reply to Benjamin Collier

TI__Expert 5090 points

Hi Ben,

My customer tests f2838x_cpu1_echoback_solution example project, both RUN and ERROR LEDs work well. We study the code and find that GPIO145 and GPIO146 pins are configured as GPIO pins, the software uses HW_SetLed() function to turn ON/OFF LEDs according to communication status.

My customer wants to know the reason we don't configure GPIO145 and GPIO146 pins as ESC_LED_ERR and ESC_LED_RUN functions, please advise your comments on this question, thank you.

Regards,

Luke

0 Benjamin Collier over 1 year ago in reply to Luke Chen

TI__Mastermind 36526 points

Luke,

I am OOO until September 3rd. Please expect a response by then.

Best Regards,

Ben Collier

0 Benjamin Collier over 1 year ago in reply to Luke Chen

TI__Mastermind 36526 points

Luke,

Luke Chen said:
We study the code and find that GPIO145 and GPIO146 pins are configured as GPIO pins, the software uses HW_SetLed() function to turn ON/OFF LEDs according to communication status.

Which file is this in? Is it in a file generated by Beckhoff's ESC tool?

Best Regards,

Ben Collier

0 Luke Chen over 1 year ago in reply to Benjamin Collier

TI__Expert 5090 points

Ben,

My customer follows the instructions of 3.2 CPU1 Echoback Demo Example and generates the file ecatappl.c, it is in this C file.

Regards,

Luke

+1 Benjamin Collier over 1 year ago in reply to Luke Chen

TI__Mastermind 36526 points

Luke,

Since the file is generated by Beckhoff's ESC tool, it would probably be better to ask ETG/Beckhoff.

Best Regards,

Ben Collier

0 Luke Chen over 1 year ago in reply to Benjamin Collier

TI__Expert 5090 points

Ben,

One more question, is the ESC IP in F28388D identical with the IP in F28P65x device?

Regards,

Luke

+1 Benjamin Collier over 1 year ago in reply to Luke Chen

TI__Mastermind 36526 points

Luke,

Luke Chen said:
One more question, is the ESC IP in F28388D identical with the IP in F28P65x device?

Yes, the ESC IPs are the same.

The wrapper (called ESCSS in TRM) is slightly different, since ESC in F28388D connects to the ARM core while F28P65x has only C28x cores.

Best Regards,

Ben Collier

C2000™︎ microcontrollers

C2000 microcontrollers forum

TMS320F28388D: The question of ESC_LED_ERR pin