X-NUCLEO-IDB05A1

[chaitanya jasti]

Posted on March 07, 2017 at 11:48

Hi 

We are using X-NUCLEO-IDB05A1. Why EEPROM is used in the board.

[Nesrine M_O]

Posted on March 07, 2017 at 12:13

Hi

jasti.chaitanya

,

The

http://www.st.com/content/st_com/en/products/ecosystems/stm32-open-development-environment/stm32-nucleo-expansion-boards/stm32-ode-connect-hw/x-nucleo-idb05a1.html

is a Bluetooth Low Energy evaluation board based on BlueNRG-MS RF module,SPBTLE-RF, to allow expansion of the STM32 Nucleo boards.

The board has the following features:

• On-board SPBTLE-RF module based on the BlueNRG-MS single mode BLE network processor
• SPI EEPROM for parameter saving
• Jumper at 3V3 for checking the current consumption of STM32 expansion board

please refer to

http://www.st.com/content/ccc/resource/technical/document/user_manual/group0/32/90/61/05/d1/7d/45/d8/DM00210197/files/DM00210pdf/jcr:content/translations/en.DM00210pdf

about getting started with X-NUCLEO-IDB05A1 BLE expansion board

-Nesrine-

[chaitanya jasti]

Posted on March 07, 2017 at 12:30

• SPI EEPROM for parameter saving

But EEPROM is controlled by STM32 and how it is useful for BLE module.

[Nesrine M_O]

Posted on March 07, 2017 at 13:39

The

EEPROM

can be used to store the configuration parameters related to applications or settings of the SPBTLE-RF module

[Ulian Shahnovich]

Posted on September 09, 2017 at 01:27

Since the eeprom is on the expansion board, the question about its necessity is automatically rising. 

Of course, this is a dev board and we can use or not the peripherals based on the application needs.

Of course we can use the eeprom to store any kind of data (not only re to Bluetooth) during the life time of the app..

We can use the embedded registers for the same propose as well (if there are left unused).. 

So, the question is the following: is the eeprom is a necessary unit for basic bluetooth communication?

[richard orengo]

Posted on November 14, 2017 at 11:20

Hi, maybe someone know..

I am testing EEPROM with a nucleo F302R8 spi2 port. I have weird behaviour on receive sometimes 0x00, sometimes 0xFF (something is floating ...?). Is the module totally hardware compatible with nucleof302r8 ? I see optional on xnucleo datasheet 'SPI and GPIO connection options' PA5 (SPI_CLK) has optionnal configuration. It is necessary to change something to hardware or i need only to look at GPIO configiuration side

[richard orengo]

Posted on November 14, 2017 at 12:45

I answer by myself. It seems harware pathc is necessary as described here:

https://os.mbed.com/teams/ST/code/X_NUCLEO_IDB0XA1/