Raspberry Pi HowTo #37
Comments
|
Thanks to your pics, I was able to troubleshoot the issue with my hardware setup and able to dump the bin file. |
|
Is there any chance that this can be added to the wiki? |
|
Hi Nikolas, My name is Dave Lattimore and I saw you Post on the apnea boards about enabling ASV. I had the thread bookmarked but they removed the post. Guess someone didn't like the idea of an AirBreak :-). I was going to private message you to see if there are any issues with missing ASV data structures but I don't have you logon id. My "apnea board" and "cpaptalk" id is sosotired. My email is [email protected]. Please get in touch. |
|
For any future hackers that come across this and are using a RasPi B version one, like me, you’ll need to do the following: Wire your serial clock line to the SPI0 sclk pin GPIO11, data to GPIO25, reset to GPIO24. Modify /usr/share/openocd/scripts/interface/raspberrypi-native.cfg Uncomment the two lines Modify the rasp-pi.cfg to source the raspberrypi-native.cfg rather than raspberrypi2-native.cfg The rest works the same. I successfully dumped and flashed the 0306 image from both a cpap and an autoset version of the Airsense 10 with this config (and verified that they are interchangeable). |
Cool thanks! So did your flash with 0306 go smoothly without any issues? |
Yes, I flashed the Autoset stock image and the unlocked/modified image onto the base model CPAP machine with this. Both worked perfectly, and I've been using that machine daily in Autoset mode for about 4 months. |
Hi, I am trying to airbreak my Airsense 10 CPAP elite with a raspberry pi 4 as the programmer. I follower your instructions but I cant seem to get it to work properly. It connects to the uC but won't dump the firmware and keeps giving errors. Could you please assist? Kind regards, root@raspberrypi:/home/pi/airbreak# sudo openocd -f tcl/rasp-pi.cfg -f tcl/airsense.cfg Info : Listening on port 6666 for tcl connections |
|
This is the error I get when I try dump the firmware... Please someone assist, been trying for 2 days straight... root@raspberrypi:/home/pi/airbreak# telnet localhost 4444
SWD DPIDR 0x2ba01477 |
Disclaimer: I am far, far from any kind of expert here. This was my first time trying to talk to any kind of STM microcontroller You definitely don’t want to follow my instructions with a Pi 4, but you may need to do what I did. I looked up the port/pin assignments for my version one Pi compared to the instructions that were written for a Pi 2/3, and made those adjustments so that it was using the same port functions, just on different pins. I would guess that the original instructions are probably closer to what you need than mine, since mine are adapted for a much earlier revision of the Pi hardware. It took me a few days of hacking at it and taking breaks before I figured it out, so you’re not the only one to struggle with it. I had actually ordered a USB programmer and it was in the mail when I finally figured it out, so worst case scenario you can throw in the towel and spend an extra $10 or so to get it done. |
Thanks so much for the reply, I really appreciate it. On a different note, this is what I get when I use dump_all, seems to fail at the same place...
Thanks so much for your feedback, good to know its not just me struggling. |
|
The dump process will be the same regardless of version - the difference comes in with the actual patching, since the key pieces of data that need to be flipped around will be at different offsets in the file - I think there’s a patch or a fork out there with a file that contains the correct offsets for your firmware, but don’t quote me on that - it’s been quite a while since I worked on this. I do have a Pi 400, which afaik, has the same pin out as the Pi 4, so if I have a need to take one of my machines apart, I may fire it up and take a crack at it. If I have any luck, I’ll post here again with whatever worked. |
Cool, thanks so much. If I manage to get it working I will add details to this thread to hopefully help the next person. At the moment I’m thinking it is protection bits or something along those lines preventing me from reading that location. The error “could not find MEM-AP to control the core” is also a little concerning 🙈 |
Feel free to use these pictures in the official documentation, I release them into the public domain. The only image I don't own is the R-Pi pinout diagram, that was sourced from Adafruit.
Ubuntu 20.04 Raspberry Pi 3 Image Download Link: https://ubuntu.com/download/raspberry-pi/thank-you?version=20.04&architecture=armhf+raspi
The text was updated successfully, but these errors were encountered: