I’m not sure of what you mean. But anyway, I don’t think you can.
The OTAP/Syslog command only enables OTAP logging messages on your local console (whether it’s ASC0, ASC1 or USB). You shouldn’t need to save it anywhere, it’s only useful when your OTAP doesn’t work and you have no idea why. It helps you to :
- Diagnose wrong OTAP SMS sent
- Diagnose problems in the actual OTAP process (DNS failure, server connection refused, wrong JAD file, wrong JAR file).
Hey Florent, I know this blog post is quite old now, but I have a semi-related question. I’m rewriting software that runs on the XT65 module and have been testing OTAP recently. I notice the AMS logs this out (just before reboot I think):
EVENT_STOP received, wrong implementation of MIDlet
Ever seen this before or have an idea of what it means? Is it problematic? What does my application code need to do to avoid this?
Not sure if you’ll get this comment, but thanks in advance for your insight.
When the application shutdowns because the chip shutdowns or restarts, the destroyApp method is called. You have 5s to clean everything (like saving the data currently in memory, closing sockets, etc.) and you have to call the notifyDestroy. (ref Java_UserGuid.pdf : 5.7.2)
So, to solve it, you must properly handle the destroyApp method.
I have seen this error before and it never created me any problem. So, you shouldn’t worry about this. The only thing you should always avoid is restarting the chip (AT+CFUN=1,1) within the destroyApp method, I’ve seen some people doing it. I don’t think it solves any problem and it totally messes up the OTAP process.
Yes, you’re right. If you have access to one chip that shows the OTAP password and the other parameters (like the server name) are left unconfigured, you could update the program of all the chips.
In the real world, I don’t think that should be an issue. Because you still have to guess all the numbers, the correct APN settings and hope that nobody finds out what you did. Because I think it’s clearly considered as hacking a system.
One way of securing your chip could be to define an OTAP SMS password depending on a secret key and the IMEI. In PHP code this would look like this “$otapSmsPass = substr( md5( $key.’-’.$imei), 0, 8)”.
But the real solution, is to create deploy a certificate on the chip and sign all the produced code with it. This is the best way to create a really secure product but it takes a little bit of time.
I think the real risk around OTAP is to get the program that runs the chip. Because reproducing the hardware is quite easy but running a successful software can be quite tricky, if you can steal it, you can save a lot of time. If the program is correctly built, you might just have few days of reverse-engineering and refactoring to do. As the TC65 programs usually do mostly AT Command and API calls, it’s quite easy to do.
I have problem with OTAP…I dont know where is wrong…this my log in hyperterminal
[OTAP] ERROR: Network is unavailable!
[OTAP] Reboot now.
I’m using OTAP on a TC65i, FW02.004, with differet providers. The provider “Orange” (Austria) works fine, but with the provider “A1″ (Austria) i always get the message “[OTAP] ERROR: Cannot establish connection!” back. In normally use, the http connection works with A1, the parameters for the connection (APN, username, password) are correct.
Do you know about this problem? My update string for Orange:
Update string for A1: