Murata LoRa SOC bootloader

Are your custom board and the Discovery using the same MCU type ?

Are the LEDs you try to blink on the same pin(s) ?

Are the clock source (quartz, frequency) the same ?

I reckon this must be because the ICs aren't shipped with bootloader?

If you mean the system bootloader (entered via BOOT0/BOOT1), no.

This bootloader is in ROM, and always present.

I don't know any Discovery kit that uses a second-stage bootloader.

But if your LoRa SoC has such a second stage BL, it most probably conflichts with your test application.

I would try a JTAG/SWD adaptor (like STLink) to flash, and a toolchain.

SARTHAK KELAPURE wrote:

I have a Murata LoRa SOC

You mean the 'Type ABZ' module:

https://wireless.murata.com/eng/products/rf-modules-1/lpwa/type-abz.html

https://wireless.murata.com/media/catalog/product/cache/3/image/9df78eab33525d08d6e5fb8d27136e95/t/y/typeabz.jpg

Note that this is not a SoC; it is an

STM32L072 microcontroller and a Semtech SX1276 Radio - two separate chips.

Sorry - I can't see the rest of your text due to the forum faults.

In another post you indicate the lack of SWD (SWCLK,SWDIO), hopefully you have at least test points or edge castellations where you can access these signals, otherwise your design is going to be a bit of a bear to debug and bring up.

The BOOT0 high configuration seems to get you into the loader. In normal operation this should be pulled low. You should also be able to read out the code written to confirm the correct delivery.

You will need to simplify your test code so you can see how far beyond Reset_Handler you get. You should perhaps just let the part run of the initial clock rather than change them or enable the PLL.

I might start by adding code into the Reset_Handler to enable a GPIO clock, and a GPIO pin, and then toggle that in a way I can scope to prove the part is alive, and that my code can run. Once you have done that look for code that sticks in spin loops or bombs silently into Error_Handler(), etc.