TDA4VM: run app_tidl_od demo on EVM about 48 hours, C7x aborted

Hello Sam,

We have seen a similar issue in the past, but could you do a few things to debug:

• If you have not submitted the schematic of the custom board to TI for review, please do so. If there is a local FAE, they will be able to help enter the schematic review request. This behavior can be seen on boards with bad chips as well as boards that have issues with the design.
• Also send the chip ID of the custom boards that see the failure.
• Run your tests with lower C7x frequency. C7x frequency can be lowered to half the default speed (1GHz -> 500MHz) using this command: k3conf set clock 15 0 500000000. In the past, we have seen that lowering the C7x frequency works around the issue on boards that fail due to bad chip.

Regards,

Takuma

Hello Takuma,

Thanks for your reply.

• We have submitted the schematic of our board to TI for review,and there is no issue with the design.
• I made a mistake on EVM chip ID,this is the correct chip ID:
  root@j7-evm:~# devmem2 0x43000020
  /dev/mem opened.
  Memory mapped at address 0xffff86a40000.
  Read at address  0x43000020 (0xffff86a40020): 0x14020001
  root@j7-evm:~# devmem2 0x43000024
  /dev/mem opened.
  Memory mapped at address 0xffffa4af0000.
  Read at address  0x43000024 (0xffffa4af0024): 0x04040001
  root@j7-evm:~# devmem2 0x43000028
  /dev/mem opened.
  Memory mapped at address 0xffff9ca80000.
  Read at address  0x43000028 (0xffff9ca80028): 0x0800FA5A
  root@j7-evm:~# devmem2 0x4300002c
  /dev/mem opened.
  Memory mapped at address 0xffffa3a10000.
  Read at address  0x4300002C (0xffffa3a1002c): 0x12017008
  root@j7-evm:~# devmem2 0x4300002C
  /dev/mem opened.
  Memory mapped at address 0xffff9bdf0000.
  Read at address  0x4300002C (0xffff9bdf002c): 0x12017008
• Here are 4 chip ID of our boards that  see the failure as follow: 

                 22FA0002040500040804344318017010 

                 5E0E000204050004080434430F013010

                 696A00220405000408043A1D02012003

                 62F600020405000408043A1D0300D004

• We are running app_tidl_od demo on our 3 boards with 500MHZ C7X frequency.We are waitting for the result.And I will tell you the result.
• What else can we do about this problem?

Regards

Hi Sam,

If this is the same issue we have seen in the past, this will just be a matter of switching out the chips. The chip ID will be enough to determine if this switch is necessary. Continuing the tests at 500MHz C7x frequency will also help in determining if this is the same issue. Another thing that could be done on your side would be to review the schematics again, especially the schematics related to PDN.

Internally, I will be getting in contact with some of our product engineers to determine details about the chips using the ID you shared with me. I will also ping some of our hardware applications engineers to re-review your schematics. However, this process may take a week or two. 

Regardless of how long the process takes, I will update you on the status next week at the latest.

Regards,

Takuma

Hello Takuma,

Thanks for your reply.

• We submitted the schematic of our board to TI for review again yesterday.
• Three boards that runing app_tidl_od demo at 500MHZ C7x frequency are all aborted after different time.

Looking forward to your reply.

Regards,

Sam

Hello Sam,

Do you have the link to the previous and current schematic review and/or the email of the FAE that helped you submit the schematic?

Regards,

Takuma

Hello Takuma,

Here is the email of the FAE Cary Zhang : cary-zhang1@ti.com You can contact him.

Regards,

Sam

Hello Sam, 

Thank you. I will try contacting him.

Some good news is that I was able to confirm with our product engineers that the chips used in the custom board have been fully tested (the chip on the EVM will need a bit more time to confirm). Once we also verify that the board design has no issues, we can focus on the debug from a software standpoint.

Regards,

Takuma

Hello Takuma,

Thanks for your reply.

That is a good news,and we can focus on the software standpoint as you said.I will tell you the app_tild_od demo result that c7x_1.cfg was modified on our two boards at this thread.Looking forward to your other good news.

Regards,

Sam

Hi Takuma,

We modified the c7x_1.cfg as your suggestion, we ran app_tidl_od demo on three our boards.We found one aborted today, the other two are working fine.It has been about two days since we did this test.We will do more test and let you konw the result.

Regards,

Sam

Hi Takuma,

We finished full test yesterday on our boards.Yes, it works.After more than five days, our boards are still ok.At the same time, your suggestions are able to fix the C7x abort issue.Thanks for your support.

Regards,

Sam