TMS320F28379D: software problem

FRANK1

Part Number: TMS320F28379D

Hi Team,

A customer has a software problem but he can not post thread in E2E due to the limited access as student.

I currently have issues with communicating over SPI between my two TMS320F28379D launchpads.
I make use of the two copies spi_loopback_cpu01, in two different roles, as slave and master, across two CCS instances.
I have F2837xD_Spi.c formatted differently across both files to reflect which is slave and master.

The issue I have is that when I send one value, and only one value like 212, this does not appear in the rdata register window of ccs.
Could you please help me out with this?

7183.spi_loopback_cpu01.zip

spi_loopback_cpu01_Primary.zip

Thanks for your help.

Regards,

over 4 years ago

0 Marlyn Rosales Castaneda20 over 4 years ago

TI__Mastermind 24890 points

Hi Frank,

Please allow me a day to look over the code that you attached and I will respond with feedback.

Best Regards,

Marlyn

0 Marlyn Rosales Castaneda20 over 4 years ago in reply to Marlyn Rosales Castaneda20

TI__Mastermind 24890 points

Frank,

What value is received instead of 212? Also, if they send more than just one value is the correct data received?

Best Regards,

Marlyn

0 FRANK1 over 4 years ago in reply to Marlyn Rosales Castaneda20

TI__Expert 8555 points

Hi Marlyn,

Sorry for the late reply.

If I haven't already told you, instead of the number 212, on the slave side, or the receiver side,

I receive random numbers like 65334, 20098, 12398 and other random numbers as such. No discernible pattern seems to be derivable.

Also, whether I try to send just one number or many, the same issue persists.

Thanks.

0 Marlyn Rosales Castaneda20 over 4 years ago in reply to FRANK1

TI__Mastermind 24890 points

Hi Frank,

Thank you for the additional information.

Have you observed what is getting transmitted using a logic analyzer or an oscilloscope, as well as the data being received on the other F28379D device? Have you also verified the baud rate is as expected?

Best Regards,

Marlyn

0 Nima Eskandari over 4 years ago in reply to Marlyn Rosales Castaneda20

TI__Guru 52040 points

In general have you looked at the signals on an oscope? That is usually step 1 in debugging the communication. Making sure the clock and data are coming out correctly on the pins.

0 Nima Eskandari over 4 years ago in reply to Nima Eskandari

TI__Guru 52040 points

if all is well on the sender, then you move on to the receiver. Connecting the clock to the receiver and grounding the data. you should get new 0x00 values. Then pulling the data high, you should get 0xFF.

0 Nima Eskandari over 4 years ago in reply to Nima Eskandari

TI__Guru 52040 points

Also anytime you send data, you should automatically receive a dummy 0xFF value.

C2000™︎ microcontrollers

C2000 microcontrollers forum

TMS320F28379D: software problem