is there any sample for X-NUCLEO-NFC08A1 to be used with NUCLEO-U083RC board

[Mihaita Ivascu]

Hello,

      I would like if anyone had to use X-NUCLEO-NFC08A1 expansion boards with NUCLEO-U083RC and could reuse successfully the examples for NFC08A1? I see there are a few, but for other MCUs

Thanks,

      Mihai

[Brian TIDAL]

Hi,

when using X-CUBE-NFC6, one can generate the polling demo and the NDEF demo for any NUCLEO-64 board. I would recommend to use this X-CUBE-NFC6 package and generate for NUCLEO-U083RC with STM32CubeMX.

Rgds

BT

[Mihaita Ivascu]

Hello,

    Thanks for the prompt answer.

    I have downloaded X-CUBE-NFC6 package and checked the contents.

    I did not figure out how to generate ndef for NUCLEO-U083RC

Thanks,

     Mihai

[Brian TIDAL]

Hi Mihai,

see STMicroelectronics.X-CUBE-NFC6_GettingStarted.pdf inside the STM32Cube\Repository\Packs\STMicroelectronics\X-CUBE-NFC6\3.1.0\Documentation folder. This provides step by step instructions.

Rgds

BT

[Mihaita Ivascu]

Yes I was able to generate it already. This is really helpful feature. thanks.

But although I select application it does not generate code for application(ndef demo for example). but it does so for BSP, drivers and all level. 

Thanks,

    Mihai

[Brian TIDAL]

Hi,

make sure to properly configure the components:

and then:

This should generate the NDEF application.

Rgds

BT

[Mihaita Ivascu]

Hello BT,

    I can generate the needed code in MX but when I import it in cubeIDE there are compilation issues. APIs are not the same even though are used one from another, for example:

void MX_NFC8_PollingTagDetectNDEF_Init(void)
{
   BSP_NFC0XCOMM_Init();
   BSP_COM_Init(COM1);

but declaration is:

#if (USE_BSP_COM_FEATURE > 0)
int32_t  BSP_COM_Init(COM_TypeDef COM, COM_InitTypeDef *COM_Init);
int32_t  BSP_COM_DeInit(COM_TypeDef COM);

so is not easy to integrate the generated code from MX

Best regards,

          Mihai

[Brian TIDAL · Accepted solution]

Hi Mihai,

On my side, no compilation issue:

Make sure to have the following configuration for the Bsp:

I've attached the ioc file that I have used. Just compare with your ioc.

Rgds

BT

[Mihaita Ivascu]

Hello BT,

    Yes, you are right SPI is by default use, for I2C hardware changes to the expansion board are needed.

    I knew that but somehow I generate it by mistake for I2C in the project I was referring.

   For the picture above I  have "No solution" for HAL_EXTI_DRIVER and BSP_COMMON_DRIVER(for USART).

   Am i missing some components to check in for CubeMX ?

Thanks,

      Mihai

[Mihaita Ivascu]

like this: