Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Register Log in

SIM900 Customer Flash Loader

Status
Not open for further replies.
cnd said:
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
Click to expand...


Hi 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
 

teleko7 said:
Hi 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
Click to expand...
Hello Iban
we have done lot of hit n trial to work on Sim900. so far we got solid concrete procedure from here. "ftp://ftp.macrogroup.ru/Support/SimCom/Embedded%20AT/tools/ " .
At my case we code, compile n load sucessfully, but i ddnt get any out from debug port whn i was trying trace out EAT. it turns out coresw n app files are not matching in combination. So technically Core update Firmware is working , but not EAT app.

At your case find Custom firware downlder v 1.04. which for SIM908.

We have been trying to make it work since last 2 weeks. Let us know ur work updates.

Update:

Hey please Update your SIM908DevIDE with this one. It Includes SIM908 Customer Flash Loader v1.5. I think this will solve your issue.

ftp://ftp.macrogroup.ru/Support/SimCom/Embedded%20AT/firmware/Compiled%20example%20for%20Sim908.rar

Thanks Chinmay
 

Attachments

  • Compiled example for Sim908.rar
    13.6 MB · Views: 234
Last edited:
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
 

teleko7 said:
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
Click to expand...

Hey Iban
Good to know your thing is working now. at my case using debug port as additional serial is the goal. so tracing debug port is just one way to start. AS u mentioned I also received garbage value from Debug port during power on the modem. but after that i ddnt get any of the trace sting from the core w.r.t to AT response for main UART of sim module.
I am using 2 comm port to trace, 1 for main UART and another for Debug port. Baud rate for both ports are set to 115200.(I like to stay on default baud setting).

my doubts are , does EAT api needs core-EAT.cla firmware support to run api or EAT api can run with default firmware loaded on module?

i will run few more codes n research more into it tonight n will update soon. wish me luck. :)

Chinmay
 
Hy Chinmay

No progress over here... No matter the app I download, whatever the core file i download, when i set the switch to "RUN" i get all the time this 8 characters periodically: " 0x49 0x49 0x49 0x49 0xFE 0xFE 0xFE 0xFE "... even if my app is only a

while(TRUE){}

I still get these garbage characters!!!

I have no clue what's going on... Compiler gives no errors, download process (both for core file and app) says OK... somebody else who got an application succesfully running on a SIM908??? Could you please share the core file and the app .cla file just to get something to work in my SIM908???

T.I.A.

Iban

P.D.: Chinmay: Wish you luck!!
 

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
 
cnd said:
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
Click to expand...



Hi Chinmay

Thanx again!!! I'll try it tomorrow... But this confuses me a bit... Until your reply i thought that core ".cla" files and user application ".cla" files where completely independent from each other... That is, I understood that the latest core ".cla" file would be backwards compatible with all the example firmwares released by SIMCOM... I thought that user applications would run withouth problem as long as the latest core file was downloaded onto the module...

Thanx again, now you, wish me luck!! :)
 

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
 
cnd said:
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
Click to expand...


Hi Chinmay

Many thanx for your last post, I think I got it (99,9% sure). I sent the CPIN command and after that I got "PIN READY" and "CALL READY" from the module so... i guess now it´s only a matter of coding right...

In short: get the right core files before you download your app.

THANX!!!!
 

RafaelLopez said:
I was planning to joke about the fact i replied myself, but i'm a grown up...
Anyway, just sharing...
Click to expand...
just currious about the samsung tag ? whats it?

- - - Updated - - -

Kosh said:
Is there a similar version for SIM900D?

Is there a version for SIM900D with jamming detection enabled?

Thanks.
Click to expand...
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/

- - - Updated - - -

Kosh said:
Is there a similar version for SIM900D?

Is there a version for SIM900D with jamming detection enabled?

Thanks.
Click to expand...
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/

- - - Updated - - -

behnam9856 said:
Sim900 can be drives easily! so, can we drive Sim908 as easy as sim900?
Click to expand...

cnd said:
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.
Click to expand...

**broken link removed**6.9 MB
**broken link removed**6.3 MB

The Enhance versions support all the functions
check http://www.dostmuhammad.com/blog/a-collection-of-firmwares-app-notes-and-guides-for-simcom/ for updates
 

Hi everybody,

Has anyone finally got work the SIM900 EAT or SIM908 EAT with GCC compiler instead RVCT2.2_616 version?.

If someone has had success making it, please post the procedure to make this working in GCC Compiler.

Regards,
Ignacio

marleydc said:
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
Click to expand...
 
Last edited:

cnd said:
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
Click to expand...

Hi Chinmay. I have a final question: I´m trying to wait in my code till a GPIO rising edge generates an EVENT_INTERRUPT event. But no matter the voltage I apply at pin 55 or 56, no edge is detected. These are the steps I follow:

1) Unsubscribe pin

2)Set pin to Interrupt

3)Set rising edge

4)Set de-bounce time to 20

In all of them I check taht i get FL_OK as a response, so it should be OK. But when I apply 3volts to the configured pin no EVENT_INERRUPTS shows up... May be interrupts are not supported by my core file??? 1137B01V01SIM908M64_ST_DTMF_JD_EAT

Do I have to write something in the lib files??

Anybody who succeeded with GPIO interrupts??

thanks in advance, best regards

Iban
 

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
 

cnd said:
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
Click to expand...

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
 

teleko7 said:
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
Click to expand...

Hey Iban
Any progress on ur work? kindly post ur updates.

Thank You
 

cnd said:
Hey Iban
Any progress on ur work? kindly post ur updates.

Thank You
Click to expand...

Hi Chinmay. Yes, thursday I succeeded with interruptions... I'm still "fine tuning" my code, that´s why I haven't replied yet. But as I was afraid of, it was a matter of a new core file...so I asked for and got a new file "1137B02V01SIM908M64_ST_DTMF_JD_EAT" together with a new downloader, and it worked. I think SIMCOM customizes core application files according to their needs "on the go" :) so, it´s quite "trial and error and asking". But my module works fine with INT-s now. Find attached rar. IMPORTANT: User App address is 00400000.

A problem I see for so many different core files is that they have to be well documented, saying for each one what is it for... and what it does not do yet... :)

One thing I have noticed is that I can only set pins 55 and 56 to GPIOInterrupt. I used a loop from Pin nr. 1 to Pin nr. 150, using integer values instead of labels, not to miss a possible unknown pin value, and only pins 12 and 13 (PIN_FL_55 and PIN_FL_56, SCL and SDA)where able to be set to GPIOInterrupt. Once again core file issue?? Somebody something on this??

If you have any doubt let me know. Hope this helps!!

Iban
 

Attachments

  • 1137B02V01SIM908M64_ST_DTMF_JD_EA_with_downloader.rar
    20.1 MB · Views: 175
  • Like
Reactions: cnd

    C

    cnd

    Points: 2
    Helpful Answer Positive Rating
1) Is there some program that READ the firmware from the SIM900?

2) Where can I obtain the latest SIM900L firmware?

Thanks.
Kosh
 

Hello...
I searching for 1137B01SIM900A64_ST_MMS. please help me...
thanks
 

hello
my firmware sim900B is 1137B08SIM900B32_ST
dtmf isnt work
please help me to work dtmf with sim900B
 

Status
Not open for further replies.

Similar threads

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top