ST25DV-i2c energy harvesting and GPO with stm32l031k6

WPARK.1 · ‎2022-12-19

Hello, I am trying to open a project that can turn on the low power MCU stm32l031 with ANT7-T-25DV64KC while turning high and low periodically for GPO pin of the MCU. I tried many different ways but still not done with any of them (steval code and using NFC4 and 7 provided by stm32cubeide).

Would you please suggest me for any reference or sample for St25DV-i2c?

WPARK.1 · ‎2023-01-30

Hello,

It is good news that after updating my cubeIde to 1.11.2. It is working now. Therefore, I modified EH project code to detach the BSP button and LEDs while it is always working in EH mode (Active boot).

For EH project, I have one more question. As you told me EH_mode is nonvolatile, if I already set ST25DVxxKC_EN_STATUS_E = ST25DVXXKC_ENABLE and ST25DVxxKC_EH_MODE_STATUS_E = ST25DVXXKC_EH_ACTIVE_AFTER_BOOT for my extension board ST25 chip, can I remove MX_NFC7_EH_Process (as in my case, I will not turn off EH function).

And for NDEF example, I have some questions.

It is very interesting that by this strcpy function, can directly change the payload length and set other headers. What is the URI_ID for MME (Text, in my RF430 code, I use 0x02, // URI header identifier). And furthermore, what is the difference between URI_Message and Information. It is a bit confused as I originally used TI chip for NFC.

In my case, I want to send ADC sensor values in TEXT format when I put my mobile phone to my ST25.

I will attach my RF430 NDEF format.

const u08_t NFC_NDEF_Message[57] = {

// Block 0

0xE1, // NDEF Magic Number

0x40, // Version Number, read/write access conditions

0x79, //0x7E, // 1008 bytes / 8 = 126 blocks

0x00,//0x04,//8 byte extended memory //0x00, // does not support read multiple blocks (limited to only 3 blocks)

// Block 1

0x03, // NDEF Message present

0x34, // Length , 17 bytes

0x91, // Record header

0x01, // type length

// Block 2

0x0E, // Payload length 14

0x54, // Record Type T (Text)

0x02, // URI header identifier

0x65, // 'e'

// Block 3

0x6E, // 'n'

0x54, // 'T'

0x65, // 'e'

0x6D, // 'm'

// Block 4

0x70, // 'p'

0x74, // 't'

0x75, // 'u'

0x72, // 'r'

// Block 5

0x65, // 'e'

0x3A, // ':'

0x00,

// Block 6

0x51, // Record header

0x01, // type length

0x0B, // Payload length 11

0x54, // Record Type T (Text)

// Block 7

0x02, // URI header identifier

0x65, // 'e'

0x6E, // 'n'

0x4E, // 'N'

// Block 8

0x48, // 'H'

0x34, // '4'

0x2B, // '+'

0x3A, // ':'

// Block 9

0x00, //

0x00,

0x51, // Record header

// Block 10

0x01, // type length

0x0A, // Payload length

0x54, // Record Type T (Text)

0x02, // URI header identifier

// Block 11

0x65, // 'e'

0x6E, // 'n'

0x43, // 'C'

0x6C, // 'l'

// Block 12

0x2D, // '-'

0x3A, // ':'

0x00, //

// Block 13

0x00, //

0xFE, // TLV terminator

0x00, // Empty don't care

0x00 // Empty don't care

};

Thank you for reading.

WPARK.1 · ‎2023-01-30

The problem is solved but, I still want your answers for the questions.

For EH project, I have one more question. As you told me EH_mode is nonvolatile, if I already set ST25DVxxKC_EN_STATUS_E = ST25DVXXKC_ENABLE and ST25DVxxKC_EH_MODE_STATUS_E = ST25DVXXKC_EH_ACTIVE_AFTER_BOOT for my extension board ST25 chip, can I remove MX_NFC7_EH_Process (as in my case, I will not turn off EH function).

And for NDEF example, I have some questions.

And furthermore, what is the difference between URI_Message and Information. It is a bit confused as I originally used TI chip for NFC.

Rene Lenerve · ‎2023-01-30

Hi @WPARK.1,

Great that you solved your issue, Happy for you.

For EH, if you have set the register to the value ST25DVXXKC_EH_ACTIVE_AFTER_BOOT, EH will be always active (when a field is present) until you modify this register. (please read the DataSheet of the ST25DV64KC to have more information on it and other features).

For NDEF, NDEF is a file format message described by the standard from NFC Forum specifications, it describes how data are organized in the memory. There are multiple formats defined by NFC Forum, URI is one to store URI information as for this example an URL (could be also phone number, email, ftp, ...). The field information is just additional information used for smart poster (it is an extended format that contains more fields not mandatory to store only an URL). For NDEF Text format you need to use another format than the URI, in the ndef lib you have a file named lib_NDEF_Text that allow you to build such messages. But it is recommended to read the standard or find some resources on google to learn more about NDEF format (This standard is used for applications with NFC but are not NFC spec).

I hope this can help you.

Kind Regards.