View topic - Mapping a file to memory

by **AmazoNKA** » Fri Jun 10, 2016 12:39 am

When I try to download FX-CG Manager Plus (90 day trial for windows) it takes me to 2.00 version of it only - how do you get the updated one please?

By the way M2 is pmed to you as well and I will do M3 shortly but then have to sleep - so will do the other ones tomorrow hopefully

by **TeamFX** » Fri Jun 10, 2016 11:00 am

Do you know if I will be able to keep both versions - i.e. 2.00 and 2.02 - or any workaround to achieve that please?

Try installing both and use different installation paths.
Emulator download: https://edu.casio.com/softwarelicense/

by **AmazoNKA** » Fri Jun 10, 2016 1:47 pm

Thanks for the link - i can see 2.02 version now and they have it as a subscription service now and it seems to go to another folder during installation. I haven't tried it on the machine i have my older emulator on to see if they work alongside each other yet. But can confirm that on the new service going from main menu to system version shows 2.02.0201 or something similar with 1 at the end as well similar how it looks on my latest hardware calculator.

Thanks again and I will do other memory back ups for you later.

by **AmazoNKA** » Sat Jun 11, 2016 12:20 pm

Hi TeamFX, I have just PMed you M4 and M5, and in the process of saving the last one for you - let me know if anything is missing or wrong please. Kind regards

by **AmazoNKA** » Sat Jun 11, 2016 12:30 pm

Should all be with you now - I also checked now that they are all different to make sure I did not duplicate something by mistake - so I hope they are all good but let know please if not.

by **TeamFX** » Sat Jun 11, 2016 2:40 pm

Well, your OS is identical to the official one... :think:

Even all the bits that are not covered by the OS checksum are the same - which is good.
Only those bytes at 0x80B20000 differ. This is where some unknown exam mode information is stored.

Regarding the OS version difference, this is what I could find out:
Starting with OS 2.02, four bytes at address 0x8001FFF0 are inverted by the OS version routine.
2010.0910.1621 boot code: ~0xFFFFFFFF == 0
2015.1116.2146 boot code: ~0xFFFFFFFE == 1
It appears this is a very stupid way of differentiating either boot code or hardware versions.
I could not find other places where this value is checked.

Now we should take a look at the new boot code.

by **AmazoNKA** » Sat Jun 11, 2016 2:57 pm

Thanks for sharing you findings. By the way i saw more screenshots on Chinese cncalc.org with os version and diagnostics screens having 1s at the end. Let me know if you would like links please

by **TeamFX** » Sat Jun 11, 2016 3:08 pm

I only know this: http://www.cncalc.org/thread-11883-1-2.html

by **AmazoNKA** » Sat Jun 11, 2016 4:27 pm

I think I got confused - I saw 1s in "[LY755.. MAIN] 111" on those Chinese pictures only, sorry

by **TeamFX** » Sun Jun 12, 2016 4:52 pm

There is only one small functional change in the new boot code:

During the OS update procedure, a new subtype value 07 is included in the ACK response following command subtype 0A.
The same code is present in the OS 2.02 update routine, but missing from OS 2.01 which added exam mode.
The value is always sent regardless of the model or hardware version.

Not very useful if you ask me, but it may prevent using old setup files for updating.

View topic - Mapping a file to memory

Mapping a file to memory

Re: Mapping a file to memory

Re: Mapping a file to memory

Re: Mapping a file to memory

Re: Mapping a file to memory

Re: Mapping a file to memory

Re: Mapping a file to memory

Re: Mapping a file to memory

Re: Mapping a file to memory

Re: Mapping a file to memory

Re: Mapping a file to memory

Who is online