Vampyre wrote:I'll check the first fail msg and see what it says, other program sends 36 80 not 36 00. Wonder if that has anything to do with it
I think you are comparing opposite ends of the binary ...
I do not know the exact proper names, however,
36 00 is receive/write.
36 80 is receive/write and then execute what was just received/written, I believe (pretty sure) this must be the last packet ... not 100% sure, never tested myself.
Intelligence is in the details!
It is easier not to learn bad habits, then it is to break them!
If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
the other program loads the kernel in one upload hammer is trying to load it in sections.
nope antus the 7f code is first thing that pops up after code tries to upload.
found in the code where it mentions hard coding 91 5E, but it says using 80 00 and file length instead. Now ill try and figure out how to hard code 91 50.
really wish I hade a terminal to just straight send commands so I could test crap easier.
darkhorizon also got back to me and may have a test read kernel i can use and key algo set up so no more hard coding, he did let me know that hes pretty sure its algo 13 for the P04 v6 pcm
What happens if you move the load address back or forward a byte or two? Change the size of the file a byte or two larger or smaller? We'll be needing to make a kernel that talks pcmhammer protocol.
testing file size now antus so far 4096 is to much looks like the p04 doesnt like multi part upload for kernel, also hard coded it to 915E so once I max out size ill move back some
