For some reason I felt sorry for you and thought I'd help by letting you know not to bother with 32-bit checksums to help speed up things so I don't understand why you answered like you did, lesson learned I guess.
An example for anyone else worrying about 32-bit checksums. I've taken a Pascal VBIOS and modified it by changing 2 bytes in the legacy section (in one of those unsigned blob sections) so that the 8-bit checksum remains unchanged with the addition of those 2 bytes but the 32-bit checksum doesn't.
My answer was based on how you write. Everyone values your contributions.
Maybe its wrong for me to call it "checksum".
Every ID rebrand (strap) has small checksums
there are then main blob checksums
And there is a file integrity hash ontop.
Based on this foundation, then it is double signed and HMAC hashed for the newer series.
Ti's have one sig, non Ti's have double sig. You can read this out with binwalk (github).
I know that changing some bits which are unsigned flash on Pascal.
Changing bits that are signed, still flashes but driver refuses as card is reported as unsigned. ~ Code43
^ This functionality was then prevented on newer cards ~ newer falcon revision & its OS
Goal is not to cherry pick what is unsigned (although is interesting information where you can place edits to preserve file-integrity)
But goal is to flash an edited file with real edits, and later sign it.
Real goal.
First step is creating a file that is valid for falcon.
in the near future it is to sign your valid file created by an editor and give ability to work with RTX cards.
Fail 5 years ago was creating a file that will flash ~ because disabling Falcon is something we can forget
Sure the Tegra research was valuable and some old cards @ Falcon v4 can work.
But this has no future.
Modifying the driver so that your bootup (hard enough) unsigned card passes the driver check
Also is going thickhead against a brickwall. It has no future either.
It can work for a short time and publishing how also will work for a short time.
But that's not the goal. Its a big security risk, outside of trustloss.
Work with falcon not against it
Build your mods ontop of the foundation i give.
I see a chance and future success. Wouldn't have started it without any chance.
EDIT:
CID rebrands with signed files,
seems to be half a falcon half an nvflash issue.
At least the flash portion of it
I have to fix some things for the next update
(likely rewrite it fully once again, as eeprom access issue is a big one i can't just fix without changing approach
~ bug of my ISSI bypass for 2000 series affecting access of some other EEPROM versions // XUSB FW rebrand ability.
i'm such a novice . . .)
Then we have to see what can be done with the help of Falcon.
Nobody else can force that rebrand. HW-Mods can change falcon's outcome
But only falcon can help us. Work with it
EDIT2:
Here are 3-4 things which can help you/us for development
Sweetscape 010 Editor Nvidia VBios Templates. Contribute to ChairGraveyard/010-nvidia-vbios development by creating an account on GitHub.
github.com
A mixture of
https://github.com/dmlloyd/envytools/tree/master/hwdocs for example
https://github.com/envytools/envytools/blob/master/nvbios/bios.h //
https://github.com/envytools/envytools/blob/master/nvbios/p.c
And
Support of Nvidia Falcon processors for Ghidra. Contribute to marysaka/ghidra_falcon development by creating an account on GitHub.
github.com
A RISC-V ELF psABI Document. Contribute to riscv-non-isa/riscv-elf-psabi-doc development by creating an account on GitHub.
github.com
Low level runs as ELF files ~ RiscV
Nvidia still uses couple of opensource projects ~ but the OS and bits of the design are proprietary.
OhGodATeam's fork is sadly also incomplete
Dump of it, just lists this ~attached file~
This is rather what we want, at very least
But,
Copyleft by a friend~
Most of the interesting values, run in the legacy section of the Bios.
It wouldn't wonder me, if the swap to UEFI and BAR, forced the double bios and annoying signing requirement/behavior.
Sadly i can't create code, i can only modify code and exploit based on logic.
So i rely on you guys.
www.techpowerup.com
