0 Members and 2 Guests are viewing this topic.
After recently buying a Prime, I've now spent several hours making my own armfir.elf. The result is attached.The code fills one third of the screen with red, one third with green, and the last third with blue (with some glitches...), then enters an infinite loop. Yeah, this PoC sucks, I know - it sucks just as much as my Nspire DummyOS did, more than three years ago.Usage: copy the armfir.elf file into APPSDISK.DAT. Firmware transfer, enter recovery mode by pressing the Reset button in the hole on the back, pressing the Symb key, releasing the Reset button, and holding Symb until the Recovery mode screen appears. Then, use usbtool (Windows only).As usual: works for me, but use at your own risk
So, what I'm getting from this:There's no built-in native coding tools, but they have done nothing to stop us from making our own OS with such features built in, even so far as replacing it with an entirely new system.That is just about the best case scenario.
So we just need to apply the lessons we learned with the Nspires, and then we have a good time with assembly.
Quote from: ordelore on July 07, 2014, 11:37:53 amSo we just need to apply the lessons we learned with the Nspires, and then we have a good time with assembly.There is no lesson to get from what happens on Nspires. They are not closed because of a move from the community, they were always closed. Now, I don't say that a program against TI's interest is a good idea, just that even if it contributes to nothing good, it did not start the whole thing either.Just a question about the HP Prime, would it be possible to "patch" an OS, kind of like what Ndless does ? Because I don't really like the idea of having to choose between HP's OS and the "Ndless" OS.