TMS320F28379D: What CPU Am I using?

Hi Anil,

Please take a look at the attached TRM (spruhm8g.pdf).  You will find the answer in section 2.2.1 Device Identification. Let us know if you need further assistance.

Cheers!

Krishna

dual_core_delfino_spruhm8g.pdf

Hi Anil,

Address for this location is "0x0007 026D" which is  provided in device manual (section "6.4 Identification").

Regards,

Vivek Singh

Anil,

CPUID at 0x7026D will tell whether it is C28x CPU1 or C28x CPU2 for F2837xD.  However, it does not tell the processor type - looks like you are looking for processor type (I have seen few customers asking for this info and hence wanted to clarify).

Also, note that the CPUID address may not be same in all the Defino family devices - if that matters for you.

Thanks and regards,

Vamsi

Thanks for your reply. Yes, I am trying to identify processors across Delfino family. For example, I may want to configure differently for 379 vs piccolo.

Anil,

In all the devices that we have up to now in Piccolo or Delfino family, processor type is C28x.
In Concerto family, we have C28x and ARM M3.
We may have other processor types in Delfino and Piccolo families as well in the future.

Thanks and regards,
Vamsi

Hi Krishna,

The TRM (spruhm8.pdf) that you pointed out to Anil is really

interesting and has quite a bit of information on the system. Noticed

that it was last update on Sep 017 so I'd imagine perhaps a more

recent version (update) might be available? If so I'd really be interested to

have a look at it if you could point me to it. In addition, hope you don't

mind me asking few questions/thoughts on this particular system.

A colleague of mine go a copy of it sometimes ago but passed it on

to me for testing etc. Due to the hectic schedules I have

not had much chance to look much closer into the hardware etc. till very

recently.

I really appreciate it and many many thanks.

Cheers,

Saleh

Hi Saleh,
You are welcome! The TRM (spruhm8.pdf) appears to be the latest version. Please let us know if you have all the information you need.
Thanks,
Krishna

Hi Krishna,

Wonderful to hear back from you and hope all is going well there. The TRM is
quite full of interesting info on the system. Also due to the size of the document
I'm still going over various parts of it :) A colleague (very well experienced engineer
and circuit designer) is planning on designing another board that would
couple with the TMS320F28379D via a set/subset of those GPIO pins.
The board would be used for different applications we have in mind.
As of now I'm not quite sure which subset of those pins would be of relevance
here and could certainly used be for such coupling... That is now one of those
points I have been looking into and trying to figure out...

Cheers,
Saleh

Any more recent technical docs/work for the TMS30F28379D? or the TRM
suppose to cover it all?

Hi Saleh,
You might find this training material useful:
processors.wiki.ti.com/.../C2000_Multi-Day_Workshop
Thanks,
Krishna

Hi Krishna,

Thanks for pointing to the workshop and training materials
there. I have already come across this and looked at those
lab examples. They are quite useful. I was hoping that there
might be more materials there along those lines that perhaps
might have been put together or developed by TI perhaps
more recently or after the aforementioned workshop.
I have not come across any other similar materials but
thought to ask just in case I might have missed it.

Would appreciate any pointers or suggestions. Many thanks.

Cheers,
Saleh

Hi Krishna,

Thanks again for the pointers to the workshop materials.
Going back and looking at the workshop manual I have
a couple of questions. The first figure of the manual under
Development Tools is for the front of F28379D LaunchPad.
Showing there the plug-in module connectors of J2/J4* , J6/J8*,
J1/J3* and J5/J7*. I'd guess that one would only need a subset
of those connectors to do an interface with another module?
Say perhaps the first 8 columns -right to left- (16 pins) plus the
bottom pin in the 9th column of J2/J4, and the first 6 columns
-right to left- (12 pins) plus the bottom pin in the 7th column
would perhaps do? If not, then how do we go about to get those
connectors (either all or a subset of them) to be part of any
actual modular interface? At minimum, which one/part of
(J2/J4, J6/J8, J1/J3, and J5/J7) would need to be made available
or active for any plug-in module, or would that highly depends
on the module/board itself? I'd guess a subset of those connectors
would be enough rather than the entire set.
My sincere apologies if this post is not too clear or my questions are
not too precise....
I appreciate any of your thoughts on this.

Cheers,
Saleh

Hi Krishna,

Best wishes hope you don't mind me asking another question :)

Using one of the lab examples provided in the above-mentioned multi-day

workshop I was able to display the provided sinusoidal data on a single ADC

channel (connected to pin 30 which is labeled as AA0 on the back of the C2000

board). I gather the other A/D channels appear to be, for example, on pin 29 (labeled

AA2 on back of the board) as well as the other pins labeled AA__, ABx and  ACx --

... there are 16 pins in total. I'd like to know if you could point me to some example code

(or perhaps a modified version of one of those workshop examples) that would work

in such a way to acquire data on 4 of these channels concurrently. Would such

concurrency in data acquisition via multiple channels be possible on TMS320F28379D?

If so I really would love to see an example so I could perhaps try it out as a separate project

on the code composer studio (v8). Thanks.

All the best,

Saleh

Any thoughts or suggestions on my previous message from anyone out
there who is quite familiar with LaunchPad C2000 TMS320F28379D
are quite welcome and very much appreciated.

Any thoughts or suggestions on my previous message from anyone out
there who is quite familiar with LaunchPad C2000 TMS320F28379D
are quite welcome and very much appreciated.

-Saleh

Hi Krishna,

Wonderful to hear back from you. No I have not completely resolved it.

Been exchanging posts with your colleague Devin Cottier on this. The tag of that thread is:

"TMS320F28379D: Concurrent data acquisition via multiple channels on the F28379D ...".

He and Joseph been quite helpful and pointed me to a couple project examples there. Neither of

them is from the workshop labs so I have been asking Devin a bit more about modifying them

in order to be able to handle multiple channels concurrently.

Most recent reply from him was posted early this morning. Looking at all of that now ... but so far

I don't have a complete solution. Will work at it for while and keep you posted if you like.

Many thanks and will chat more soon.

-Saleh

I guess Devin, Joseph and other colleagues there reply to my post on another
thread? You can verify that at:
e2e.ti.com/.../2652439