Compiler/DRA745: EARLY DCAN fail with ERROR: line 149: E_alreadyDefined: Hwi already defined: intr# 28

Hi Chokri,

Have you made any other changes apart from 'DCAN_INCLUDE=yes' in the SDK? If yes, can you please check if you are assigning interrupt no. 28 to anything else?

Thanks & Regards,
Vivek Dhande.

Texas Instruments (India) Pvt Ltd

Hello Vivek,

Im working in the same project and  same team as chokri , So for the changes that we  made are listed below:

in the Rules.make:

MAKECONFIG?=tda2xx_evm_robust_rvc

in vision_sdk/apps/configs/tda2xx_evm_robust_rvc/cfg.mk:

PROC_IPU1_0_INCLUDE=yes
VSDK_BOARD_TYPE=TDA2XX_EVM
PROFILE ?= debug
DCAN_INCLUDE=yes
IPU_PRIMARY_CORE=ipu2
IPU_SECONDARY_CORE=ipu1_0

in vision_sdk/apps/src/rtos/usecases/vip_single_rvc_cam_view_crc/cfg.mk:

ALG_swcrc=yes
ALG_rvcDiags=yes

NEED_PROC_IPU2=yes
NEED_PROC_DSP1=yes
NEED_PROC_IPU1_0=yes

the remoteproc show these logs :

