so erase entire SRAM means Koko cycle doesn't write to param block & is virtually the same as a reset/boot that initializes the SRAM & reads param block afresh like a power up would?
antus wrote: Fri Jul 31, 2026 12:50 pm
Seem to have param block sorted, just erase sram on kernel load. challenge is arbitary code execution on slave. But can write it without, just can implement read.
Not sure what a Koko cycle is, but yes it seems to work. Though thats with my kernel, not the factory boot loader, not sure if I can clear the sram through the bootloader, so thats still something to look at and solve. I feel like the user needs the option to use my kernel or the factory method. Mine can write boot loader, but not slave, and bootloader method can do slave but not the boot sector. The tool could look at what it needs to do and even use both kernels but its more complicated than I like. Manual selection probably overcomplicates the tool for users. No other tool has options like that and it would surely going to create some WTF moments for people who just have a file and want to click a write button to flash it to their PCM.
I think I understand why we may not be able to program between generations. The boot loaders are not designed to be user updateable. The are set at factory and that is it. We can now program the factory bootloader with the pcmhammer kernel, but the slave write process also programs with the slave boot sector, which is not readable and not writable as we cant write it from another source. So if the boot to OS API is incompatible between generations, then we cant change the slave, so we cant match the master, and there is the problem. So now testing this on the bench, see if we reach this outcome, or if it can be programmed and work.
@MPC001 the E38 slave diagram from usbjtagnt shows this. Did you only require the 3 connections on the slave diagram, or did you need to keep the others from the master side connected also and just move reset across? Havnt needed to BDM slave yet, but it's much easier to only do these 3 if I need it in the next round of testing/recovery.
You do not have the required permissions to view the files attached to this post.
so erase entire SRAM means Koko cycle doesn't write to param block & is virtually the same as a reset/boot that initializes the SRAM & reads param block afresh like a power up would? 
