Open Port from Developer Studio -> ERROR Bootloader Mode

IoT Modules Development tools
1

Hi,

in case of open port in the Target Management perspective I receive an error message that “Bootloader Mode” is active:

1007×603 94.5 KB

This is the text in the detail dialog box:

Open and load local port ttyS0 => ERROR: Connected module seems to be blocked in bootloader mode
Open and load physical port ttyS0 => ERROR: Connected module seems to be blocked in bootloader mode
Open port ttyS0 => DONE: Port opened
Open port ttyS0 => DONE: Port opened
Load informations from target => ERROR: Connected module seems to be blocked in bootloader mode
Waiting for module detection => DONE: Target detected sn:null baudrate:115200
Switch to Development mode and check => ERROR: Connected module seems to be blocked in bootloader mode
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
Try to unlock developement mode and check => ERROR: Connected module seems to be blocked in bootloader mode
Waiting for module detection => NO NEED TO DO IT: Success
Check if the target is stuck in bootloader mode => ERROR: Connected module seems to be blocked in bootloader mode

Here is what I see on the AT command interface:

----------------- Port opened -----------------
AT

OK
AT+WMSN

ERROR
AT+CFUN=1

OK
AT

OK
AT+WMSN

ERROR

atat

OK

atat

OK

atat

OK

!RSSI: 94

!RSSI: 88

!RSSI: 94

I have updated my Developer Studio to the latest version 3.2
My EvalBoard is AR7554 and these are the Firmware version infos.

What does this mean?

Br,
Martin…

2

The Target Management perspective of DS is designed to work with Open AT enabled devices, which is not the case for AR7.
You should uninstall the Open AT IDE feature and install the Legato IDE feature instead.
Then, you’ll be able to connect (through IP) to your device thanks to the Remote System Explorer perspective.

3

Hi daav,

I wasn’t aware about the limitation that Open AT isn’t enabled on AR7(554). All PDF documentation including getting started and so on describes to get a helloWorld running, there is no hint that AR7 doesn’t work.

Anyway many thanks for your quick reply.
I removed the Open AT integration and libs etc. completely from Developer Studio, afterwards I used the “Remote System Explorer” perspective as you mentioned in your answer.
As you can see I can now access my remote AR7 system via SSH/SCP and can browse through the remote file system:

2225749a3d6f439229c0a153783f433a8bf9c3a5.png408×902 48 KB

Best regards,
Martin…