Bisam a écrit:critor a écrit:I already checked this, as it would be much better than those fingers-killing-keys.
[...]The problem is the keypad state is not accessible in RAM, but through a port I couldn't write to.
I thought it could be possible to dump that menu, copy it to another memory zone (like Extended or else) and launch it from there, as for Diags, as I said.
It's a feature built inside the Boot2, so extracting the related code wouldn't be easy.
Bisam a écrit:Something else : how do you erase a part of boot2 zone (or any other zone) with BtMg ? Can it be done only by overwriting ?
I've never added an erase feature to BtMg.
Mainly because it wasn't there in nsNandMgr, and this was for security reasons. If you remove all Boot2 images, your calculator is bricked.
BtMg still lets you overwrite useless images with something else.
But I'm not completely against adding it, as there is already a growing difference between both tools :
- nsNandMgr for compatibility with old tutorials and basic harmless features
- BtMg for more advanced features
So please, tell us about the kind of context in which you need this.
Bisam a écrit:And yet another feature idea.
How about copying a full OS in Extended zone and allow to inject it (as nSwitchOS does) from CtrlX before Boot2 starts ?
One could recover from a wrong manipulation which deleted the OS (on purpose or not) without using a computer.
Like the Boot2 maintenance menu, it's also something which has already been thought of.
But it's not easy.
Installing an OS needs write access to the filesystem.
In the Boot1/ControlX context, there are no filesystem drivers.
So although we have write access to the filesystem partition, it's just raw data. We don't know about files or folders, since all C files/folders functions (fopen, fwrite...) are missing and unusable.
