0 Members and 2 Guests are viewing this topic.
OSLauncher does not permanently install the CAS OS, it merely hot-launches it (and often fails to, for some reason nobody has bothered to investigate). The Press To Test (PTT) mode triggers a reboot and therefore undoes the effect of OSLauncher anyway, so you wouldn't have to do anything yourself, for your calculator to be usable in standardized tests
// Killing all interrupts is necessary (exercise for the reader: why ?) *((uint32_t *)0xDC00000C) = 0xFFFFFFFF; __builtin_memset((void *)0x10000000, 0, 0x02000000); // Useful ? __builtin_memcpy((void *)0x10000000, dest, ziphdr.usize); // Useful ? __builtin_memcpy((void *)0x00000000, (void *)0x10000000, 0x40); // This is also necessary (exercise for the reader: why ?) *((uint32_t *)0xC000001C) &= ~((1 << 0) | (1 << 11)); // Launch the OS. asm volatile( ".arm \n" "mov lr, pc\n" "ldr pc, =0x10000000\n" );
// Killing all interrupts is necessary (exercise for the reader: why ?)*((uint32_t *)0xDC00000C) = 0xFFFFFFFF;
// This is also necessary (exercise for the reader: why ?)*((uint32_t *)0xC000001C) &= ~((1 << 0) | (1 << 11));
The message i get from trying to use a regular touchpad nSpire with CAS commands is a message bow that tells me to buy a CAS
The CAS for regular nspire might not actually be good and my lead to the downfall of the nspire for things like the ACT because CAS calculators are not allowed to be used on it and if an OS included CAS functions, they might disallow all nSpires for the test.