SK-TDA4VM: The EVM board often crashes when running or no-loading

Hi Nancy,

The first thing we can check is if the crash is power or heat related.

Could you advise customer to do the following:

• Share board revision number, there should be a sticker on the under side of the board saying something like PROC112A
• Print out temperature when crash occurs: https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-sk-tda4vm/08_02_00/exports/docs/performance_visualizer.html#generating-performance-logs
• Ensure power supply being used has similar power rating as the recommended power supply (20V/65W): https://www.digikey.com/en/products/detail/qualtek/QADC-65-20-08CB/9771104 

Regards,

Takuma

Takuma Fujiwara said:

Share board revision number, there should be a sticker on the under side of the board saying something like PROC112A

PROC112A1

Takuma Fujiwara said:

Print out temperature when crash occurs: https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-sk-tda4vm/08_02_00/exports/docs/performance_visualizer.html#generating-performance-logs

root@tda4vm-sk:/opt/edge_ai_apps/apps_python#                                   
root@tda4vm-sk:/opt/edge_ai_apps/apps_python#                                   
root@tda4vm-sk:/opt/edge_ai_apps/apps_python#                                   
root@tda4vm-sk:/opt/edge_ai_apps/apps_python# [ 1033.118359] Insufficient stack!
[ 1033.118361] ESR: 0x96000047 -- DABT (current EL)                             
[ 1033.118362] FAR: 0xffff800011ffffe0                                          
[ 1033.118363] Task stack:     [0xffff8000116a0000..0xffff8000116b0000]         
[ 1033.118364] IRQ stack:      [0xffff800011ff0000..0xffff800012000000]         
[ 1033.118366] Overflow stack: [0xffff00087fa802b0..0xffff00087fa812b0]         
[ 1033.118367] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G           O      5.10.11
[ 1033.118369] Hardware name: Texas Instruments J721E SK (DT)                   
[ 1033.118370] pstate: 40000085 (nZcv daIf -PAN -UAO -TCO BTYPE=--)             
[ 1033.118371] pc : gic_handle_irq+0x4/0x128                                    
[ 1033.118372] lr : el1_irq+0xcc/0x180                                          
[ 1033.118373] sp : ffff800012000000                                            
[ 1033.118374] x29: ffff8000116aff40 x28: ffff00082016a800                      
[ 1033.118377] x27: 0000000000000000 x26: ffff800012000000                      
[ 1033.118379] x25: ffff800011ff0000 x24: 00000000000000e0                      
[ 1033.118382] x23: 0000000040000005 x22: ffff800010a84398                      
[ 1033.118384] x21: ffff8000116aff60 x20: 0000ffffffffffff                      
[ 1033.118387] x19: ffff8000116afe10 x18: 0000000000000000                      
[ 1033.118389] x17: 0000000000000000 x16: 0000000000000000                      
[ 1033.118391] x15: 0000000000000000 x14: 0000000000000000                      
[ 1033.118393] x13: 0000000000000001 x12: 0000000000000000                      
[ 1033.118395] x11: 0000000000000000 x10: 00000000000009a0                      
[ 1033.118398] x9 : ffff8000116afec0 x8 : ffff00082016b200                      
[ 1033.118400] x7 : 0000000000000000 x6 : ffff00082016a800                      
[ 1033.118403] x5 : ffff00087fa8bd40 x4 : ffff00087fa8be40                      
[ 1033.118405] x3 : 0000000000000000 x2 : 0000000000077796                      
[ 1033.118407] x1 : ffff8000104b7ea0 x0 : ffff8000116afe10                      
[ 1033.118410] Kernel panic - not syncing: kernel stack overflow                
[ 1033.118411] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G           O      5.10.11
[ 1033.118413] Hardware name: Texas Instruments J721E SK (DT)                   
[ 1033.118414] Call trace:                                                      
[ 1033.118415]  dump_backtrace+0x0/0x1a0                                        
[ 1033.118416]  show_stack+0x18/0x68                                            
[ 1033.118417]  dump_stack+0xd0/0x12c                                           
[ 1033.118418]  panic+0x16c/0x334                                               
[ 1033.118419]  nmi_panic+0x8c/0x90                                             
[ 1033.118420]  handle_bad_stack+0x11c/0x148                                    
[ 1033.118420]  __bad_stack+0x9c/0xa0                                           
[ 1033.118422]  gic_handle_irq+0x4/0x128                                        
[ 1033.118423]  arch_cpu_idle+0x18/0x28                                         
[ 1033.118424]  default_idle_call+0x20/0x68                                     
[ 1033.118425]  do_idle+0xc0/0x128                                              
[ 1033.118425]  cpu_startup_entry+0x24/0x60                                     
[ 1033.118427]  secondary_start_kernel+0x14c/0x178                              
[ 1033.118442] SMP: stopping secondary CPUs                                     
[ 1033.118443] Kernel Offset: disabled                                          
[ 1033.118444] CPU features: 0x0040022,20006008                                 
[ 1033.118445] Memory Limit: none                                               

