Nikolas Britton

I tried completely overwriting my AirSense firmware with my AirCurve's firmware, however, the device still retains the old serial number and AirSense_10_AutoSet header in the Identification.tgt file. So this information...

I don't see anything significantly different within those dump files. For instance, optionsbytes.bin contains only a single address line that is different between the AirSense and AirCurve. Is it possible...

Hi, sorry no, I lost motivation because I had some major life changes take priority.

Few things to think about. 1) I noticed on my machine that if I didn't have all the JTAG wires connected (especially the ground wire) the machine would sporadically reboot...

I have an AirCurve 10 S on the way so I should be able to help with getting the differential. Not sure what version of the firmware it has on...

``` % diff -U0 stm32.bin.AirSense_10_AutoSet_0306.DAT_08008584 stm32.bin.AirCurve_10_S_0306.DAT_08008584 --- stm32.bin.AirSense_10_AutoSet_0306.DAT_08008584 2020-05-09 14:39:28.000000000 -0500 +++ stm32.bin.AirCurve_10_S_0306.DAT_08008584 2020-05-09 14:37:47.000000000 -0500 @@ -10 +10 @@ - 0800858c 01 ?? 01h + 0800858c 03 ?? 03h...

Yeah I think you could be right. 08008590 is a data block referenced by a pointer located at 08004128, and PTR_DAT_08004108 is referenced by FUN_08004100:08004100 which returns the pointer data....

Ok cool, I didn't realize those were intentional, I just thought it was some gibberish buffer overflow or something. I'm a principal computer systems engineer but this project isn't anywhere...

It seems an extra library is required, located here: https://github.com/ntfreak/openocd/blob/master/tcl/mem_helper.tcl wget https://raw.githubusercontent.com/ntfreak/openocd/master/tcl/mem_helper.tcl;

Well presumably the digital electronics are just sending PWM signals to the blower motor, so I would expect it to ether stop entirely or just keep sending the same signal....