Hugging Face's logo

Spaces:
ignitariumcloud
/
TI_RAG_Demo_L3.1
Runtime error

App Files Community
TI_RAG_Demo_L3.1
File size: 16,818 Bytes 
5aefcf4
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
 
Ticket Name: Linux/TDA2EVM5777: attaching to ipu1 ..... Cannot see any demo usecase.

Query Text:
Part Number: TDA2EVM5777 Tool/software: Linux Hi, I have successfully build and put the image on the sd card. I can get into the root and when I tried to run app.out it keeps on running attaching to ipu1 and other processing units without showing any particular display of the demo usecases. Can anyone help me figure this thing out? 6786.apps_out.txt root@dra7xx-evm:/opt/vision_sdk# source ./vision_sdk_load.sh
insmod: ERROR: could not insert module ./bin/memcache.ko: File exists
insmod: ERROR: could not load module ./bin/cmemk.ko: No such file or directory
mknod: /dev/memcache: File exists
./disableDssInterruptsOnA15.sh: line 11: COMMANDS: command not found
./disableDssInterruptsOnA15.sh: line 12: COMMANDS: command not found
./disableDssInterruptsOnA15.sh: line 13: COMMANDS: command not found
./disableDssInterruptsOnA15.sh: line 14: COMMANDS: command not found
./disableDssInterruptsOnA15.sh: line 15: COMMANDS: command not found
./disableDssInterruptsOnA15.sh: line 16: COMMANDS: command not found
./disableDssInterruptsOnA15.sh: line 17: COMMANDS: command not found
./disableDssInterruptsOnA15.sh: line 18: COMMANDS: command not found
./disableDssInterruptsOnA15.sh: line 19: COMMANDS: command not found
updated  value is


COMMANDS

        ### WARNING ###: use the following [read | write | set bit | clear bit | dump] commands at your own risk!
        No address check done, may generate:
          - bus error (invalid or not accessible <physical address>,
          - platform crash/hang (bad <value>).

            Read any OMAP memory address (register), given its <physical address> or <name> as listed in TRM.

            Write <value> at any OMAP memory address (register), given its <physical address> or <name> as listed in TRM.

            Set bit at <position> into any OMAP memory address (register), given its <physical address> or <name> as listed in TRM.

            Clear bit at <position> into any OMAP memory address (register), given its <physical address> or <name> as listed in TRM.

            Dump a range of OMAP memory addresses, from <start address> to <end address>.
            Note all addresses within given range must be valid and accessible.

        ### WARNING ###: use the following I2C [read | write] commands at your own risk!
        No address check done, may generate:
          - I2C bus error (invalid or not accessible <physical address>,
          - platform crash/hang (bad <value>).

            Read I2C register at address <addr> from I2C chip at <chip-addr> on I2C <bus>.

            Write <value> in I2C register at address <addr> from I2C chip at <chip-addr> on I2C <bus>.
root@dra7xx-evm:/opt/vision_sdk# ./apps.out
 [HOST]  OSA: MEM: 0: Mapped 0xa0100000 to 0xb697f000 of size 0x00100000
 [HOST]  OSA: MEM: 1: Mapped 0x84203000 to 0xa3d7f000 of size 0x12c00000
 [HOST]  OSA: MEM: 2: Mapped 0xa0200000 to 0xa3cbf000 of size 0x00040000
 [HOST]  OSA: MEM: 3: Mapped 0xa02c0000 to 0xa3cff000 of size 0x00080000
 [HOST]  OSA: MEM: 4: Mapped 0x00000000 to 0x00000000 of size 0x00000000
 [HOST]  OSA: IPU1-0 Remote Log Shared Memory @ 0xa0200000
 [HOST]  OSA: HOST Remote Log Shared Memory @ 0xa024f140
 [HOST]  OSA: DSP1 Remote Log Shared Memory @ 0xa02769e0
 [HOST]  OSA: DSP2 Remote Log Shared Memory @ 0xa029e280
 [HOST]  OSA: EVE1 Remote Log Shared Memory @ 0xa02c5b20
 [HOST]  OSA: EVE2 Remote Log Shared Memory @ 0xa02ed3c0
 [HOST]  OSA: EVE3 Remote Log Shared Memory @ 0xa0314c60
 [HOST]  OSA: EVE4 Remote Log Shared Memory @ 0xa033c500
 [HOST]  OSA: IPU2 Remote Log Shared Memory @ 0xa0363da0
 [HOST] [IPU1-0]   1957.479259 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [IPU1-0]   1958.479289 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [IPU1-0]   1959.479320 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [IPU1-0]   1960.479350 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [IPU1-0]   1961.479381 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [IPU1-0]   1962.479411 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [IPU1-0]   1963.479442 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [IPU1-0]   1964.479442 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [HOST  ]   1964.546391 s:  SYSTEM: System A15 Init in progress !!!
 [HOST] [DSP1  ]   1957.570853 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]   1958.570883 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]   1959.570914 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]   1960.570944 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]   1961.570975 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]   1962.571005 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]   1963.571036 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]   1956.710852 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]   1957.710882 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]   1958.710882 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]   1959.710913 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]   1960.710943 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]   1961.710974 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]   1962.711004 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]   1963.711035 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]   1964.571066 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]   1964.711065 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [IPU1-0]   1965.479472 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]   1965.571066 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]   1965.711096 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [IPU1-0]   1966.479503 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]   1966.571097 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]   1966.711096 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [IPU1-0]   1967.479533 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]   1967.571127 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]   1967.711126 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [IPU1-0]   1968.479564 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]   1968.571158 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]   1968.711157 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [IPU1-0]   1969.479594 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]   1969.571188 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]   1969.711187 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [IPU1-0]   1970.479625 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]   1970.571219 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]   1970.711218 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [IPU1-0]   1971.479655 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]   1971.571249 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]   1971.711248 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [IPU1-0]   1972.479686 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]   1972.571280 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]   1972.711279 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [IPU1-0]   1973.479686 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]   1973.571280 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]   1973.711309 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [IPU1-0]   1974.479716 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]   1974.571310 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]   1974.711340 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [IPU1-0]   1975.479747 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]   1975.571341 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]   1975.711340 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [IPU1-0]   1976.479777 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]   1976.571371 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]   1976.711370 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [IPU1-0]   1977.479808 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]   1977.571402 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]   1977.711401 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [IPU1-0]   1978.479838 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]   1978.571432 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]   1978.711431 s:  SYSTEM: Attaching to [IPU2] ...

