teleko7
Junior Member level 2
- Joined
- Sep 27, 2009
- Messages
- 24
- Helped
- 2
- Reputation
- 4
- Reaction score
- 2
- Trophy points
- 1,283
- Location
- Basque country, Spain
- Activity points
- 1,560
Hello Harley
Nice to know you got success with SIM900 EAT. I have been working on EAT for last 2 weeks,so far i can compile code for EAT on SIM900 IDE using RVCT2.2_616 (cracked versin) . it is not genuine ARm compiler. as ARM is not supporting old compiler any more. i got it dnld 4m a different forum. as i mentioned above i can compile the codes without any errors, but i noticed firmware files (e.g *.cla) are not generating properly with this compiler. It wud be gr8 if u cud show us your work here and the procedures.
Thank You.
Chinmay
Hello IbanHi all.
I'm working with a SIM908 module, with RVCT2.2_576 (cracked also). I compile my projects with SIM908_DTMF_DevIDE withouth problem, but when I try to dwl them, a message shows up: "The FLASH type does not match the firmware". The thing is that despite the installer being called "SIM908...", the IDE executable is called "SIMdevIDE" what wouldn´t bother me unless I saw that the only two compiling options are SIM900 and SIM900B. I think the core of a SIM908C is a SIM900... but as it keeps on giving this same FLASH error message all the time... now i doubt... any help??
T.I.A.
Iban
Hi Chinmay
Nice info!! Thanx a lot. Just as I was reading your email, I got a response from Texim-Europe (really fast and good service!!) with core file update and precise instructions from SIMCOM tu load new FW onto my SIM908. I have succeeded on it so i can finally start developing apps.
As to the debug stuff... I put a trace string like "ebdat7_01DebugTrace("Im alive!!!");" just after the main while. In the debug window i get strange characters... may be a matter of bauds, I haven´t had enough time to mess around. In the comm settings i have put my main comm port, so i guess... as I haven´t changed FCM stuff, what i'm getting are the AT commands or answers from the modem...I'm not sure. I would have to check the compiled code (tcp example project)... I will change comm settings to debug port and see if i get something intelligible.
Will tell you.
At least, now it works!! If you needed my core .cla file (i pressume is similar to yours) or any other stuff, let me know.
Thanks
Iban
Hey Iban
We had luck n got it work. Did some cool things.e.g we add RFID reader with sim900 module tro SPI n pull sms on sweep wid tags. traced modem working status 4m debug port, and we currently testing other EAT features with d module. But it took some hard research to figure out work it. The very 1st thing you need is the CORE FIRMWARE for exact EAT. this firmware file contain an additional .sbm file wich actully make the bridge part between core firmware and your embeded api. this firmware is different from general update sim firmwares. may be you need to ask ur distributor, in my case i asked to simcom directly for given support of EAT firmwares for SIM900 or SIM908 module.
for your case sim908 try one of this EAT firmwares.
1. ftp://ftp.macrogroup.ru/Support/SimCom/Embedded AT/firmware/1137B01SIM908M64_ST_DTMF_JD_EAT.rar
2. ftp://ftp.macrogroup.ru/Support/SimCom/Embedded AT/firmware/1137B04SIM900M64_ST_EAT.rar
For me 2nd one works completely. Note that EAT API .cla file wont works with SIMCOM regular Firmwares, we have tested and confirmed, you can only work with combination of EAT Firmwares and EAT api .cla. So dnld the both sim core flash n eeprom flash. make sure your address for memory flash as per donld sw. dont change address for EAT api.cla file. if you do you will lose you module. Try this carefully, it sud work for you.
Thank you
Chinmay
Hello Iban
Yah it is little bit confusing because itz not explained in any simcom documentation. My conclusion is based on wht we found during my research into this. Let me explain to how both files are different.
there are two types of firmware is supported by SIMCOM.
1. 1137B03SIM908M64_ST.rar (Normal firmware)
2. 1137B01SIM908M64_ST_DTMF_JD_EAT.rar (EAT Firmware)
If you looking into dees two rars or extract dem, you will see 1st one has 4 files as *.cla, *def, *.str, and *.x .
but the 2nd has all dees files in addition *.sym file. and this 5 file combination require to enable n run user api 4m sim module. As *.sym file has all the function to address list, while u compile api over EAT firmware, dis file actully make the bridging part between CORE SW and USER API.
As normal firmware doesnt hv dis file inculded, so user api doesnt work wid it.
But yes u need to load EAT firmware just once b4 loading application firmware. After dat u can load only api firmwares as many time u want, as long as The core EAT firmware is unchanged to Normal Firmware.
I hope this explanation will clear your confusion, if u got doubt on it. hit me again.
Till den happy Coding.
Chinmay
just currious about the samsung tag ? whats it?I was planning to joke about the fact i replied myself, but i'm a grown up...
Anyway, just sharing...
its late reply but still it can help others have found some firmwares including one with JD DTMF for Sim900D , Shared it on my blog http://www.dostmuhammad.com/blog/a-collection-of-firmwares-app-notes-and-guides-for-simcom/Is there a similar version for SIM900D?
Is there a version for SIM900D with jamming detection enabled?
Thanks.
its late reply but still it can help others have found some firmwares including one with JD DTMF for Sim900D , Shared it on my blog http://www.dostmuhammad.com/blog/a-collection-of-firmwares-app-notes-and-guides-for-simcom/Is there a similar version for SIM900D?
Is there a version for SIM900D with jamming detection enabled?
Thanks.
Sim900 can be drives easily! so, can we drive Sim908 as easy as sim900?
Hello Chipseller can u please get me latest firware for SIM908/SIM908-C modules. MY current Firmware is SIMCOM_SIM908 Revision:1137B03SIM908M64_ST. Thanks In advance.
Yay, I got the Sim900 EAT system working too.
I started off using the SimDevIDE tool however I thought it nicer to use Eclipse. After some experimentation I got Eclipse compiling using RVCT.
It is possible to set Eclipse up to compile using either RVCT or GCC.
After some more experimentation (and help from simcom) we got the free GCC compiler working using EAT on Eclsipse. You need to use the EABI GCC compiler then that is really nice since you see compiler errors nicely highlighted in red. You get the usual code completion and basic C++ syntax checks.
Maybe I will set up a page showing how to set it all up if anyone is interested. Running EAT on the SIM900 using GCC or RVCT
Cheers,
Harley
Hello Iban
Yah it is little bit confusing because itz not explained in any simcom documentation. My conclusion is based on wht we found during my research into this. Let me explain to how both files are different.
there are two types of firmware is supported by SIMCOM.
1. 1137B03SIM908M64_ST.rar (Normal firmware)
2. 1137B01SIM908M64_ST_DTMF_JD_EAT.rar (EAT Firmware)
If you looking into dees two rars or extract dem, you will see 1st one has 4 files as *.cla, *def, *.str, and *.x .
but the 2nd has all dees files in addition *.sym file. and this 5 file combination require to enable n run user api 4m sim module. As *.sym file has all the function to address list, while u compile api over EAT firmware, dis file actully make the bridging part between CORE SW and USER API.
As normal firmware doesnt hv dis file inculded, so user api doesnt work wid it.
But yes u need to load EAT firmware just once b4 loading application firmware. After dat u can load only api firmwares as many time u want, as long as The core EAT firmware is unchanged to Normal Firmware.
I hope this explanation will clear your confusion, if u got doubt on it. hit me again.
Till den happy Coding.
Chinmay
Hey Iban
I hvnt move to SIM interrupts yet, but i think b4 setting GPIO to interrupt, you need to configure GPIO state to Input setting. go to GPIO settings , change or set GPIO as input pin. den check if it works or not. SIM docs has not describe many thing in coding,so many thing u need to find out on guess work, we are doing the same. so chk it, if it doesnt work i will look into it.
Chinmay
Hi Chinmay
Yes, as you mention, documentation is not a strong point of this (otherwise good for me) module. I have also been doing lots of trial and error but no way i can get an interrupt from the core... With regards to defining the pin as input first, speaking from what I have understood reading the EmbeddedAt manual and what I've seen from the module responses, both modes (GPIO and GPIOInterrupt) are mutually exclusive, so that if you try to set a pin as input and then you define the triggering option, you get "FL_PARAM_ERROR" for an answer.
Thanks again.
Iban
Hey Iban
Any progress on ur work? kindly post ur updates.
Thank You
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?