Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatically determine TXU size from ROM #393

Open
pixelherodev opened this issue Feb 17, 2020 · 6 comments
Open

Automatically determine TXU size from ROM #393

pixelherodev opened this issue Feb 17, 2020 · 6 comments

Comments

@pixelherodev
Copy link

This requires a bit of careful thought, as it's not as simple as checking for zeroes.

@aviallon
Copy link
Member

Is the number of pages dependant on the ROM size ?

@pixelherodev
Copy link
Author

Sorta.

ROMs include every single page, but TI upgrade files only include the ones you explicitly specify. If we specify every page, then uploads will take an enormous amount of time literally just writing zeroes. If we miss a page (as is sometimes the case now), then it results in missing data and bugs.

@aviallon
Copy link
Member

Oh. So how do I tell to send every page then ? For debugging purposes.

@pixelherodev
Copy link
Author

KnightOS/KnightOS's makefile has this:

       	mktiupgrade -p -s exploit/signature.bin -d $(PLATFORM) -n $(KEY) $(OUT)KnightOS-$(PLATFORM).rom \
				$(OUT)KnightOS-$(PLATFORM).$(UPGRADEEXT) 00 01 02 03 04 05 06 07 08 $(PRIVILEGED) $(EXPLOIT_PAGES);\
	

Basically, just add 09 0A 0B 0C... etc after 08.

(sorry for the delay, I somehow missed this)

@pixelherodev
Copy link
Author

Note: genkfs appears to print out the page list.

@pixelherodev pixelherodev reopened this Oct 12, 2020
@pixelherodev pixelherodev removed this from the Kernel 0.7.0 milestone Oct 14, 2020
@pixelherodev
Copy link
Author

Current planned path: add a flag to genkfs that causes it to print the full list of needed pages to a file in .knightos, and read that in the Makefile to generate the mktiupgrade command line.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants