to my knowledge the TNETC4830 Puma 5 is a MIPS based cable modem platform from Texas Instruments. Comparable Intel architecture based platforms include Intel(R) Atom(TM) Processor CE5300 or the Intel(R) Puma 6 Media Gateway. Both of these are supported with Intel(R) System Studio via Intel(R) ITP-XDP3 or Macraigor usb2Demon* JTAG debug devices.
We currently only support Intel architecture and not MIPS* though.
thanks for pointing this out to me. I had actually not quite noticed that the MIPS based Puma 4 and Puma 5 chips are now owned, distributed and supported by Intel. Being focused on primarily IA this had escaped me - sorry.
The main landing page for Intel's cable modem solutions is at www.intel.com/go/cablemodem.
For software support of your Intel provided reference platform design, I would recommend to log into your IBL or Intel Premier Supprot account or contact your company's Intel field contact.
If you don't have any of these contacts, please provide me with the exact platform you are basing your development on, and I will see if I can identify the right point of contact.
Puma5 being a very specialized platform not based on IA, informatio about the proposed JTAG debug solution is probably posted on our Intel Business Link portal. Where you succesful in talking with your Intel field contact or the distributor for your Puma5 platform?
This would really be the best source of information on these older non-IA platforms. As I am sure you can imagine JTAG debug on MIPS is quite different from JTAG debug on IA. I do not know which specific JTAG vendors have been enabled for Puma5.
I sent an email to some contacts I have in the business unit that owns Puma5. I hope to get a recommendation for a JTAG debug tool back from them.
I would still like to emphasize that your distributor or Intel field representative is probably the best source of this information.
I am pinging our owning division on recommended software tools for these older Puma platforms again.
If you have not doen so yet, please als ocheck with your Intel field representative.
our application engineers tell me that for Puma4, they mostly use EST* VisionProbe* debug tools and that for Piuma5 they mostly use Trace32* from Lauterbach*.
Your Intel field representative (Field Application Engineer or Field Sales Engineer) should be able to provide you additional guidance.