Re: [javacint] Problem connecting Siemens TC65 Terminal

[Nikita Kapitonov]

Hello, Gilhiu!

I think if you cannot reach the AT-interface, you cannot upgrade its firmware anyways.

So its bricked, go get a new one, maybe better based on newer chip like TC65i-X.

Nikita

2013/4/5 gilhiu jubgukh <in3...@gmail.com>

Hi all !
I am new to TC65 modems.
I have a TC65 modem that was used and programmed in java by someone else in the past.
Now I have to implement a new java program.
As a first step I tried to connect the modem via serial cable and putty terminal.
When I plug in the power connector I get on the terminal the following and I am not able to send AT commands:

^SYSSTART

^SHUTDOWN

^EXIT 00010000,02b1414e524d324c434c2c4e5652414d2072656164206661696c757265

This last string translated from HEX is:

??ANRM2LCL,NVRAM read failure

This doesn't sound good...

If after this message I press shortly the On/Off button, I get on the terminal:

SHUTDOWN after Illegal PowerUp

At some point trying to connect the terminal, I got also as output a continuous stream of this:

2006-03" ÿÖ KATHY_ALL_246R:RELEASE:Fri 15.12.2006:19:33:ccalbd&Bootloader version: Bln-Bootloader V2.0&cfc_version.h:  /main/dev01/10 $, 2005-10-12 13:28:11 $&cfc_types.h:  /main/dev01/21 $, 2006-03-09 08:10:49 $&cfcrpc.h:  /main/dev01/27 $,

Does someone have an idea of what is happening and what I can try?
Is my TC65 bricked? If yes, it is possible to reset the TC65?
I read something about Firmware Update in the Application Note 16 (AN_16_FW_Update.pdf).
It is possible to get a factory firmware and flash it on the modem?

Thank you all very much!

Best regards,
Gilhiu

--
javacint group - http://www.javacint.com/
---
You received this message because you are subscribed to the Google Groups "Cinterion Java enabled chips support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to javacint+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[gilhiu jubgukh]

Thank you Nikita,

so there is no way to act at a lower level than AT-interface ?

This is strange, for embedded system I think usually it is possible to refalsh trough low level serial port.

Anyway, thank you very much.

2013/4/5 Nikita Kapitonov <nikita.k...@teplomonitor.ru>

[Florent Clairambault]

Hi Gihiu,

NVRAM read failure means your device is bricked because it won't be able to store any of its settings. I suspect this happens when people do a lot of changes in the NVRAM (with AT^SCFG commands) but I have no proof of that.

I think there are few ways to communicate at a lower level (OBEX protocol is used for file transfers, something else for firmware update, and maybe something else for development) but they are undocumented.

This device has very little in common with most of the other embedded devices you find on the market. Programming is way easier but getting in the low layers of the system is impossible.

Best regards,

--

Florent

[gilhiu jubgukh]

Hi Florent,

thanks for the info, I'll try to use another similar device for my work.

But just for fun I will try to investigate further how the siemens TC65 works at a lower level.
Maybe with JObexFTP I can go a little further ?

PS: I found out that in the wiki, the page http://www.javacint.com/%5EEXIT_errors  was edited by someone

replacing the usefull content of the page.

The original content is still reachable trough the history functionality.

If you or someone else has access to the wiki the original content can be restored.

The same is true also for other pages on the wiki where sone information was removed, i.e.:
http://www.javacint.com/OTAP
http://www.javacint.com/Handling_time_on_the_TC65i

I don't know if this was an error...but it is a shame that usefull information is wasted.

Thank you very much Florent.

Regards,
G.

2013/4/6 Florent Clairambault <flo...@clairambault.fr>

[Florent Clairambault]

Hi,

Thank you. I reverted it back these pages to last correct versions, banned some users and changed the settings to force email validation.

I think jobex ftp is just a high-level communication protocol, something else might be used for firmware transfer. If you want to investigate this, you should use portmon and flash the chip with an other firmware then analyze the portmon logs (like we did in the past for obexftp here).

Best regards,

--
Florent