0 Members and 1 Guest are viewing this topic.
Isn't the boot2 programmed into the nand?
How does it get loaded then?
Would boot1 be easier to rev-eng if it needs to access the flash?
I don't want to lose my loved boot2 Does is work in nspire emu?You could easily compare the image with your bytes read.
Now, how should I test write support without killing it?
QuoteNow, how should I test write support without killing it?Use nspire_emu, even I wasn't able to brick it ;-)If it works, test it on real hardware (Please do it, I don't want to brick mine :-) )We really need to get linux running with nspire_emu, that would make thinga lot easier
Just emailed you something that may be of interest. Linux doesn't run on nspire_emu right now though
I also added MTD partitions into the mix so you can dump your boot2 and diags via Linux if you really wanted to
The worst that can happen is that I have to reinstall the OS
QuoteJust emailed you something that may be of interest. Linux doesn't run on nspire_emu right now thoughI read it, but seems to be not very useful :-(QuoteI also added MTD partitions into the mix so you can dump your boot2 and diags via Linux if you really wanted to Could you implement one for the filesystem, too?I'd experiment a bit with flashfx support. (Which seems to be harder than reliance)QuoteThe worst that can happen is that I have to reinstall the OSActually (but not very likely) you could damage boot2 if you write to the wrong bytes.
Edit: Heh
@Vogtinator, we could use this to write a read-only filesystem driver for FlashFX and Reliance? http://ourl.ca/99835