We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
I have two devices purchased from mouser in the last couple of weeks.
When I initially fired them up AT+VER returned
1.0.1,2.9 OK
I then setup my ST-Link v2 & FTDI
I then backed them up and two files were created in the bin directory
303634327C376902.bak 343834335F368F09.bak
I then wanted to update the devices two the most recent software (4.0.0.2) but it failed
or
When I now query the devices with AT+VER I get
ERROR_INVALID_MODULE
How to I recover from this?
Thanks
@KiwiBryn
The text was updated successfully, but these errors were encountered:
I had a look at the recovery document WM-SG-SM-42 recover guide.pdf when I try and STM-Link I get this error
I'm currently stuck and have burnt a bit of time trying to get this to work.
Sorry, something went wrong.
Any assistance would be greatly appreciated...
It's been more than two months with no reply, any assistance would be greatly appreciated...
No branches or pull requests
Hi,
I have two devices purchased from mouser in the last couple of weeks.
When I initially fired them up AT+VER returned
1.0.1,2.9
OK
I then setup my ST-Link v2 & FTDI
I then backed them up and two files were created in the bin directory
303634327C376902.bak
343834335F368F09.bak
I then wanted to update the devices two the most recent software (4.0.0.2) but it failed
or
When I now query the devices with AT+VER I get
ERROR_INVALID_MODULE
How to I recover from this?
Thanks
@KiwiBryn
The text was updated successfully, but these errors were encountered: