Problem during dwl download

[candelo]

hi everybody

I had a problem during the download of a .dwl. I was downloading the file through xmodem (hyperterminal) and, during the download, one of the boards I was using between the computer and the modem failed. now, the modem doesn’t responds AT comands from hyperterminal. it is kind of blocked. how can reset o make the modem start responding again???

I also tried to download de firmware using DwlWin (and the boot pin), but, after the software finished the download (the progress bar finished), it throws a ‘fatal timeout error’… I don’t know why

thx for any comments and solutions

[davidc]

Hiya,

Try re-flashing the firmware using DWLWin - make sure you check the erase ‘Objects’, ‘Customization Files’ and ‘OpenAT application’ boxes. This should put the module back to factory.

Also, make sure that you are using the right firmware for your development environment.

ciao, Dave

[diste]

hi,
I have a similar problem, the fastrack supreme not answer to at commands anymore, and dwlwin says:
Starting up the target (attempt #1)
…
Starting up the target (attempt #12)
…
Boot failure: cannot connect with the target
Cannot boot up the remote target: giving up

there is another way to reset the modem (hard reset?)

thanks

[diste]

Found a solution:

1. written a small program in C that writes countinously on serial port “AT+WOPEN=0”
2. started the program with wavecom connected to serial port without power
3. plugged the power to wavecom

at command is received before the openat application is started

[awneil]

@diste

at command is received before the openat application is started

This is why it’s a good idea to put a delay at the start of your application - to give time to send an AT+WOPEN=0 if necessary!

[awneil]

@diste

at command is received before the openat application is started

This is why it’s a good idea to put a delay at the start of your application - to give time to send an AT+WOPEN=0 if necessary!

eg, see: viewtopic.php?f=30&t=3227&p=12032&hilit=delay+startup#p12032

[davidc]

Hiya,

@diste

hi,
I have a similar problem, the fastrack supreme not answer to at commands anymore, and dwlwin says:
Starting up the target (attempt #1)
…
Starting up the target (attempt #12)
…
Boot failure: cannot connect with the target
Cannot boot up the remote target: giving up

there is another way to reset the modem (hard reset?)

Did you pull the boot pin (on the Fastrack Supreme HD 15 connector) to ground when trying to connect using DWLWin?

See this post for notes on making making the appropriate cable and using DWLWin …

ciao, Dave

[diste]

@davidc

Did you pull the boot pin (on the Fastrack Supreme HD 15 connector) to ground when trying to connect using DWLWin?

thanks dave, I read your post, I spare that as last chance

@awneil

This is why it’s a good idea to put a delay at the start of your application - to give time to send an AT+WOPEN=0 if necessary!

Now I agree with you . I will do that.

the luck is that there is per default a little delay between init of box and start of application!