Search

cakeisalie5 wrote:Also, is there a manual with everything Hmake supports in it?

The last few pages of
"Renesas High-performance Embedded Workshop V.4.05 Manual"
contain the maximum information about HMAKE I could find up to now.

cakeisalie5 wrote:By the way (sorry if that's not the correct topic to deal with this), does Hitachi's compiler define any compiler-specific macro, something like __HITACHI__?

Yes. __HITACHI__ (1) and __HITACHI_VERSION__ (0x0600).

The OS checksum:
At 0xA0B5FFF8
0xA0020000..0xA0B1FFFF + 0xA0B5FEF0..0xA0B5FFF7
(As with fx-CG20 OS 2.02)

Found this today online, and as you told me OHP was only possible on USB, I'm quite surprised... is there any way to do OHP on serial? They swapped the physical port order on the PCB with the fx-9860GII types. The calculator pictured here is a fx-9860G connected via USB to a OH 9860. But indeed I s...

The fx-CG50 OS is very similar to the fx-CG20 OSes. I am a bit disappointed. Looks as if there are no secrets to unravel. Apart from the RAM-address there seem to be no grave differences. INSIGHT, NOTEVIEW, FARGOAL and even a relatively complicated UBC-tool work well (OK, I wrongly used 0x88000000 a...

Do you know if anyone knows where the table of the names and icons of the built-in add ins is stored in the OS? And how to get that offset? I want to make a program which can edit the icons of the 2.0 firmware to match the new white ones. Basically I'm trying to patch OS 2.02 to be a fake OS 3.0 wi...

You have to activate "receive" on the receiving calculator before starting "transmit" on the other calculator.
I just checked it between my CP400 and CP330plus.

AmazoNKA wrote:Sorry for being ignorant with this type of things...
Would add-in with vram address being hardcoded as 0xA8000000 still work on fx-cg50 please?

No. Syscall 1e6 returns 0xAC000000.

Also, for what I've seen, Projector and ScreenReceiver are the same things, and ScreenCapture is basically just about sending one OHP packet then going offline. Is there any difference between Projector and ScreenReceiver, maybe in the syscalls it uses to read screens? Does USB_CaptureDisplay also ...

...you added the checksum member, is this member never read/written by any syscall or always generated before sending or at reception, without sending to the user? (was this structure member a supposition that, in the end, was not correct?) The Comm_Prepare****Packet-syscalls set this byte to zero....