Responses:
Hi, For linux we use IPU2 core and IPU1 is disabled. How are you getting IPU1 core log when it is disabled? Have you made any changes? Regards, Anuj

Hi Anuj, I was trying to run the tidl usecase on linux as it is not available by default so I had to make some changes in the configuration file to run it. This is the reason I changed it. My core purpose is to build the tidl on the linux system rather than BIOS. Can you tell me how can I achieve it without facing these problems. Thank you. With best regards, H.M. Owais

3386.apps_out.txt root@dra7xx-evm:/opt/vision_sdk# ./vision_sdk_load.sh
insmod: ERROR: could not insert module ./bin/memcache.ko: File exists
insmod: ERROR: could not load module ./bin/cmemk.ko: No such file or directory
mknod: /dev/memcache: File exists
./disableDssInterruptsOnA15.sh: line 11: COMMANDS: command not found
./disableDssInterruptsOnA15.sh: line 12: COMMANDS: command not found
./disableDssInterruptsOnA15.sh: line 13: COMMANDS: command not found
./disableDssInterruptsOnA15.sh: line 14: COMMANDS: command not found
./disableDssInterruptsOnA15.sh: line 15: COMMANDS: command not found
./disableDssInterruptsOnA15.sh: line 16: COMMANDS: command not found
./disableDssInterruptsOnA15.sh: line 17: COMMANDS: command not found
./disableDssInterruptsOnA15.sh: line 18: COMMANDS: command not found
./disableDssInterruptsOnA15.sh: line 19: COMMANDS: command not found
updated  value is


