[ot][spam][crazy] The Trials of Controlling a Programmer

Undiscussed Horrific Abuse, One Victim of Many gmkarl at gmail.com
Mon Mar 28 13:46:34 PDT 2022


Mysteries That Could Be Solved

I have two firmwares. The official release from many years ago, and the new
code I'm porting from recent months.

I've modified both of them to run the exact same assembler on boot.
However, the addresses the entry point jumps to find it are different, due
to different rom layouts from other code that would be run later.

The old official code functions.
The newer ported code does nothing.

I've visually inspected the assembler and the bytecode, and they appear
bit-for-bit identical to me, aside from the initial jump instruction.

It is completely possible to troubleshoot the issue, by finding what set of
changes from the working bytes, to the failing bytes, trigger the failure.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/html
Size: 1005 bytes
Desc: not available
URL: <https://lists.cpunks.org/pipermail/cypherpunks/attachments/20220328/590501f4/attachment.txt>


More information about the cypherpunks mailing list