See below for updates.

IF YOU BREAK YOUR BOOT0 PIN. DO NOT DM ME ASKING FOR HELP. THAT'S IT. YOU BREAK THAT PIN AND YOU CANT FLASH. YOUR CHIP IS STUCK WITH WHATEVER HWFLY PUT ON IT


Pre-requisites:

---

• Raspberry Pi Zero W
  • You may use another flasher if you desire.
• Pinout Diagram
• Modchip Diagram
• FULL_CHIP_STOCK.bin
• Modchip Diagram, find the PA9(TX) and the PA10(RX) pins on your modchip, and do the following:
  • Connect GPIO14(TX) on your Raspberry Pi Zero W to the PA10(RX) pin on your modchip.
  • Connect GPIO15(RX) on your Raspberry Pi Zero W to the PA9(TX) pin on your modchip.

1. Solder a wire to each of the following pinouts on the Raspberry Pi Zero W:
   • 3.3V
   • Ground
   • GPIO 14 (UART TX)
   • GPIO 15 (UART RX)
2. Do the following to prepare the modchip:
   1. Lift pin 44 (also known as BOOT0).
   2. You will need a way to power the chip, so you need to find two 3.3v points. It can be on a MOSFET, but it will differ based on the revision of the modchip.
   3. Connect Ground on your Raspberry Pi Zero W to the Ground pin on your modchip.
   4. Check the Modchip Diagram, find the PA9(TX) and the PA10(RX) pins on your modchip, and do the following:
      • Connect GPIO14(TX) on your Raspberry Pi Zero W to the PA10(RX) pin on your modchip.
      • Connect GPIO15(RX) on your Raspberry Pi Zero W to the PA9(TX) pin on your modchip.
3. Boot your Raspberry Pi Zero W and do the following:
   1. In the terminal, type the following command, and press enter:
      

      sudo nano /boot/config.txt

   2. Add the following line to the end of the file:
      

      dtoverlay=pi3-miniuart-bt

   3. Press CTRL + X to save and exit the editor.
   4. In the terminal, type the following command, and press enter:
      

      sudo nano /boot/cmdline.txt

   5. Remove the following line from the file:
      

      console=serial0,115200

   6. Press CTRL + X to save and exit the editor.
   7. Restart your Raspberry Pi with this command
      

      sudo /sbin/reboot

   8. In the terminal, type the following commands, and press enter after each command:
      
      

      git clone https://github.com/Pheeeeenom/stm32flash.git
      cd stm32flash
      sudo make install

4. Now you will flash the modchip.
   Note: This will remove read protection, and the modchip will wipe itself (that is what we want).
   1. In the terminal, type the following command, and press enter:
      

      stm32flash -k /dev/serial0

   2. Now to flash Spacecraft-NX Version 0.2.0, type the following, and press enter:
      

      stm32flash -v -w ./FULL_CHIP_STOCK.bin /dev/serial0

5. Once you're done flashing your modchip, remove the wiring from the modchip, and restore the 3.3v pin on the modchip to its original position.

Please post pictures of your work here to further the identification of the different board revisions!


UPDATE: So it seems like stitching the spacecraft bootloader and firmware together from the repo causes unstable glitching behaviors. For now, consistent glitching behavior works with this bootload/firmware combo. This is the original file on the OLED variant chip which has 0.2.0 spacecraft. As for glitching, I'll figure it out, give me some time...unless someone else wants to hop in and reverse the differences.

For now, this at least solves the 0.1.0 HWFLY gen 3 issue. More to come.

UPDATE 2: This is only going to work on some HWFLY chips. Older ones use higher protection than the new revisions that seem to use the QFN FPGA.

UPDATE 3: This should fully work on OLED modchips with the QFN FPGA. https://github.com/Pheeeeenom/firmware

 

[doom95]

vol+ to skip deep sleep only works after sdloader.enc is flashed

 

[xdMatthewbx]

vol+ to skip deep sleep only works after sdloader.enc is flashed

Yes, that's what I was saying.

 

[Dean_]

I have a question.
on mena's 0.4.0 or hwflyboi's 0.5.0, do I need to remove sd card to use 'boot to ofw' function?

 

[xdMatthewbx]

I have a question.
on mena's 0.4.0 or hwflyboi's 0.5.0, do I need to remove sd card to use 'boot to ofw' function?

Shouldn't

 

[Dean_]

Shouldn't

I mean, on 0.4.0's NO SD screen (which shows 'failed to init SD card'), you can boot to ofw by pressing VOL+ and VOL- at the same time.
My question is that whether you can do this without removing sd card or not.

 

[lufeig]

It only works without sd card inserted

 

[doom95]

that's intentional. you want ofw, it's 2 taps from hekate. much simpler than removing sd. boot to ofw is a last resort option, not a feature

 

[fragged]

that's intentional. you want ofw, it's 2 taps from hekate. much simpler than removing sd. boot to ofw is a last resort option, not a feature

