5 years, 9 months ago.

"Pinmap not found for peripheral" error with X_NUCLEO_IDB0XA1 library on NUCLEO-F767ZI

I'm trying to run an X-NUCLEO-IDB05A1 Bluetooth BLE board on a NUCLEO-F767ZI and I keep getting the "Pinmap not found for peripheral" error whenever the X_NUCLEO_IDB0XA1 library is loaded within a project. I have tried loading and running the "BlueNRG-MS-Stack-Updater" project (checking the "Update all libraries to the latest revision" box when importing the project into the online compiler workspace) and it compiles and loads without issue but returns the following runtime error in the console:

++ MbedOS Error Info ++
Error Status: 0x80010130 Code: 304 Module: 1
Error Message: pinmap not found for peripheral
Location: 0x800c3c3
Error Value: 0xffffffff
Current Thread: Id: 0x2b968352 Entry: 0x7958e54 StackSize: 0x2c2e55e1 StackMem: 0xea6ca962 SP: 0xc729c80
-- MbedOS Error Info --

I've also tried creating a new project based on the "A small example of TCP server over ethernet for mbed-os" template. The project builds and runs perfectly until I import the X_NUCLEO_IDB0XA1 library; no changes were made to the source code and it still compiles without errors but running it just outputs the "Pinmap not found for peripheral" message and terminates. If I remove the library from the project (again without any source code changes) the project then runs without issue again, so it does seem the problem is with the library itself on this platform.

The library status shows as 'Synced' and the library revision is 307:fa98703. Is there any way to decode the "Error Status: 0x80010130" code in the console message to determine what pin or peripheral is failing to map, so I at least have a clue what to search for in the library code?

1 Answer

5 years, 9 months ago.

Hello Dave,

One user may have had a similar issue that they seemed to have solved referencing this github issue: https://github.com/ARMmbed/mbed-os/issues/3541

One of the main issues centers around using either the D3 or D13 pin to drive the SPI clock. Based on the pin configurations here, the Nucleo-F767ZI has an SPI_SCLK connected to D13 rather than the default D3.

Can you take a look and see if it helps with your issue? Let us know if you have any more questions!

-Karen, team Mbed

If this solved your question, please make sure to click the "Thanks" link below!