cat /d/remoteproc/remoteproc1/trace0
[0][ 0.000] 18 Resource entries at 0x99000000
[0][ 0.000] 265.639083 s: SYSTEM: System Common Init in progress !!!
[1][ 0.001] [t=0x000a277e] ti.ipc.family.vayu.VirtQueue: vring: 0 0x60000000 (0x3000)
[1][ 0.001]
[1][ 0.001] [t=0x000a6750] ti.ipc.family.vayu.VirtQueue: vring: 1 0x60004000 (0x3000)
[1][ 0.001]
[1][ 0.002] [t=0x000a8514] ti.ipc.family.vayu.VirtQueue: VirtQueue_startup: VDEV status: 0x0
[1][ 0.002]
[1][ 0.002] [t=0x000a9915] ti.ipc.family.vayu.VirtQueue: VirtQueue_startup: Polling VDEV status...
[1][ 0.002]
[0][ 0.010] 265.648630 s: SYSTEM: IPC init in progress !!!
[0][ 0.010] 265.648905 s: SYSTEM: Attaching to [IPU1-0] ...
[0][ 1.010] 266.648478 s: SYSTEM: Attaching to [IPU1-0] ...
[0][ 2.010] 267.648478 s: SYSTEM: Attaching to [IPU1-0] ...
[0][ 3.010] 268.648508 s: SYSTEM: Attaching to [IPU1-0] ...
[0][ 4.010] 269.648539 s: SYSTEM: Attaching to [IPU1-0] ...
[0][ 5.010] 270.648569 s: SYSTEM: Attaching to [IPU1-0] ...
[0][ 6.010] 271.648600 s: SYSTEM: Attaching to [IPU1-0] ...
[0][ 7.010] 272.648630 s: SYSTEM: Attaching to [IPU1-0] ...
[0][ 8.010] 273.648661 s: SYSTEM: Attaching to [IPU1-0] ...
[0][ 9.010] 274.648691 s: SYSTEM: Attaching to [IPU1-0] ...
[0][ 9.743] 275.384462 s: SYSTEM: Attaching to [IPU1-0] ... SUCCESS !!!
[0][ 9.746] 275.387756 s: SYSTEM: Attaching to [DSP1] ... SUCCESS !!!
[0][ 9.747] 275.388031 s: SYSTEM: Notify register to [IPU1-0] line 0, event 15...
[0][ 9.747] 275.388427 s: SYSTEM: Notify register to [DSP1] line 0, event 15...
[0][ 9.747] 275.388732 s: SYSTEM: Notify init done !!!
[0][ 9.749] 275.390624 s: SYSTEM: MsgQ init done !!!
[0][ 9.749] 275.390868 s: SYSTEM: IPC init DONE !!!
[0][ 9.757] 275.398249 s: SYSTEM: System Common Init Done !!!
[0][ 9.757] 275.398554 s: SYSTEM: System Init in progress !!!
[0][ 9.757] 275.398767 s: SYSTEM: BSP Common Init in progress !!!
[0][ 9.758] 275.398981 s: SYSTEM: BSP Common Init Done !!!
[0][ 9.758] 275.399255 s: SYSTEM: BSP Platform Init in progress !!!
[0][ 9.758] 275.399530 s: SYSTEM: BSP Platform Init Done !!!
[0][ 9.758] 275.399743 s: SYSTEM: FVID2 Init in progress !!!
[0][ 9.759] 275.400048 s: SYSTEM: FVID2 Init Done !!!
[0][ 9.759] 275.400292 s: SYSTEM: VPS Init in progress !!!
[0][ 9.759] 275.400506 s: SYSTEM: VPDMA Descriptor Memory Address translation ENABLED [0x80000000 -> 0x80000000]
[0][ 9.760] [t=0x00077296] ti.sysbios.family.arm.m3.Hwi: ERROR: line 1104: E_hardFault: FORCED
[0][ 9.760] ti.sysbios.family.arm.m3.Hwi: line 1104: ti.sysbios.family.arm.m3.Hwi: line 1104: E_hardFault: FORCED
[0][ 9.760] [t=0x0007c225] ti.sysbios.family.arm.m3.Hwi: ERROR: line 1181: E_busFault: IMPRECISERR: Delayed Bus Fault, exact addr unknown, address: e000ed38
[0][ 9.760] ti.sysbios.family.arm.m3.Hwi: line 1181: ti.sysbios.family.arm.m3.Hwi: line 1181: E_busFault: IMPRECISERR: Delayed Bus Fault, exact addr unknown, address: e000ed38
[0][ 9.760] Exception occurred in background thread at PC = 0x9960ca2e.
[0][ 9.760] Core 0: Exception occurred in ThreadType_Task.
[0][ 9.760] Task name: System main, handle: 0x9c6662e0.
[0][ 9.760] Task stack base: 0x9c8657c0.
[0][ 9.760] Task stack size: 0x8000.
[0][ 9.760] R0 = 0xfc000000 R8 = 0xffffffff
[0][ 9.760] R1 = 0x4899584c R9 = 0xffffffff
[0][ 9.760] R2 = 0x00000001 R10 = 0xffffffff
[0][ 9.760] R3 = 0x9959dbac R11 = 0xffffffff
[0][ 9.760] R4 = 0xffffffff R12 = 0x9c86d630
[0][ 9.760] R5 = 0xffffffff SP(R13) = 0x9c86d5f0
[0][ 9.760] R6 = 0xffffffff LR(R14) = 0x9959daf7
[0][ 9.760] R7 = 0xffffffff PC(R15) = 0x9960ca2e
[0][ 9.760] PSR = 0x01000000
[0][ 9.760] ICSR = 0x00435803
[0][ 9.760] MMFSR = 0x00
[0][ 9.760] BFSR = 0x04
[0][ 9.760] UFSR = 0x0000
[0][ 9.760] HFSR = 0x40000000
[0][ 9.760] DFSR = 0x00000000
[0][ 9.760] MMAR = 0xe000ed34
[0][ 9.760] BFAR = 0xe000ed38
[0][ 9.760] AFSR = 0x00000000
[0][ 9.760] Unhandled Exception:
[0][ 9.760] Exception occurred in ThreadType_Taskhandle: 0x9c6662e0.
[0][ 9.760] stack base: 0x9c8657c0.
[0][ 9.760] R0 = 0xfc000000 R8 = 0xffffffff
[0][ 9.760] R1 = 0x4899584c R9 = 0xffffffff
[0][ 9.760] R2 = 0x00000001 R10 = 0xffffffff
[0][ 9.760] R3 = 0x9959dbac R11 = 0xffffffff
[0][ 9.760] R4 = 0xffffffff R12 = 0x9c86d630
[0][ 9.760] R5 = 0xffffffff SP(R13) = 0x9c86d5f0
[0][ 9.760] R6 = 0xffffffff LR(R14) = 0x9959daf7
[0][ 9.760] R7 = 0xffffffff PC(R15) = 0x9960ca2e
[0][ 9.760] PSR = 0x01000000
[0][ 9.760] ICSR = 0x00435803
[0][ 9.760] MMFSR = 0x00
[0][ 9.760] BFSR = 0x04
[0][ 9.760] UFSR = 0x0000
[0][ 9.760] HFSR = 0x40000000
[0][ 9.760] DFSR = 0x00000000
[0][ 9.760] MMAR = 0xe000ed34
[0][ 9.760] BFAR = 0xe000ed38
[0][ 9.760] AFSR = 0x00000000
[0][ 9.760] Terminating Execution...Terminating execution..

We need to solve this issue asap bcoz the early can is very important to be started in the rtos side .

Best Regards.

Ahmed

Hi Vivek,

the issue is  not yet solved  , we tried as u said  to change the macros   SYSTEM_DCAN_INTR_ID , we used some of the values listed in  platform/src/tda2xx/irq_xbar_interrupt_ids.h and still the same behavior  also the android startup makes crash and there are no display only the terminal . I can confirme that the issue isn't about the early can feature but its related to the core IPU1_0 because when i disbled the dcan juste compiled the ipu1-0 along side the rvc UC the problem is the same , SO please can u confirme this if you have jacinto evm with a prebuilt images , Also how to switch the DCAN  module to use IPU2 instead of IPU1 ?

