TC397XX development kit

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
Sakthivel
Level 3
Level 3
50 sign-ins 10 questions asked First like received

Hello there,

We planned to use the MCU part "TC397XX256F300SBDKXUMA1" in our project, but before actually putting it into the project, we need to evaluate its performance. For that, we need a development board with the same MCU mounted. We found a few development boards available on the Infineon site that are based on TC397 (ex: KIT_A2G_TC397_5V_TRB, KIT_A2G_TC397_3V3V3_TFT, KIT_A2G_TC397_24V_GTW), we found TC397XE and TC397XP series MCU mounted in the development kit.  Could you please share the development board that has the "TC397XX256F300SBDKXUMA1" MCU mounted?

if not please suggest any alternate approach to evaluate our MCU "TC397XX256F300SBDKXUMA1" in the available development board, since it is in BGA package it is difficult for us to remove and remount the MCU in dev kit.

Thanks,
Sakthivel

0 Likes
1 Solution
Jeremy_Z
Moderator
Moderator
Moderator
1000 replies posted 250 sign-ins 100 likes received

Hi @Sakthivel ,
1. Can you share the first sale details for the parts "TC397XX256F300SBDKXUMA1" MCU? we don't find it in longevity sheet.
-- Sorry, I don't find the exact information of the first sale day, as I know, the TC397/387 was launched in early of 2020.
2. So can you confirm that the TC4xx series MCU has 6 core and it is PIN compatible and Footprint compatible with "TC397XX256F300SBDKXUMA1" MCU
-- Yes.
BR,
Jeremy

 

View solution in original post

23 Replies
Sakthivel
Level 3
Level 3
50 sign-ins 10 questions asked First like received

Could you  share what is the difference between these MCU variants ?  

A ADAS enhanced, HSM enabled
E Emulation device, no HSM
F Emulation device, HSM enabled
P Production device, HSM enabled
X Extended feature, HSM enabled
C Customer specific

0 Likes
Jeremy_Z
Moderator
Moderator
Moderator
1000 replies posted 250 sign-ins 100 likes received

Hi @Sakthivel ,

1) Could you  share what is the difference between these MCU variants ?  

2023-05-10_14h57_41.png
2) There's no specific board with the TC397XX256F300 actually, however, it can use the KIT_A2G_TC377_5V_TRB_S (with socket) to install this chip easily for evaluation.
BR,
Jeremy

0 Likes

Hi Jeremy_Zhou,

Thanks for your support,

1. Could you please share how to upload firmware ? through which connector in the development board initial firmware will be uploaded ?  and is there any programmer that is available?

Thanks,
Sakthivel   

0 Likes
Jeremy_Z
Moderator
Moderator
Moderator
1000 replies posted 250 sign-ins 100 likes received

Hi @Sakthivel 
1) Could you please share how to upload firmware? through which connector in the development board initial firmware will be uploaded? and is there any programmer that is available?
-- There's an Infineon On-Chip Memory Programming Tool (MemTool) to program the target chip by using DAS Wigler or a standard RS232 port, for the KIT_A2G_TC377_5V_TRB_S board, the USB connector is used for connection to a PC. Via the USB it is possible to power the board, using the ASCLIN0 as serial connection via USB and Debugging via DAS, so it allows the MemTool to establish a connection with the board.

BR,

Jeremy

0 Likes
Sakthivel
Level 3
Level 3
50 sign-ins 10 questions asked First like received

Hi Jeremy,

Thanks for your support,

  1. Could you please confirm in the KIT_A2G_TC377_5V_TRB_S kit if we mount "TC397XX256F300SBDKXUMA1 " MCU, Programming can be done through USB connector and debugging can be done by JATAG which is from mini wiggler ? 
  2. RS232 standard connector you are mentioning is that in our custom board we need RS232 to UART bridge through which Programming can be done, in case of development board the programming of MCU is possible only through the USB to UART bridge IC and JTAG (which is from the mini wiggler) is our understanding is correct?
  3. From the Tri board user manual we are having the following questions a, What is  Astep, Bstep MCUs of TC397 which is mentioned?   b, We need to evaluate the Ethernet interface, it is possible with  KIT_A2G_TC377_5V_TRB_S if we mount "TC397XX256F300SBDKXUMA1" mcu right?

 

Sakthivel_0-1683802539936.png

 

  1. There are Two different LFBGA-292 pinouts available in datasheet, may i know which pin outs should i follow in my design for the MCU part "TC397XX256F300SBDKXUMA1"?
  2. Through which Debugging options like (JTAG, DAP, OCDS1) from KIT_DAP_MINIWIGGLER_USB,  firmware uploading and debugging is possible?

