sys64738
/
mspbsldump
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

bleh

This commit is contained in:
Triss 2022-04-10 19:13:38 +02:00
parent 1fe6850ed7
commit c36b0e08b0
2 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -119,7 +119,9 @@ described near the end, the article is quite large.
1. Pipelining: can code running at `0x0FFE` (or a similar address) access the
BSL memory, (mis)using the possibility that the effective value of `pc`
might differ from the executed address due to pipelining effects? (cf.
[MerryMage's GBA BIOS dump](https://mary.rs/lab/gbabios/))
[MerryMage's GBA BIOS dump](https://mary.rs/lab/gbabios/)) NOTE: `0x0FFE` is
not backed by anything and always reads as 0, so getting this to work will
be tricky.
1. DMA: can a DMA transfer be used to change the stack contents during BSL
execution? (Most likely, just like interrupts can, I simply haven't checked.)
1. Dumping of the `0x1b00`..`0x1bff` region still needs to happen.

4
src/main.c
View File

@ -295,8 +295,8 @@ int main(void) {
setup_io();
setup_clocks();
stdio_msp_init();
SFRIE1 = NMIIE;
SFRRPCR = SYSRSTRE__ENABLE | SYSRSTUP__PULLUP | SYSNMIIES__FALLING | SYSNMI__NMI;
//SFRIE1 = NMIIE;
//SFRRPCR = SYSRSTRE__ENABLE | SYSRSTUP__PULLUP | SYSNMIIES__FALLING | SYSNMI__NMI;
memset(regbak, 0, sizeof regbak);