HAPC AT test error

nsharrok · November 30, 2012, 4:12am

Hi,
Pardon me but I am a noob. I suspect I will look back at this and chringe but I will be bauld because I have pull all my hair out

I followed the “hello world” tutorial (many times).
When I run any configuration I get an alert stating “ERROR: An error ocurred during HAPC AT test”

I get this error whenever I attempt to connect to the modem via Developer Studio.
I can connect via Discovery Tool and communicate with the modem OK.

I suspect that is something missing in the setup but I don’t know what.
The tutorial mentions [RTL]_MinGW_Debug but I don’t have that listed in my configurations.
I found a reference to HAPC indicating that it is involved in tracing but that all I could find out.

The details are
Open and load port COM10 => ERROR: An error ocurred during HAPC AT test
Open and load physical port COM10 => ERROR: An error ocurred during HAPC AT test
Open port COM10 => DONE: Success
Wait for USB port to reconnect => NO NEED TO DO IT: Success
Open port COM10 => DONE: Port opened
Pause : 1000 milliseconds => NO NEED TO DO IT: Success
Load informations from target => ERROR: An error ocurred during HAPC AT test
Waiting for module detection => DONE: Target detected sn:null baudrate:null
Switch to Development mode and check => ERROR: An error ocurred during HAPC AT test
Switch to Development mode => DONE: Success
Pause : 300 milliseconds => DONE: Success
Check dev mode unlocked => ERROR: An error ocurred during HAPC AT test
Switch to Development mode and check => ERROR: An error ocurred during HAPC AT test
Switch to Development mode => DONE: Success
Pause : 300 milliseconds => DONE: Success
Check dev mode unlocked => ERROR: An error ocurred during HAPC AT test
Switch to Development mode and check => ERROR: An error ocurred during HAPC AT test
Switch to Development mode => DONE: Success
Pause : 300 milliseconds => DONE: Success
Check dev mode unlocked => ERROR: An error ocurred during HAPC AT test

Used packages versions:

Open AT Framework package (2.51.0.201206190958)
Open AT OS Package (6.51.0.201206010944)
Firmware Package (7.51.0.201205311751)

Thanks
Noel Sharrock

Rex_alex · November 30, 2012, 6:50am

Hi,

Can you please try using the sample application with lower firmware version(like 7.46 or 7.47)?
Try to run the app on UART port(COM1) and check if same error is coming or not.

Also try to follow these things :
-reset the module

stop and erase Open AT application and objects
power-cycle the module.

Thanks.

daav · November 30, 2012, 9:25am

FW 7.51 has a known restriction, which can be workarounded by installing the patch proposed here: https://forum.sierrawireless.com/t/patch-for-developer-studio-2-2-1/5739/1
This should fix your connection issues.

nsharrok · December 6, 2012, 6:55pm

Hi Rex_alex and daav,
I tried all of your suggestions and got the same error each time.
Execpept for COM1 which I got A time out.
I reinstalled the Drivers and COM1 worked. Still got the same error with the USB port though.
Thank you for your suggestions.

I get a new error now when running the Hello_World app
Load model element: Target Informations => ERROR: Timeout while handling command: class com.swi.tm.hlservices.target.internal.bundle.AtWopenLevelCallback

daav · December 7, 2012, 6:53am

2 things to check:

can you verify that the patch is correctly installed? Can you paste here a screen capture of the Help > About > Installation Details box?
take care that trying to connect to the same target with 2 ports can be problematic, since only one can be switched in Development Mode at a time. To be able to use another port in Development Mode, you should send the AT+WDM=0 command + reset before trying to open the connection again.

nsharrok · December 7, 2012, 7:27pm

Hi Daav,
Good news.
I reinstalled Developer Studio which wiped out the patch. Patch is now installed…updated the firmware on the module…
Got Hello World to run

Now for real work. I’m sure I’ll be back here though
Thanks again

nsharrok · December 15, 2012, 8:09pm

The HAPC AT test error is back to haunt me again.
I did a fresh install of Developer Studio and attempted to apply the plugin tm131Patch

I got the following when trying to install new software
“The operation cannot be completed. See the details.
Patch for Target Manager 1.3.1.201207181400-R9827
Detils: “Patch for Target Manager” is not applicable to the current configuration and will not be installed.”

My current firmware package is Open AT ® Firmware 7.51.0.201205311751

What does " the current configuration " referred to in the details mean.
How do I fix this?

daav · December 17, 2012, 8:11am

Since the last post, DS 2.3.0 has been released.
please refer to this post: https://forum.sierrawireless.com/t/developer-studio-2-3-0-released/5995/1

The good news: you don’t need to install any additional patch (the patch was made for DS 2.2.1, that’s why it is declared not compatible with DS 2.3.0).
But you still need to modify the preferences to workaround the 7.51 / 7.47.4 bad behavior (explained in the post linked above)

nsharrok · December 17, 2012, 6:27pm

