2023-10-07 08:15 AM
Hi! We have designed our own custom board based on the X-NUCLEO-BNRG2A1, we bought the BLENRG-M2SP module some months ago. We discovered based on this, that these are coming empty (not flashed). We have flashed them using all the available images possible, for example the ones indicated in here, or the ones that you can download when reading UM3051 (DTM_Full.bin and/or DTM_LLOnly.bin). When we run our code in the X-NUCLEO-BNRG2A1 (together with the STM32 Nucleo-64 development board with STM32L476RG MCU --> the same MCU we have in our custom PCB), everything works properly. However, when we run our code in our PCB, the first frame we receive (SPI) after a BlueNRG-2 reset (RST line) is: {0x04,0xff,0x03,0x01,0x00,0x05} Note the last byte, which should be 0x01. After that, when we try to communicate again for example sending a reset command or asking for the fw and hw version, both end up in TIMEOUT. The only difference we have in our PCB with respect to the dev kit is that we are using 1.8V, the rest is the same. Thus, why cannot we communicate with the device? and I guess the 0x05 reasoning error code is related to that, right?
thanks!