Best regards

Ahmed .

Hello again , 

 I changed the  SYSTEM_DCAN_INTR_ID from 28 to 24 in the system_dcan.c because its  used to control the vip2  , i geuss ist fine with  the rtos vsdk but the android won't run and stopped at the 5 ms os the statup with this log :

[ 5.802434] init: [libfs_mgr]Running /system/bin/e2fsck on /dev/block/platform/44000000.ocp/480b4000.mmc/by-name/cache
[ 5.816441] random: e2fsck: uninitialized urandom read (40 bytes read, 25 bits of entropy available)
[ 5.846675] random: e2fsck: uninitialized urandom read (40 bytes read, 26 bits of entropy available)
[ 5.863944] e2fsck: e2fsck 1.43.3 (04-Sep-2016)
[ 5.863944]
[ 5.870025] e2fsck: cache: clean, 14/65536 files, 6228/65536 blocks
[ 5.870025]
[ 5.890137] EXT4-fs (mmcblk0p12): mounted filesystem with ordered data mode. Opts: (null)
[ 5.898362] ------------[ cut here ]------------
[ 5.898375] WARNING: CPU: 0 PID: 140 at drivers/bus/omap_l3_noc.c:147 l3_interrupt_handler+0x318/0x400()

it seems that i must set the gpio interrupter also in the kernel side or some where else ! plz any help for this ??

Best regards

Ahmed.

Hi

1) As per your previous post you said you have disabled DCAN, Have you done the proper  clean build?

2) If are facing the issue when DCAN is not included in the build, then please share the runtime logs as you shared in your original post.

3) Put a braekpoint in the function "BspOsal_registerIntr" & check the function call stack when the intNum = 28 and which all ips are using this interrupt no 28.

currently only VIP2 should be using when dcan is diabled.

Thanks

Gaviraju

Hello Gaviraju

i change the primary codeto ipu1_0 instead of ipu2 ,also i changed the SYSTEM_DCAN_INTR_ID to 61 . The starting and ending functions of the dcan {System_dcanInit() & System_dcanDeInit()} included into the file links_fw/src/rtos/links_ipu/system/system_ipu2.c so the dcan shoud works through the remote ipu2. after make clean and built the binaries  the dcan still not working and the log shows :