Preferences > Developer Studio > Target Management > Send AT commands requests in development mode.
I unchecked this and now I get time out error.

685×735 103 KB

Discovery Tool has no problem connecting to module via this com port.

daav · December 18, 2012, 6:21am

Looks like your device answers to AT commands in production mode (can you confirm by giving a try in the console?)
If DS can’t switch it to dev mode, it may because the device is locked in dev mode on another port.
Please send AT+WDM=0;+CFUN=1 and try again to refresh the status view.

nsharrok · December 18, 2012, 7:06pm

Hi daav,
Thanks for your prompt response.
I applied the "AT+WDM=0;+CFUN=1’ commands, refreshed the status view. looks better.

Recompiled mms demo OK and started run in debug mode. dwl uploaded. eventually got an error

I save the complete error text should you need it

daav · December 19, 2012, 7:45am

Does your application perform some kind of heavy processing at its beginning?
Can you verify if this kind of timeout occurs only when the application is just downloaded again, or just started?
Another test would be to try with another app (an “empty” one, or just the Hello World) and check if you reproduce the same kind of issue or not (the idea is to check if the issue is related to your application, or something else).

nsharrok · December 20, 2012, 7:53pm

Hi daav,
The timeout error happens just after the app has started.
Same with unmodified Hello_World demo.
If I attempt to stop the app I get a time out error and tha app continues to run.

Here is a twist, This morning the device would not open, again, on USB COM7 unless the serial cable was plugged in as well.
Things realy got wierd, as above and with WMSN errors on opening COM7, untill I removed the serial cable.
Now I can open and close the port and start & stop the hello_world and MMS apps.

Glee! I got a trace reaction when I entered AT+GPRS=“mms”,“411”,“optus” into the MMS app
ADL;2;-24 <- wip_bearerStart()
although the TMConsole did not respond and still has Initialising …

I added some trace lines to the MMS app to see how far it gets untill it stops. It uploaded with the same time out error after the app started.
and now I can’t interact with the app at all. Back to same state as this morning…

daav · December 21, 2012, 8:24am

When you get the timeout error, please can you make some tests:

try to send AT commands in the TMConsole: are they answering?
if not, try to hardware reset the target (do not close the port)
try again to send commands: are they answering?
if not, try to close & reopen the port in DS
try again to send commands: are they answering?
Please post the feedback, to help us trying to diagnose the issue…

nsharrok · December 26, 2012, 8:49pm

Seasons Greetings daav,
Back from a few days away with friends.
Turned on the computer, checked FXT009 connections and LED. Look OK. Opened Discovery Tool,
Com Port: COM7 - USB Modem
Discovery Tool can Open Con Port 7 but is unable to communicate with device.
Disconnect. Plug in serial cable. Connect OK. Disconnect.
Open Developer Studio - Target Management - select COM1 - Open Port

TMConsole(COM1)

----------------- Port opened -----------------
AT+WMSN

Serial Number BH2420075708100

OK
at

OK
Device not responding to AT Commands.
Reset Device (Power off, wait 15 secs, power on, wait for LED to blink intermittently )
TMConsole(COM1)
+WIND: 3

+WIND: 1

+WIND: 7

+WIND: 4

Initializing …
Initializing … is sent from MMS demo which is supplied as Sample - WIP-MMS demo with Internet Library
Device is answering AT commands
ati9

“DWL”,“V09c08”,"",“Sierra Wireless”,55684,“053112 09:27”,“6baf6254”,“00010000”
“FW”,“FW_751_14.Q2687RDG”,“R7.51.0.201205311751.FXT009”,“Sierra Wireless”,620780,“053112 17:51”,“de5225b8”,“001c0000”
“MODEM”,“1.2.12”,“201205311748.FXT009”,“Sierra Wireless”,1660692,“053112 17:48”,“16b6cdaa”,“00020000”
“OAT”,“1.0.0.20121221063516”,“MMS [Internet Library Package (5.54.0.201206011257)] Sample”,“MyCompany”,146448,“122112 06:35”,“7126cb53”,“002a0000”
-“Developer Studio”,“2.3.0.201212051546-R10684”
-“Open AT Framework package”,“2.51.0.201206190958”
-“Open AT OS Package”,“6.51.0.201206010944”
-“Firmware Package”,“7.51.0.201205311751”
-“Internet Library Package”,“5.54.0.201206011257”
“ROM”,“800000”
“RAM”,“200000”
“DWLNAME”,“FXT009”

OK
Compile and run MMS demo.
Compiled: OK. Run: Time out Error --> Switch to Development mode and check => ERROR: Time out: 1000ms (before uploading code)

Switch to COM7
Open port. OK Status normal, 1 error reported
TMConsole(COM7)
----------------- Port opened -----------------

+WIND: 3

+WIND: 1

+WIND: 7

+WIND: 4

Initialising …

Serial Number BH2420075708100

OK

+WIMEI: 353270041031826

OK

+WDM: 3

OK

+WOPEN: (0-9),(256-4608),(0-24),(0-24)

