Hello,
Not so long ago I asked this question and the solution I was given is still working for the devices I was using.
Now I've received a new version of the device in which the only difference is that the only LED light now has PWM. So I modified my code to take advantage of that.
Naturally I want to flash the bootloader, softdevice and firmware so I used the script I was using from my previous question. And I'm having some different issues from what I had when I asked that. I've searched through the forums and found this other question that pretty much is the same issue I'm having.
What I'm seeing is that after flashing following my script:
I'm stuck at the dfu bootloader since using the nrfConnect Android app I'm only seeing my device as DfuTarg.
If I connect to the dfuTarg and try to upload the firmware via dfu, the process completes but it's still stuck in the dfu bootloader.
So before going to the question I found that resembles my problem, I decided to try to flash this PWM version of my firmware to one of my old devices without the pwm module knowing that the LED light might not work. And this works fine (the light doesn't as expected), I don't see the device as DfuTarg, I see it with the custom name I give it in the firmware.
So now I'm going back to one of my newest boards with PWM. I decided to try the steps given in the comments from that question.
1. I see that the P0.21 is the reset pin, so I removed the following I had in my code. Because I see that I have CONFIG_GPIO_AS_PINRESET set in the configuration.
Doing this did not ressolve my problem.
2. This is the comment marked as a solution to the question. I couldn't find the "flash_uc.h" the answer mentions, but in the linker options of my firmware, bootloader and what mentions the bootloader settings page I see the following addresses:
Firmware:
Bootloader:
Bootloader settings page:
Now I see that the bootloader and the bootloader settings page are pretty close.
If I add the Bootloader start and size I end up with 0x0007E000. So I don't think these two are colliding.
But if I add the firmware start and size I end up with 0x00080000, which I think it could be overlapping the bootloader and its settings.
Is this thought process correct? How can I solve this?
Thanks,
Pau