loadide.sh line94:command not found

#1

i get the error:"loadide.sh line94:command not found "when i use the “open at ide command line”,how to resolve the problem?
i didn’t setup the cygwin before.i need setup it ?

0 Likes

#2
  1. What version of the OpenAT SDK are you using?
  2. Open loadide.sh (search your hard drive if you don’t know where it is) and look at line 94. What’s the command that’s failing?
0 Likes

#3

hi,my ide version is 1.08.02,and line 94 is :
export WM_OAT_IDE=$(cd $WM_OAT_IDE; cmd /c cd | $WM_OAT_IDE_CYGWIN/bin/sed -s “s|\\|/|g”)

0 Likes

#4

Well, it looks like it’s trying to use cmd to change directories (although it doesn’t use cmd eariler in the same line…). Anyway, do you have c:\Windows\system32\ in your path? Does C:\Windows\system32\cmd.exe exist? (If not, what OS are you using?)

I don’t know Cygwin well enough to know why the Cygwin environment can’t find it. You may have to uninstall and reinstall the SDK (I think I’ve read that that worked for some people).

0 Likes

#5

Thanks a lot ,adding “c:\Windows\system32” to the path is useful! :laughing: Thank you!

0 Likes

#6

:open_mouth: I didn’t think it would be that easy! I’ve never seen a Windows PC that didn’t have system32 in the path by default…

0 Likes

#7

But I have two computers.None of them have the system32 path.I didn’t know why.
And thanks a lot. :laughing:

0 Likes

#8

And when I test with the ‘helloworld’ example,There is another problem:
I can’t see the debug information as it in the tutorial.But the message below instead:

Trace		1	Unable to find the string of the remote trace in the file (ID = 12654)
Trace		1	Unable to find the string of the remote trace in the file (ID = 12654)
Trace		1	Unable to find the string of the remote trace in the file (ID = 12654)
Trace		1	Unable to find the string of the remote trace in the file (ID = 12654)
Trace		1	Unable to find the string of the remote trace in the file (ID = 12654)
Trace		1	Binary header at 100141D8
Trace	L3RR	1	Unable to find the string of the remote trace in the file (ID = 3771)

Or,what does that mean? :open_mouth:

I changed a module ,and another message:

Trace	L3RR	1	Unable to find the string of the remote trace in the file (ID = 1060442)
Trace		1	Unable to find the string of the remote trace in the file (ID = 1072551)
Trace		1	Unable to find the string of the remote trace in the file (ID = 1072551)
Trace		1	Unable to find the string of the remote trace in the file (ID = 1072551)
Trace		1	Unable to find the string of the remote trace in the file (ID = 1072551)
Trace		1	Unable to find the string of the remote trace in the file (ID = 1072551)
Trace		1	Binary header at 100141D8
Trace	L3RR	1	Unable to find the string of the remote trace in the file (ID = 1060442)

My module is Q24PL002.

0 Likes

#9

You need to read section 6.1.3.4 of TM_Tools_Manual_for_Open_AT.pdf (search your OpenAT directory). In short, you need to look in a subdirectory of your project for a *.wks.

0 Likes

#10

Hi,I did it.The message changed:

Trace	DEV	1	Unable to find the string of the remote trace in the file (ID = 1072551)
Trace	DEV	1	Unable to find the string of the remote trace in the file (ID = 1072551)
Trace	DEV	1	Unable to find the string of the remote trace in the file (ID = 1072551)
Trace	DEV	1	Unable to find the string of the remote trace in the file (ID = 1072551)
Trace	DEV	1	Unable to find the string of the remote trace in the file (ID = 1072551)
Trace	CUS4	1	Embedded Application : Main
Trace	CUS3	1	Binary header at 1000E150
Trace	IOB	1	Unable to find the string of the remote trace in the file (ID = 1065628)
Trace	L3RR	1	Unable to find the string of the remote trace in the file (ID = 1060442)

and I don’t know if the “Command->Set and Request to the target” need to be set.
I select CUS4 and Bitmap1 in the “Command->Set and Request to the target” ,
and select ADL(just one choose) and Trace level1 in the" RemoteTasks Monitor".
And my Baudrate is 115200 .
What leads my problem?
And another appearance:when I click the “start” button of " RemoteTasks Monitor",the target seems to have a reset… :confused:

0 Likes

#11

I know that some trace messages are for internal use at Wavecom and not publicly documented. I Since I never use TMT, I’ve exceeded my knowledge on the subject and can’t help anymore.

0 Likes

#12

Hi,Thanks
I’ll get in touch with my distributor.
Thanks again for your patient help.

0 Likes

#13

the only trace messages you need tot pay attention to are the cus4 or adl messages
the other messages are just internal wavecom debug chatter. as Matt Otto said, they are undocumented.

0 Likes

#14

Thanks,Madouc,I’ll pay attention to it .

0 Likes