[0][ 0.000] 18 Resource entries at 0x99000000
[0][ 0.000] 0.554382 s: SYSTEM: System Common Init in progress !!!
[0][ 0.001] 0.555358 s: SYSTEM: IPC init in progress !!!
[0][ 0.002] 0.555633 s: SYSTEM: Attaching to [IPU1-0] ...
[0][ 0.004] 0.558195 s: SYSTEM: Attaching to [IPU1-0] ... SUCCESS !!!
[0][ 0.022] 0.575886 s: SYSTEM: Attaching to [DSP1] ... SUCCESS !!!
[0][ 0.022] 0.576160 s: SYSTEM: Notify register to [IPU1-0] line 0, event 15...
[0][ 0.023] 0.576526 s: SYSTEM: Notify register to [DSP1] line 0, event 15...
[0][ 0.023] 0.576892 s: SYSTEM: Notify init done !!!
[0][ 0.025] 0.578783 s: SYSTEM: MsgQ init done !!!
[0][ 0.025] 0.579027 s: SYSTEM: IPC init DONE !!!
[0][ 0.032] 0.586042 s: SYSTEM: System Common Init Done !!!
[0][ 0.032] 0.586286 s: SYSTEM: System IPU2 Init in progress !!!
[0][ 0.034] 0.588147 s: UTILS: DMA: HWI Create for INT25 !!!
[0][ 0.035] 0.588574 s: SYSTEM: SW Message Box Msg Pool, Free Msg Count = 1024
[0][ 0.035] 0.588940 s: SYSTEM: Heap = LOCAL_DDR @ 0x00000000, Total size = 262144 B (256 KB), Free size = 259240 B (253 KB)
[0][ 0.035] 0.589428 s: SYSTEM: Initializing Links !!!
[0][ 0.147] 0.701335 s: UTILS: PRF: ##### Cannot allocate Object for SYNC3 ####
[0][ 0.150] 0.704691 s: UTILS: PRF: ##### Cannot allocate Object for ALGORITHM0 ####
[0][ 0.154] 0.708137 s: UTILS: PRF: ##### Cannot allocate Object for ALGORITHM1 ####
[0][ 0.157] 0.711553 s: UTILS: PRF: ##### Cannot allocate Object for ALGORITHM2 ####
[0][ 0.161] 0.715061 s: UTILS: PRF: ##### Cannot allocate Object for ALGORITHM3 ####
[0][ 0.164] 0.718568 s: UTILS: PRF: ##### Cannot allocate Object for ALGORITHM4 ####
[0][ 0.168] 0.722137 s: UTILS: PRF: ##### Cannot allocate Object for ALGORITHM5 ####
[0][ 0.171] 0.725675 s: UTILS: PRF: ##### Cannot allocate Object for ALGORITHM6 ####
[0][ 0.175] 0.729305 s: UTILS: PRF: ##### Cannot allocate Object for ALGORITHM7 ####
[0][ 0.176] 0.729671 s: SYSTEM: Initializing Links ... DONE !!!
[0][ 0.176] 0.730006 s: UTILS: DCAN INTERRUPT: HWI Create for INT61 !!!
[0][ 0.177] 0.730830 s: UTILS: PRF: ##### Cannot allocate Object for DCANRX ####
[0][ 0.178] 0.731897 s: UTILS: PRF: ##### Cannot allocate Object for DCANTX ####
[0][ 0.178] 0.732233 s: Enable message object interrupt to route interrupt line 1 !!!
[0][ 0.179] 0.732538 s: ahmedDCANConfigIntrMux interrupt to route interrupt line 1 !!!
[0][ 0.179] 0.732843 s: ahmed System_dcanInit() in the IPU2 remote !!!
[0][ 0.179] 0.733087 s: SYSTEM: System IPU2 Init Done !!!
[0][ 0.787] 1.340785 s: SYSTEM: SW Message Box Msg Pool, Free Msg Count = 1023
[0][ 0.787] 1.341151 s: SYSTEM: Heap = LOCAL_DDR @ 0x00000000, Total size = 262144 B (256 KB), Free size = 256912 B (250 KB)
[0][ 10.177] [t=0x0c228067] ti.sysbios.family.arm.m3.Hwi: ERROR: line 1104: E_hardFault: FORCED
[0][ 10.177] ti.sysbios.family.arm.m3.Hwi: line 1104: ti.sysbios.family.arm.m3.Hwi: line 1104: E_hardFault: FORCED
[0][ 10.177] [t=0x0c22cde0] ti.sysbios.family.arm.m3.Hwi: ERROR: line 1181: E_busFault: PRECISERR: Immediate Bus Fault, exact addr known, address: 4ae3c100
[0][ 10.177] ti.sysbios.family.arm.m3.Hwi: line 1181: ti.sysbios.family.arm.m3.Hwi: line 1181: E_busFault: PRECISERR: Immediate Bus Fault, exact addr known, address: 4ae3c100
[0][ 10.177] Exception occurred in background thread at PC = 0x99038bdc.
[0][ 10.177] Core 0: Exception occurred in ThreadType_Task.
[0][ 10.177] Task name: DCAN Tx Task, handle: 0x99bc397c.
[0][ 10.177] Task stack base: 0x99d7e500.
[0][ 10.177] Task stack size: 0x800.
[0][ 10.177] R0 = 0x4ae3c100 R8 = 0xffffffff
[0][ 10.177] R1 = 0x00000001 R9 = 0xffffffff
[0][ 10.177] R2 = 0x99d85a34 R10 = 0xffffffff
[0][ 10.177] R3 = 0x00000007 R11 = 0xffffffff
[0][ 10.177] R4 = 0xffffffff R12 = 0xe00fffe0
[0][ 10.177] R5 = 0xffffffff SP(R13) = 0x99d7ec50
[0][ 10.177] R6 = 0xffffffff LR(R14) = 0x990361e9
[0][ 10.177] R7 = 0xffffffff PC(R15) = 0x99038bdc
[0][ 10.177] PSR = 0x01000000
[0][ 10.177] ICSR = 0x00435803
[0][ 10.177] MMFSR = 0x00
[0][ 10.177] BFSR = 0x82
[0][ 10.177] UFSR = 0x0000
[0][ 10.177] HFSR = 0x40000000
[0][ 10.177] DFSR = 0x00000000
[0][ 10.177] MMAR = 0x4ae3c100
[0][ 10.177] BFAR = 0x4ae3c100
[0][ 10.177] AFSR = 0x00000000
[0][ 10.177] Terminating execution...

Hello again 

i would like to get the document which descibes the same procedure for android like the link below :http://www.ti.com/lit/an/spracd1/spracd1.pdf .

Also where to find the u-boot linux described in that pdf for early can demo?

Regards 

Ahmed

Hi Ahmed,

I am not sure if such a document exists for your purpose. Let me check with a colleague once and will get back to you.

Thanks & Regards,
Vivek Dhande.

Texas Instruments (India) Pvt Ltd