Summary of CPU load,
====================

CPU: mpu1_0: TOTAL LOAD =   0. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU: mcu2_0: TOTAL LOAD =   1. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU: mcu2_1: TOTAL LOAD =   1. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU:  c6x_1: TOTAL LOAD =   0. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU:  c6x_2: TOTAL LOAD =   0. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU:  c7x_1: TOTAL LOAD =   0. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )


HWA performance statistics,
===========================



DDR performance statistics,
===========================

DDR: READ  BW: AVG =    514 MB/s, PEAK =   2326 MB/s
DDR: WRITE BW: AVG =      9 MB/s, PEAK =   1103 MB/s
DDR: TOTAL BW: AVG =    523 MB/s, PEAK =   3429 MB/s


SoC temperature statistics
==========================

CPU:    80.46 degree Celsius
WKUP:   79.03 degree Celsius
C7X:    80.87 degree Celsius
GPU:    81.27 degree Celsius
R5F:    80.06 degree Celsius

Summary of CPU load,
====================

CPU: mpu1_0: TOTAL LOAD =   1.56 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU: mcu2_0: TOTAL LOAD =   1. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU: mcu2_1: TOTAL LOAD =   1. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU:  c6x_1: TOTAL LOAD =   1. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU:  c6x_2: TOTAL LOAD =   0. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU:  c7x_1: TOTAL LOAD =   0. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )


HWA performance statistics,
===========================



DDR performance statistics,
===========================

DDR: READ  BW: AVG =    513 MB/s, PEAK =   2284 MB/s
DDR: WRITE BW: AVG =      9 MB/s, PEAK =   1218 MB/s
DDR: TOTAL BW: AVG =    522 MB/s, PEAK =   3502 MB/s


SoC temperature statistics
==========================

CPU:    79.65 degree Celsius
WKUP:   79.24 degree Celsius
C7X:    80.87 degree Celsius
GPU:    81.88 degree Celsius
R5F:    80.26 degree Celsius

Summary of CPU load,
====================

CPU: mpu1_0: TOTAL LOAD =   0. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU: mcu2_0: TOTAL LOAD =   1. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU: mcu2_1: TOTAL LOAD =   1. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU:  c6x_1: TOTAL LOAD =   0. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU:  c6x_2: TOTAL LOAD =   0. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU:  c7x_1: TOTAL LOAD =   0. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )


HWA performance statistics,
===========================



DDR performance statistics,
===========================

DDR: READ  BW: AVG =    514 MB/s, PEAK =   2032 MB/s
DDR: WRITE BW: AVG =      8 MB/s, PEAK =    984 MB/s
DDR: TOTAL BW: AVG =    522 MB/s, PEAK =   3016 MB/s


SoC temperature statistics
==========================

CPU:    80.46 degree Celsius
WKUP:   79.03 degree Celsius
C7X:    80.46 degree Celsius
GPU:    81.68 degree Celsius
R5F:    79.85 degree Celsius

Summary of CPU load,
====================

CPU: mpu1_0: TOTAL LOAD =   0. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU: mcu2_0: TOTAL LOAD =   1. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU: mcu2_1: TOTAL LOAD =   1. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU:  c6x_1: TOTAL LOAD =   0. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU:  c6x_2: TOTAL LOAD =   0. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU:  c7x_1: TOTAL LOAD =   1. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )


HWA performance statistics,
===========================



DDR performance statistics,
===========================

DDR: READ  BW: AVG =    513 MB/s, PEAK =   2341 MB/s
DDR: WRITE BW: AVG =      8 MB/s, PEAK =   1226 MB/s
DDR: TOTAL BW: AVG =    521 MB/s, PEAK =   3567 MB/s


SoC temperature statistics
==========================

CPU:    80.26 degree Celsius
WKUP:   79.03 degree Celsius
C7X:    81.27 degree Celsius
GPU:    81.47 degree Celsius
R5F:    80.26 degree Celsius

Summary of CPU load,
====================