Thanks,
Sakthivel

 

0 Likes
MoD
Employee
Employee
50 likes received 500 replies posted 100 solutions authored

1. Yes, you can use TC397XX also in the board KIT_A2G_TC377_5V_TRB_S

2. In your custom board you need the DAP connector and a miniWiggler as external device. On the TriBoard is the miniWiggler on board and is not needed for this board but he is needed for custom boards.

3. There existing different device steps, from "TC397XX256F300SBDKXUMA1" it is the bold part, here BD step. In any case, you will not get A-step anymore, only B-steps are available.

4. You must use the LFBGA-292 Package Variant Pin Configuration for TC397XX. The other LFBGA-292 ADAS Package Variant Pin Configuration is only for TC397XA and TC397QA

0 Likes
Sakthivel
Level 3
Level 3
50 sign-ins 10 questions asked First like received

Thanks for your response MoD,

1. We understand that TC397XX can be used in KIT_A2G_TC377_5V_TRB_S. Could you please confirm that in the kit there are various debugging options available, through which debugging options like JTAG, DAP, and OCDS1 from  DAP_MINIWIGGLER, firmware uploading and debugging are possible?

2. as @Jeremy_Z  mentioned about standard Rs232 connector, but there is no RS232 connector available in the kit, can you explain again?  

Thanks,

Sakthivel

0 Likes
MoD
Employee
Employee
50 likes received 500 replies posted 100 solutions authored

1. Yes, there are different ways for debugger connection

2. RS232 is done via USB, there is no SUB-D connector used.

Jeremy_Z
Moderator
Moderator
Moderator
1000 replies posted 250 sign-ins 100 likes received

Hi @Sakthivel 

1) We understand that TC397XX can be used in KIT_A2G_TC377_5V_TRB_S. Could you please confirm that in the kit there are various debugging options available, through which debugging options like JTAG, DAP, and OCDS1 from DAP_MINIWIGGLER, firmware uploading and debugging are possible?
-- Yes, and please refer to the document to learn more details.
2) But there is no RS232 connector available in the kit, can you explain again?
-- After the first connection of the board to a PC via the USB, the needed driver will be installed automatically. During this, there will be created a new COM port on the PC. This COM port can be used to communicate with the board via ASCLIN0 of the device, it's the RS232 connector implementation on the board.

BR,

Jeremy

0 Likes
Sakthivel
Level 3
Level 3
50 sign-ins 10 questions asked First like received

Hi,

1. we found the part "TC397XX256F300SBDKXUMA1" now became not recommended for new design (NRND), could you please confirm the same? and if the part is NRND please share the PCN.

2. Please find our MCU requirement and kindly suggest the alternate MCU part in-replacement to "TC397XX256F300SBDKXUMA1". 

-> Requirements:

 #12 Number of CAN, one Ethernet RGMII, I2C and #5 Nos of GPIOs. and the part should be available for next 5 years.

Sakthivel_0-1683893661645.png

                         Block Diagram of our application

0 Likes
Jeremy_Z
Moderator
Moderator
Moderator
1000 replies posted 250 sign-ins 100 likes received

Hi @Sakthivel 
Could you please confirm the same?
- Yes, it's not recommended for the new design.
2) Please consider the SAK-TC377TX-96F300S AB or SAK-TC3E7QX-192F300S AA as the alternative.
BR,
Jeremy

0 Likes

Hi,

1. We found few differences between the original part "SAK-TC397XX-256F300S BD" and an alternate part " SAK-TC377TX-96F300S AB" could you please confirm that, these are the only differences that we need to consider for design or any other differences we need to take care of, (Note: differences are highlighted )

Sakthivel_0-1684215521072.png

2. Could you please share the Pin mux table for " SAK-TC377TX-96F300S AB " MCU, we need to verify if there is any two required peripheral are muxed with each other, or please share if there is any tools available to know the pin muxing of an MCU.

0 Likes
Sakthivel
Level 3
Level 3
50 sign-ins 10 questions asked First like received

Hi,

1. We have found some differences while comparing the alternate part :- SAK-TC377TX-96F300S AB with the original part :- SAK-TC397XX-256F300S BD. Could you please confirm that this is the only difference or if there are any other major differences present that we need to take care of at the design level?

Sakthivel_0-1684154571184.png