COMMANDS

        ### WARNING ###: use the following [read | write | set bit | clear bit | dump] commands at your own risk!
        No address check done, may generate:
          - bus error (invalid or not accessible <physical address>,
          - platform crash/hang (bad <value>).

            Read any OMAP memory address (register), given its <physical address> or <name> as listed in TRM.

            Write <value> at any OMAP memory address (register), given its <physical address> or <name> as listed in TRM.

            Set bit at <position> into any OMAP memory address (register), given its <physical address> or <name> as listed in TRM.

            Clear bit at <position> into any OMAP memory address (register), given its <physical address> or <name> as listed in TRM.

            Dump a range of OMAP memory addresses, from <start address> to <end address>.
            Note all addresses within given range must be valid and accessible.

        ### WARNING ###: use the following I2C [read | write] commands at your own risk!
        No address check done, may generate:
          - I2C bus error (invalid or not accessible <physical address>,
          - platform crash/hang (bad <value>).

            Read I2C register at address <addr> from I2C chip at <chip-addr> on I2C <bus>.

            Write <value> in I2C register at address <addr> from I2C chip at <chip-addr> on I2C <bus>.
root@dra7xx-evm:/opt/vision_sdk# ./apps.out
 [HOST]  OSA: MEM: 0: Mapped 0xa0100000 to 0xb69d0000 of size 0x00100000
 [HOST]  OSA: MEM: 1: Mapped 0x84203000 to 0xa3dd0000 of size 0x12c00000
 [HOST]  OSA: MEM: 2: Mapped 0xa0200000 to 0xa3d10000 of size 0x00040000
 [HOST]  OSA: MEM: 3: Mapped 0xa02c0000 to 0xa3d50000 of size 0x00080000
 [HOST]  OSA: MEM: 4: Mapped 0x00000000 to 0x00000000 of size 0x00000000
 [HOST]  OSA: HOST Remote Log Shared Memory @ 0xa024f140
 [HOST]  OSA: DSP1 Remote Log Shared Memory @ 0xa02769e0
 [HOST]  OSA: DSP2 Remote Log Shared Memory @ 0xa029e280
 [HOST]  OSA: EVE1 Remote Log Shared Memory @ 0xa02c5b20
 [HOST]  OSA: EVE2 Remote Log Shared Memory @ 0xa02ed3c0
 [HOST]  OSA: EVE3 Remote Log Shared Memory @ 0xa0314c60
 [HOST]  OSA: EVE4 Remote Log Shared Memory @ 0xa033c500
 [HOST]  OSA: IPU2 Remote Log Shared Memory @ 0xa0363da0
 [HOST] [HOST  ]    180.225035 s:  SYSTEM: System A15 Init in progress !!!
 [HOST] [DSP1  ]    162.056945 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    163.056975 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    164.056975 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    165.057006 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    166.057036 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    167.057067 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    168.057097 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    169.057128 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    170.057158 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    171.057189 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    172.057219 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    173.057219 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    174.057250 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    175.057280 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    176.057311 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    177.057341 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    178.057372 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    179.057402 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    180.057433 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    162.158939 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    163.158970 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    164.159000 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    165.159031 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    166.159061 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    167.159061 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    168.159092 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    169.159122 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    170.159153 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    171.159183 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    172.159214 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    173.159244 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    174.159275 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    175.159275 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    176.159305 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    177.159336 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    178.159366 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    179.159397 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    180.159427 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    181.057463 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    181.159458 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    182.057463 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    182.159488 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    183.057494 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    183.159488 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    184.057524 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    184.159519 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    185.057555 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    185.159549 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    186.057585 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    186.159580 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    187.057616 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    187.159610 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    188.057646 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    188.159641 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    189.057677 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    189.159671 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    190.057677 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    190.159702 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    191.057707 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    191.159732 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP1  ]    192.057738 s:  SYSTEM: Attaching to [IPU2] ...
 [HOST] [DSP2  ]    192.159732 s:  SYSTEM: Attaching to [IPU2] ...

 Hi Anuj, I have changed it to no in the configuration file, the error is still there. with IPU2

Hi, Can you revert your all changes and check with IPU2 are you able to boot of not? TIDL OD usecase is not supported on linux as of now. So in that perspective it will be difficult to help you in integrating TIDl with linux. But please search in E2E forum as few customers has already tried this. So you may get help from those threads. Regards, Anuj

Hi, I haven't heard back from you, I'm assuming you were able to resolve your issue. If not, just post a reply below (or create a new thread if the thread has locked due to time-out). Regards, Anuj