Author
Topic: New TI-Nspire emulator: Firebird Emu (Read 87223 times)

You may have heard about it already, but if you haven't… this is the official first release of Firebird Emu, a new TI-Nspire emulator!The core of Firebird is based on Goplat's renowned "nspire_emu", but with quite some changes.

But I've started looking around in WatchKit, too... so maybe some day the iPhone app will "broadcast" the screen to the watch. Or even get to compile the emu for the watch itself (btu I doubt it, that would require Qt to be ported there, and there's pretty much no way that happens )

Evidently, it would be just for fun, considering the screen size, though.

But I've started looking around in WatchKit, too... so maybe some day the iPhone app will "broadcast" the screen to the watch. Or even get to compile the emu for the watch itself (btu I doubt it, that would require Qt to be ported there, and there's pretty much no way that happens )

Evidently, it would be just for fun, considering the screen size, though.

Yeah, broadcasting the screen seems like the best way to do it, you could have the screen on your wrist and the keypad on the phone.

Yeah, broadcasting the screen seems like the best way to do it, you could have the screen on your wrist and the keypad on the phone.

Yep, that was the idea.

Also, I see you want to test it on a [jailbroken] iPad - you may want to /query me on IRC (Adriweb on EFNet) for instructions on how to set it up on iOS, it's not trivial (well, at least, to get it to compile with the JIT (since you're jailbroken, let's enable the translation). Once we figure out a process that works for you as well, I'll edit the readme instructions accordingly.But so far, here's my workflow (assuming Qt Creator is set up):

- launch build so that it creates all the needed files- clang -marm -o asmcode_arm.o -c asmcode_arm.S- move asmcode_arm.o in the objects folder- add asmcode_arm.o to the .linklistfile- lock both files so that the next rebuild won't overwrite them- re-launch build- Deploy- In iTunes, transfer the boot1 and flash

I compiled it myself from source on win32/mingw and noticed two things:

After startup of the OS, when left-click dragging around the touchpad on the on screen keyboard, the emulator might display "Invalid mode 0x0" and then no more input is accepted. Sometimes no more input is accepted without the display of the error message.

The emulated timer hardware appears to match the % emulation speed display, so it is off by some factor. I tested with some projects of mine and its most noticeable in nQuake when doing timedemo runs ( timedemo says the playback needed N seconds but in real time it took around N * 1.45 seconds ).

After startup of the OS, when left-click dragging around the touchpad on the on screen keyboard, the emulator might display "Invalid mode 0x0" and then no more input is accepted. Sometimes no more input is accepted without the display of the error message.

Invalid mode means that the OS crashed or the emulator did something weird, so it's not a UI thing. What OS are you using?I don't have windows installed anywhere where QtQuick runs (so, OpenGL accelerated), so I tried it under wine with the prebuilt packages and could not reproduce.

Quote

The emulated timer hardware appears to match the % emulation speed display, so it is off by some factor. I tested with some projects of mine and its most noticeable in nQuake when doing timedemo runs ( timedemo says the playback needed N seconds but in real time it took around N * 1.45 seconds ).

Ok, so it's not a mistake in the percent calculation, it's in the throttle itself, will likely be solved in the near future.

I tried the emulator on windows and if I try to install ndless on it the emulator crash.Has anyone a suggestion why?

What does crash exactly?

The same happens on mac, the emulator crashes, when you try to install ndless it just halts and then exits.

It behaves differently depending on the user interface mode, if it is in Docks mode and I try to install ndless, the emulator halts and displays this in the Debugger: "Warning (102fce8c): Data abort: address=0101010d status=05 instruction at 102fce8c"