Hi, again…

It’s the FOTA-guy back at it again. I have a new version of a custom board which powers the feather through vbat and with a cut jmp2. It is all working great, except FOTA. It doesnt apply the update when resetting. The only difference between this board and the previous fota-able ones are the power supply via vbat. Even though I remove batteries and use usb to flash it (it works to flash new firmware this way) the fota patch still isn’t applied. My guess is that it has something to do with the way it resets. Can anything be done about this or did I screw up?

Regards

Remind me what version of the nRF9160 Feather are you using? The bootloader is rejecting the update either due to flash layout constraints or an issue with the signing key (if you implemented one that is).

Can you tell if it boots up into the intended FOTA that you sent after update? Or not at all?

  • Nwre replied to this.

    jaredwolff Hi Jared!
    Any way to check what version it is without physically looking at the board? It is, well, encapsulated… It does not boot it at all. I’ve tried letting the fota procedure reset the device as well as me actually pressing the reset button. Do the partition addresses differ between feather versions?

    Thanks for taking the time

        Nwre Any way to check what version it is without physically looking at the board?

        The marking is on the bottom. There is no other way.

        Nwre Do the partition addresses differ between feather versions?

        It is possible if you had an older one they may be incompatible.

        • Nwre replied to this.

              jaredwolff

              Alright, I will try and get access to it and check the version. It should be a newer version and the ones I got that have FOTA working ought to be the older ones as there are a few years in between orders. If that is the case, how should I go about resolving the partitions?

                You will likely have to either update the newer one to match the older for vice versa. It will require creating a custom pm.yml and having access to a programmer and Tag Connect. How many older boards do you have and what versions are they?

                • Nwre replied to this.

                  jaredwolff I wish I could tell you, every feather board I have is soldered to another board and I can’t check the version. Do you have a pm.yml that I can try? I’m willing to try a gazillion of them if you have them

                      Nwre do you have access to the top of the board? (Specifically the tag connect footprint?) we could try to reprogram the bootloader on the older boards so they’re at least all the same.

                      Do you have a Tag Connect cable and DK?

                      • Nwre replied to this.

                          jaredwolff Sorry, I do not. I appreciate the help very much but I think I will be stuck here for a while. We are making another prototype out of a feather that has working FOTA, that will at least tell if the fault is due to battery power or versions of feathers. I have an SD-card available to all devices, it would be nice if that could hold the image but I guess that’s a tough thing to achieve.

                              Nwre understood. Unfortunately without access to the Tag Connect footprint, you won’t be able to address the problem. You may have any to rework your design so you have access in the future.

                                Terms and Conditions | Privacy Policy