CPU: mpu1_0: TOTAL LOAD =   0. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU: mcu2_0: TOTAL LOAD =   1. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU: mcu2_1: TOTAL LOAD =   1. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU:  c6x_1: TOTAL LOAD =   0. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU:  c6x_2: TOTAL LOAD =   0. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU:  c7x_1: TOTAL LOAD =   0. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )


HWA performance statistics,
===========================



DDR performance statistics,
===========================

DDR: READ  BW: AVG =    513 MB/s, PEAK =   1852 MB/s
DDR: WRITE BW: AVG =      8 MB/s, PEAK =    962 MB/s
DDR: TOTAL BW: AVG =    521 MB/s, PEAK =   2814 MB/s


SoC temperature statistics
==========================

CPU:    80.46 degree Celsius
WKUP:   79.65 degree Celsius
C7X:    80.67 degree Celsius
GPU:    81.68 degree Celsius
R5F:    80.26 degree Celsius

Summary of CPU load,
====================

CPU: mpu1_0: TOTAL LOAD =   0. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU: mcu2_0: TOTAL LOAD =   1. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU: mcu2_1: TOTAL LOAD =   1. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU:  c6x_1: TOTAL LOAD =   0. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU:  c6x_2: TOTAL LOAD =   1. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )
CPU:  c7x_1: TOTAL LOAD =   0. 0 % ( HWI =   0. 0 %, SWI =   0. 0 % )


HWA performance statistics,
===========================



DDR performance statistics,
===========================

DDR: READ  BW: AVG =    515 MB/s, PEAK =   2193 MB/s
DDR: WRITE BW: AVG =      8 MB/s, PEAK =   1228 MB/s
DDR: TOTAL BW: AVG =    523 MB/s, PEAK =   3421 MB/s


SoC temperature statistics
==========================

CPU:    80.06 degree Celsius
WKUP:   79.24 degree Celsius
C7X:    81.27 degree Celsius
GPU:    81.88 degree Celsius
R5F:    80.87 degree Celsius

Network error: Software caused connection abort

────────────────────────────────────────────────────────────────────────────────

Session stopped
    - Press <return> to exit tab
    - Press R to restart session
    - Press S to save terminal output to file

Takuma Fujiwara said:

Ensure power supply being used has similar power rating as the recommended power supply (20V/65W): https://www.digikey.com/en/products/detail/qualtek/QADC-65-20-08CB/9771104 

The power supply conforms to the rated power of (20V/65W), and the maximum output supports 20v/3.25A.

The customer tried to re-flash the SD card image (ti-processor-sdk-linux-sk-tda4vm-etcher-image.zip — 1449343 K) to reproduce the bug, ran the Single input multi inference demo and recorded the temperature log for a few minutes and the display output card appeared Dead but minicom still shows the demo running and the temperature monitoring log continues. Then he quit the demo, re-entered any demo with Segmentation fault (core dumped) errors (listed below) and couldn't run the demo. After Reset, the demo can run, but crashes from time to time (the latest crash log and the corresponding temperature during no-load will be listed below, the monitor is still displaying the wallpaper when it crashes, but no operations can be performed, including UART and SSH control)

Segmentation fault (core dumped)：

lassification.yamlt/edge_ai_apps/apps_python# ./app_edgeai.py ../configs/image_ 
2022-04-18 21:16:39,252 INFO Could not find libdlr.so in model artifact. Using o
APP: Init ... !!!                                                               
MEM: Init ... !!!                                                               
MEM: Initialized DMA HEAP (fd=4) !!!                                            
MEM: Init ... Done !!!                                                          
IPC: Init ... !!!                                                               
IPC: Init ... Done !!!                                                          
REMOTE_SERVICE: Init ... !!!                                                    
REMOTE_SERVICE: Init ... Done !!!                                               
   870.565568 s: GTC Frequency = 200 MHz                                        
APP: Init ... Done !!!                                                          
   870.565631 s:  VX_ZONE_INIT:Enabled                                          
   870.565640 s:  VX_ZONE_ERROR:Enabled                                         
   870.565646 s:  VX_ZONE_WARNING:Enabled                                       
   870.566199 s:  VX_ZONE_INIT:[tivxInitLocal:130] Initialization Done !!!      
   870.566450 s:  VX_ZONE_INIT:[tivxHostInitLocal:86] Initialization Done for H!
   870.566753 s:  VX_ZONE_ERROR:[ownContextCreateCmdObj:161] context object desd
   870.566766 s:  VX_ZONE_ERROR:[vxCreateContext:946] context objection creatiod
   870.566776 s:  VX_ZONE_ERROR:[vxGetStatus:713] Reference is NULL             
   870.566783 s:  VX_ZONE_ERROR:[tivxAddKernelTIDL:233] Unable to allocate userD
   870.566789 s:  VX_ZONE_ERROR:[vxGetStatus:713] Reference is NULL             
   870.566794 s:  VX_ZONE_ERROR:[vxGetStatus:713] Reference is NULL             
   870.566799 s:  VX_ZONE_ERROR:[vxGetStatus:713] Reference is NULL             
   870.566805 s:  VX_ZONE_ERROR:[vxGetStatus:713] Reference is NULL             
   870.566811 s:  VX_ZONE_ERROR:[vxSetReferenceName:659] Invalid reference      
   870.566819 s:  VX_ZONE_ERROR:[tivxMapTensorPatch:611] Invalid tensor referene