OK

+WOPEN: 6,1024,3840

OK

+WOPEN: 9,0,3840

OK

+WOPEN: 1

OK

ERROR

+WUSB: 1,“114F”,“SIERRA WIRELESS”,“BH2420075708100”
+WUSB: 2,0,“1000”,“USB SERIAL PORT”,192,20
+WUSB: 3,“UFLCDC”
+WUSB: 4,0

OK

“DWL”,“V09c08”,"",“Sierra Wireless”,55684,“053112 09:27”,“6baf6254”,“00010000”
“FW”,“FW_751_14.Q2687RDG”,“R7.51.0.201205311751.FXT009”,“Sierra Wireless”,620780,“053112 17:51”,“de5225b8”,“001c0000”
“MODEM”,“1.2.12”,“201205311748.FXT009”,“Sierra Wireless”,1660692,“053112 17:48”,“16b6cdaa”,“00020000”
“OAT”,“1.0.0.20121221063516”,“MMS [Internet Library Package (5.54.0.201206011257)] Sample”,“MyCompany”,146448,“122112 06:35”,“7126cb53”,“002a0000”
-“Developer Studio”,“2.3.0.201212051546-R10684”
-“Open AT Framework package”,“2.51.0.201206190958”
-“Open AT OS Package”,“6.51.0.201206010944”
-“Firmware Package”,“7.51.0.201205311751”
-“Internet Library Package”,“5.54.0.201206011257”
“ROM”,“800000”
“RAM”,“200000”
“DWLNAME”,“FXT009”

OK

+WMFM: 0,2,1,1
+WMFM: 0,2,2,0
+WMFM: 0,2,3,1
+WMFM: 1,2,4,0
+WMFM: 1,2,4,1

OK
Compile and run MMS demo.
Compiled: OK. Run: Time out Error --> Switch to Development mode and check => ERROR: Time out: 1000ms (after uploading code)
TMConsole(COM7)
OK

OK

Serial Number BH2420075708100

OK

+WIND: 1

+WIND: 7

+WIND: 4

Initialising …

Device is not responding to AT commands

Traces
2012/12/27;07:15:51:229;001;ADL;1;Binary header at 002A0000
2012/12/27;07:15:51:231;001;ADL;4;Embedded Application : Main
2012/12/27;07:15:51:231;002;ADL;4;(CfgGprs) Enter.
2012/12/27;07:15:55:269;001;ADL;4;(cbEvhSim) Enter.
2012/12/27;07:15:55:797;001;ADL;4;(cbEvhSim) Enter.
2012/12/27;07:16:06:851;001;ADL;4;(cbEvhSim) Enter.
2012/12/27;07:16:06:852;001;ADL;4;(cbPollCreg) Enter.
2012/12/27;07:16:06:853;001;ADL;4;(cbPollCreg) Registered on GPRS network.
2012/12/27;07:16:11:192;001;ADL;4;appli_entry_point| InitType : 0

Noel

nsharrok · January 6, 2013, 7:30pm

Hi Daav,

[i]When you get the timeout error, please can you make some tests:

try to send AT commands in the TMConsole: are they answering?[/i] No
* if not, try to hardware reset the target (do not close the port) Cycled power
* try again to send commands: are they answering? Yes
[i]* if not, try to close & reopen the port in DS
try again to send commands: are they answering?[/i]

Detailed answer in previous post

daav · January 8, 2013, 8:59am

If the starget starts again to answer to AT commands after it has been reset, it looks clearly like the AT commands frozen bug which is supposed to be fixed by the Developer Studio > Target Management > Send AT commands in development mode preference.
Please can you verify the preference is unchecked?

nsharrok · January 8, 2013, 7:57pm

Please can you verify the preference is unchecked? Yes it was unchecked

daav · January 9, 2013, 7:54am

Mmmm, sounds like even the preference tip is sometimes not sufficient to workaround the firmware issue.
Could you make another test?
–> Once connected to your device, try to refresh the target status view several times (let’s say 10 times…)
Give a try with the preference checked: after some tries you should fall in timeout, and need to reset the device to be able to refresh the status again.
Give a try with the preference unchecked: and please tell if it is OK or not…

nsharrok · January 9, 2013, 8:40pm

Give a try with the preference checked: Refreshed successfully four times then the HAPC AT test error occurred on fifth attempt
Give a try with the preference unchecked: Failed first time with a timeout error

Details:
Reload model for port COM7 => ERROR: Time out: 20000ms
Load informations from target => ERROR: Time out: 20000ms

Topic		Replies	Views
SL8090 and Target Management Development tools	2	1185	November 29, 2012
Open Port from Developer Studio -> ERROR Bootloader Mode Development tools	2	1555	November 19, 2014
SL6087 problem with Target Management Development tools	8	4285	December 5, 2012
COM PORT TIME OUT ERROR Development tools	2	1497	May 21, 2012
ATI9 error Development tools	4	2248	February 24, 2014

HAPC AT test error

Related topics