ruri-baka

What model and PCB revision hardware are you testing on?

I've been working on 0302 compatibility and here is what I have so far: unlock ui limits, extra debug, extra modes, and the gui config address need a +8 offset...

Lots..sitting in warehouses... By the way... Text Strings: not for use is at 1a5bo, the other two are the same. SHA256: A5E7D77FC7B2FE38DA82A7D99035CECD40749398DA31F7E39634C002E7081CC7

I just created a pull request with it; I'd be interested to see if what I did for the menus on 0302 would get them working on 0306 though.

Go for it; I didn't know who's working on what patcher so I figured I'd throw that up so I can take a break and start digging and debugging the...

Well that explains why I was going nuts over the trying to get the GUI to work, but the good news is that you should be able to enable the...

> I was able to disassemble the binary using: > > ``` > arm-none-eabi-objdump -D -bbinary -marm stm32.bin -Mforce-thumb > stm32.s > ``` > > Additionally, The Reko program was...

It ultimately has to do with how the GUI is compiled for certain sets of machines. The actual values though are still present. It should be possible to set the...

Have you taken a look at this? https://github.com/wormyrocks/airbreak/blob/master/tcl/airsense.cfg Looks like you have to go into the debug console, but I bet its prolly sysconfig or optionbytes

> 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...