Segmentation fault (core dumped) 

Crashes from time to time after reset (this time it crashes after reset login):

***************************************************************                 
***************************************************************                 
[  OK  ] Started Print notice about GPLv3 packages.                             
[  OK  ] Started weston.service.                                                
         Starting DEMO...                                                       
         Starting telnetd.service...                                            
[  OK  ] Started DEMO.                                                          
[  OK  ] Started telnetd.service.                                               
[   15.936058] PVR_K:  1047: RGX Firmware image 'rgx.fw.22.104.208.318' loaded  
[   16.768461] am65-cpsw-nuss 46000000.ethernet eth0: Link is Up - 1Gbps/Full -f
[   16.777005] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready          
                                                                                
 _____                    _____           _         _                           
|  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_                         
|     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|                        
|__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|                          
              |___|                    |___|                                    
                                                                                
Arago Project http://arago-project.org tda4vm-sk ttyS2                          
                                                                                
Arago 2021.09 tda4vm-sk ttyS2                                                   
                                                                                
tda4vm-sk login: root                                                           
root@tda4vm-sk:/opt/edge_ai_apps# cd [   27.610545] Unable to handle kernel pag0
[   27.618454] Mem abort info:                                                  
[   27.621237]   ESR = 0x96000006                                               
[   27.624279]   EC = 0x25: DABT (current EL), IL = 32 bits                     
[   27.629575]   SET = 0, FnV = 0                                               
[   27.632616]   EA = 0, S1PTW = 0                                              
[   27.635743] Data abort info:                                                 
[   27.638611]   ISV = 0, ISS = 0x00000006                                      
[   27.642432]   CM = 0, WnR = 0                                                
[   27.645387] swapper pgtable: 64k pages, 48-bit VAs, pgdp=0000000082f40000    
[   27.652156] [ffff03702418b920] pgd=00000008fffd0003, p4d=00000008fffd0003, p0
[   27.662749] Internal error: Oops: 96000006 [#1] PREEMPT SMP                  
[   27.668303] Modules linked in: bluetooth ecdh_generic ecc rfkill xhci_plat_h6
[   27.682983] Unable to handle kernel paging request at virtual address ff9f000
[   27.722389] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G           O      5.10.11
[   27.730278] Mem abort info:                                                  
[   27.738777] Hardware name: Texas Instruments J721E SK (DT)                   
[   27.741556]   ESR = 0x96000004                                               
[   27.747022] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO BTYPE=--)             
[   27.750060]   EC = 0x25: DABT (current EL), IL = 32 bits                     
[   27.756054] pc : am65_cpsw_nuss_rx_poll+0xdc/0x370                           
[   27.761336]   SET = 0, FnV = 0                                               
[   27.766109] lr : am65_cpsw_nuss_rx_poll+0xc0/0x370                           
[   27.769147]   EA = 0, S1PTW = 0                                              
[   27.773919] sp : ffff80001138fda0                                            
[   27.777043] Data abort info:                                                 
[   27.780343] x29: ffff80001138fda0                                            
[   27.783207]   ISV = 0, ISS = 0x00000004                                      
[   27.783209] x28: ffff000824001a40                                            
[   27.786594]   CM = 0, WnR = 0                                                
[   27.790411]                                                                  
[   27.793797] [ff9f000820470000] address between user and kernel address ranges
[   27.796748] x27: ffff000824001a30 x26: 0000000000000122                      
[   27.810633] x25: 000000000000012c x24: 0000000000000000                      
[   27.815928] x23: 0000000000000040 x22: ffff000824120080                      
[   27.821224] x21: ffff000824121530 x20: 0000000000000000                      
[   27.826519] x19: ffff000824001a00 x18: 0000000000000000                      
[   27.831816] x17: 0000000000000000 x16: 0000000000000000                      
[   27.837112] x15: 0000000000000000 x14: 0000000000000000                      
[   27.842408] x13: 003d090000000000 x12: 00003d0900000000                      
[   27.847703] x11: 0000000000000040 x10: ffff8000111da400                      
[   27.852998] x9 : ffff8000111da3f8 x8 : ffff000840000270                      
[   27.858294] x7 : 0000000000000000 x6 : ffff80001138fe30                      
[   27.863590] x5 : 0000000000000008 x4 : ffff000824001a40                      
[   27.868885] x3 : 0000000000000058 x2 : 0000000000000368                      
[   27.874180] x1 : ffff00082418bc80 x0 : ffff03702418b918                      
[   27.879476] Call trace:                                                      
[   27.881912]  am65_cpsw_nuss_rx_poll+0xdc/0x370                               
[   27.886344]  net_rx_action+0x118/0x380                                       
[   27.890080]  efi_header_end+0x120/0x268                                      
[   27.893901]  irq_exit+0xc0/0xe0                                              
[   27.897030]  __handle_domain_irq+0x68/0xc0                                   
[   27.901113]  gic_handle_irq+0x58/0x128                                       
[   27.904847]  el1_irq+0xcc/0x180                                              
[   27.907975]  arch_cpu_idle+0x18/0x28                                         
[   27.911538]  default_idle_call+0x20/0x68                                     
[   27.915446]  do_idle+0xc0/0x128                                              
[   27.918573]  cpu_startup_entry+0x28/0x60                                     
[   27.922481]  rest_init+0xd4/0xe4                                             
[   27.925699]  arch_call_rest_init+0x10/0x1c                                   
[   27.929779]  start_kernel+0x48c/0x4c4                                        
[   27.933430] Code: 51000400 b9006fe2 52806d02 9ba20400 (f9400419)             
[   27.939509] ---[ end trace b5919ffb93f953aa ]---                             
[   27.944110] Kernel panic - not syncing: Oops: Fatal exception in interrupt   
[   27.950964] SMP: stopping secondary CPUs                                     
[   29.023873] SMP: failed to stop secondary CPUs 0-1                           
[   29.028652] Kernel Offset: disabled                                          
[   29.032126] CPU features: 0x0040022,20006008                                 
[   29.036380] Memory Limit: none                                               
[   29.039424] ---[ end Kernel panic - not syncing: Oops: Fatal exception in in-

Hi Nancy,

The board crashing after logging in and running no applications is not a known issue - we have not been able to reproduce this behavior on our boards so far.

For the errors from the demo, we have seen some instabilities using file input on some of our demos which we are working to fix. 

A couple of questions for the customer:

• Are you using file input, or a live input from a camera when running the demo?
• After power-on and running no application, if you boot 10 times, how many time is the crash observed when sitting idle at login screen? And how long does it take?
• If you have multiple boards, can this be observed on all boards?
• If you have multiple SD cards, can this be observed on all SD cards?

Regards,

Takuma

Hi Takuma,

Got some updates from the customer side as follows:

Takuma Fujiwara said:

Are you using file input, or a live input from a camera when running the demo?

When running the demo, the customer using file input and the issue not only occurs when running the demo. 

Takuma Fujiwara said:

After power-on and running no application, if you boot 10 times, how many time is the crash observed when sitting idle at login screen? And how long does it take?

As you said, after power-on and running no application, the crash occurs occasionally(at random).  In the previous tests, the minimum time was about three minutes after power-on and I'm afraid they are not able to boot 10 times since they don't have much time.

Takuma Fujiwara said:

If you have multiple boards, can this be observed on all boards?

They do have multiple boards, and for now with the same SD card image on the bad board and other peripherals, only replace the same board model and do not observe a similar issue. So the customer suspects that the board has a h/w problem.

Takuma Fujiwara said:

If you have multiple SD cards, can this be observed on all SD cards?

They've tried to replace other SD card but this still happens. 

Assuming the following procedure:

A. after flashing the SD card image, load the development board and power-on.
B. Run demo for about ten minutes
C. the display is stuck, and the demo is terminated via the keyboard, and the program re-runs failed
D. after rebooting the board, the system crash periodically.

The point is replacing the same type of board with the same environment does not occur with other development boards of the same type. Could you please help determine if there is a quality problem with this board?

Thanks and regards,

Cherry

Hi,

May I know is there any updates?

Thanks and regards,

Cherry

Hi Cherry,

Currently checking with HW app team about the process for determining/reporting a defective board.

Can you confirm that the random kernel crashes are seen only on 1 "bad" board and switching boards fixes the issue? Or do multiple boards exhibit the same failure?

Regards,

Takuma