2.Please share the PIN MUX table for both the MCUs to compare pin levels and any pin mixing conflicts present in the required peripherals. as shared above our requirement is parallel operation of #12 Can and #1 Ethernet and few GPIOs there should not be any pin muxing with these pins. if not please share any tools to identify the pin muxing.

0 Likes
Jeremy_Z
Moderator
Moderator
Moderator
1000 replies posted 250 sign-ins 100 likes received

Hi @Sakthivel ,

Sorry for replying late.
1) Actually, the above tables basically illustrate the differences.
2) First, please compare their related datasheet to check the pin compatibility, next, the AURIX™ Development Studio provides the Pin Mapper tools to help you configure pins and generate the codes, plus, it can ensure no pin conflicts exist.

2023-05-22_13h27_58.png
BR,
Jeremy

0 Likes
Sakthivel
Level 3
Level 3
50 sign-ins 10 questions asked First like received

Hi Jeremy,

Thanks for your support,

could you please confirm, Is there any active part available in TC39x series MCUs? 

0 Likes
Jeremy_Z
Moderator
Moderator
Moderator
1000 replies posted 250 sign-ins 100 likes received

Hi @Sakthivel ,

I'd highly recommend you use the product selector to choose the expected MCU.

2023-05-24_15h13_57.png
BR,
Jeremy

Sakthivel
Level 3
Level 3
50 sign-ins 10 questions asked First like received

Hi,

1. We know the part "SAK-TC397XX-256F300S BD" is not recommended for the new design. So could you please tell us, till which date we are able to procure the part?  and when Infenion planned to stop the production.

2. Our product MCU requirement is 6 Tricore CPUs, 10 CAN peripherals, 1 gigabit Ethernet, and ISO 26262 compliance, so we could find only these MCUs, TC39x and TC38x, so please list the MCUs with their last-time-buy details.

3. Is there any other MCU in the infenion that has the above-mentioned features and is still in an active state? If so, please list the MCUs.

4. In general, if the product status is "not for new design or discontinued," how long will production continue?

 

Thanks,
Sakthivel

0 Likes
Jeremy_Z
Moderator
Moderator
Moderator
1000 replies posted 250 sign-ins 100 likes received

Hi @Sakthivel 
Infineon’s longevity program ensures that based on Infineon current estimate of and subject to the actual product demand, Infineon currently plans to have available the participating products, listed below, or a form, fit and function-compatible device, for a minimum of 15 years from the date of first sale (the “Supply Period”).
Plus, please learn the supply period of specific chips via the link.
BR,
Jeremy

0 Likes
lock attach
Attachments are accessible only for community members.
Sakthivel
Level 3
Level 3
50 sign-ins 10 questions asked First like received

Hi,

Our parts (TC39x and TC38x, series ) are not listed in the longevity program, please share the last time buy details of the requested parts.

Sakthivel
Level 3
Level 3
50 sign-ins 10 questions asked First like received

Hi,

If the entire HEXA (SIX) core Auric series MCUs are end of life, can we expect any replacement parts with the same TC39x footprint in the feature? If so, please share the exact date.

 

Thanks,

Sakthivel

Jeremy_Z
Moderator
Moderator
Moderator
1000 replies posted 250 sign-ins 100 likes received

Hi @Sakthivel ,
1) Can we expect any replacement parts with the same TC39x footprint in the feature?
-- First, I definitely understand your worry, next, according to the production longevity policy, Infineon promises a minimum of 15 years from the date of the first sale, further, the TC4xx is coming soon, which makes the customers to update the system easily in the future.
BR,
Jeremy

0 Likes
Sakthivel
Level 3
Level 3
50 sign-ins 10 questions asked First like received

Hi @Jeremy_Z,

Thanks for your understanding,

1. Can you share the first sale details for the parts "TC397XX256F300SBDKXUMA1" MCU? we don't find it in longevity sheet.

2. So can you confirm that the TC4xx series MCU has 6 core and it is PIN compatible and Foot print compatible with "TC397XX256F300SBDKXUMA1" MCU 

Thanks,

Sakthivel

0 Likes
Jeremy_Z
Moderator
Moderator
Moderator
1000 replies posted 250 sign-ins 100 likes received

Hi @Sakthivel ,
1. Can you share the first sale details for the parts "TC397XX256F300SBDKXUMA1" MCU? we don't find it in longevity sheet.
-- Sorry, I don't find the exact information of the first sale day, as I know, the TC397/387 was launched in early of 2020.
2. So can you confirm that the TC4xx series MCU has 6 core and it is PIN compatible and Footprint compatible with "TC397XX256F300SBDKXUMA1" MCU
-- Yes.
BR,
Jeremy