If you're dual booting OFW for online & CFW holding Vol + while powering on is the best feature for me. I've got an SX Lite so I can only use a modified version of r022.

 

[xdMatthewbx]

If you're dual booting OFW for online & CFW holding Vol + while powering on is the best feature for me. I've got an SX Lite so I can only use a modified version of r022.

Or you can just autoboot Hekate and have sysMMC and emuMMC boot options. Do you autoboot Atmosphere or something? You can even set Hekate to autoboot Atmosphere and hold VOL+ to show the Hekate menu instead, from which you can select sysMMC or emuMMC. Works on any firmware that actually boots a payload, doesn't need to be part of the chip firmware.

EDIT: VOL-, not VOL+

 

[fragged]

Or you can just autoboot Hekate and have sysMMC and emuMMC boot options. Do you autoboot Atmosphere or something? You can even set Hekate to autoboot Atmosphere and hold VOL+ to show the Hekate menu instead, from which you can select sysMMC or emuMMC. Works on any firmware that actually boots a payload, doesn't need to be part of the chip firmware.

EDIT: VOL-, not VOL+

I use Atmosphere emummc which I have set to auto boot, I don't use Hekate nearly that often so I prefer to have that just boot & hold Vol + to boot OFW when I want to. I switch between the two fairly often so it's the most convenient for me. And obviously use Vol - on the rare occasions I need to use Hekate.

 

[kylum]

I use Atmosphere emummc which I have set to auto boot, I don't use Hekate nearly that often so I prefer to have that just boot & hold Vol + to boot OFW when I want to. I switch between the two fairly often so it's the most convenient for me. And obviously use Vol - on the rare occasions I need to use Hekate.

I would have to agree with this. Ideal for me would be:
1. Hold Vol- during power on = disable Hwfly allowing OFW(not through hekate)
2. Tap Vol- during boot = hekate if autoboot enabled
3. Hold vol+ during power on = Hwfly toolbox functionality (hekate autoboot disabled)
4. No button press = whatever you have hekate autoboot to load or just hekate

We would only need the creator of 0.5.0 or @Mena to add number 1 functionality to their firmware if at all possible and their willingness to do so of course!

 

[doom95]

sorry, you will not find such willingness

 

[Magatame]

Does anyone in the UK do installs? I'm too shaky with a solder.

 

[Magatame]

Does anyone in the UK do installs? I'm too shaky with a solder.

 

[FruithatMods]

Does anyone in the UK do installs? I'm too shaky with a solder.

I do mod installations but from within the EU. I am not sure what the declaration process is like but if you were to find out how to declare the shipment so neither one of us gets charged any tariffs I would be happy to perform the mod for you.

 

[ViOTeK]

Hoping someone has an insight into a new problem I'm having; I have one of the early first batch new 6 wire OLED chips, where it turns to a red LED when connected to USB, so I ordered a ST-LINK v2 programmer and followed Sthetix's guide on flashing it. The programming of the chip goes smoothly, however, when I power the modchip on afterwards, I get a brief yellow LED flash, and then a solid white. I'm just testing this on a bench currently so it's not installed, what I'm wondering if anyone knows if this behavior is normal until it's installed and goes through the learning phase. I was hoping I would see the yellow LED and be able to connect via putty, but cannot. I've tried a few different bootloader+firmware combo bin files to no avail. I can see what happens with it installed in a few days, but was hoping someone out there might have run into this already.

 

[fragged]

Hoping someone has an insight into a new problem I'm having; I have one of the early first batch new 6 wire OLED chips, where it turns to a red LED when connected to USB, so I ordered a ST-LINK v2 programmer and followed Sthetix's guide on flashing it. The programming of the chip goes smoothly, however, when I power the modchip on afterwards, I get a brief yellow LED flash, and then a solid white. I'm just testing this on a bench currently so it's not installed, what I'm wondering if anyone knows if this behavior is normal until it's installed and goes through the learning phase. I was hoping I would see the yellow LED and be able to connect via putty, but cannot. I've tried a few different bootloader+firmware combo bin files to no avail. I can see what happens with it installed in a few days, but was hoping someone out there might have run into this already.

Don't some of the OLED chips not have a working USB connection? I've heard some of them also lose the ability to update over USB after a certian newer firmware is flashed to them, though the ST-Link should be able to flash the chip. Make sure you are stitching the Bootloader & Firmware files together into one file with a hex editor and are flashing that combined file.

 

[FR0ZN]

When I connect my OLED modchip to the PC, I can see the LED glow yellow and red at the same time (or is it green and red? I made a picture and it shows up as solid yellow).
The PC recognizes it as a DFU device.

Anyone know what to do? I try to flash it with 0.5.0 before the installation.

 

[doom95]

sounds like it's training. wait and it'll boot

 

[FR0ZN]

sounds like it's training. wait and it'll boot

It's not pulsing - and it's not installed