I need help with the BlueNRG-2 unique device serial number. All the numbers are FF.

dallas48

I need help with the BlueNRG-2 unique device serial number. All the numbers are FF. [Copy link]

 

 Please advise: As the title says, the Unique device serial number of BlueNRG-2 is all FF when read out. Is the unique code here written by myself?

littleshrimp

The unique id is generally said to be globally unique, so you don't need to write it yourself. Otherwise, what difference does it make if you have it or not?

littleshrimp

littleshrimp posted on 2017-12-15 01:19 Usually, unique ids are claimed to be globally unique, so you don't need to write them yourself. Otherwise, what difference does it make whether you have it or not?

Which address did you read? Or post the code to see it. Unique device serial number The BlueNRG-2 device has a unique six-byte serial number stored at address 0x100007F4: it is stored as two words (8 bytes) at addresses 0x100007F4 and 0x100007F8 with unique serial number padded with 0xAA55.

dallas48

littleshrimp posted on 2017-12-15 01:20 Which address did you read or post the code to see Unique device serial number The BlueNRG-2 device has a uni ...

This is the code void flash_read_mac(void) { uint32_t mac_24bits_ieee, mac_24bits_com, i; uint8_t mac[6]; mac_24bits_ieee = *(volatile int *)(0x100007F4); mac_24bits_com = *(volatile int *)(0x100007F4 + 4); for (i = 0; i < 4; i++) { mac = (uint8_t)(mac_24bits_ieee >> 8 * i); } for (i = 0; i < 2; i++) { mac[i+4] = (uint8_t)(mac_24bits_com >> 8 * i); } PRINTF("##---[%X] [%X] ----- ", mac_24bits_ieee, mac_24bits_com); for(i=0; i<6; i++) PRINTF("%02X ", mac); PRINTF("\r\n"); }

littleshrimp

dallas48 posted on 2017-12-21 15:36 This is the code void flash_read_mac(void) { uint32_t mac_24bits_ieee, mac_24bits_com, i; ...

Try accessing the address 0x100007F4 directly in debug mode My device is BlueNRG-1, and I can read the corresponding data

dallas48

littleshrimp posted on 2017-12-21 16:00 Try accessing the address 0x100007F4 directly in debug mode. Mine is BlueNRG-1 and I can read the corresponding data.

I can read NRG-1 normally but NRG-2 is all F

dallas48

littleshrimp posted on 2017-12-21 16:00 Try accessing the address 0x100007F4 directly in debug mode. My device is BlueNRG-1 and I can read the corresponding data.

By the way, how do I call the debug memory map? It is always gray and unavailable when I debug.

littleshrimp

dallas48 posted on 2017-12-21 16:45 I read that NRG-1 is also normal but NRG-2 is all F

I compared the manuals of bluenrg-1 and bluenrg-2, but did not find any special instructions on the Unique device serial number. I also did not find the corresponding information on the Internet. I do not have a bluenrg-2 board and cannot help you test it. You can ask the ST engineer or @nmg administrator and ask him to help.

nmg

littleshrimp posted on 2017-12-21 17:16 I compared the manuals of bluenrg-1 and bluenrg-2, but didn't find any special instructions on the unique device serial number, and I didn't find any on the Internet...

Haha, please help send an email, and wait for feedback from the lovely engineers of ST

littleshrimp

nmg posted on 2017-12-21 17:55 Haha, please help send an email and wait for feedback from the lovely engineers of ST

dallas48

nmg posted on 2017-12-21 17:55 Haha, please help send an email and wait for feedback from the lovely engineers of ST

Thank you very much~

dallas48

littleshrimp posted on 2017-12-21 18:08

Thanks~~~

melau

I guess the BlueNRG-2 hardware version is an engineering sample. I also had the BlueNRG-1 hardware read FF, and the later hardware versions were normal.

saystar

The above answer is correct. The poster probably got an early sample of BlueNRG-2, which is an engineering sample and therefore does not have a unique ID. Normal chips will be the same as BlueNRG-1 and there is no need to worry about this problem. The poster can define an address in the code as an alternative for development and debugging.

saystar

dallas48 posted on 2017-12-21 16:46 By the way, how to call the debug memory map? It is always gray and unavailable when I debug

Which compiler did you use? In IAR, just open memory under the View menu.

dallas48

saystar posted on 2017-12-22 17:08 The above answer is correct. The poster should have got an early sample of BlueNRG-2, which is an engineering sample, so there is no unique ID. Normal samples will be the same as BlueNRG-2...

This is how it is done now

dallas48

melau posted on 2017-12-22 12:14 I guess the BlueNRG-2 hardware version is an engineering sample or something like that. I also had the BlueNRG-1 hardware version read FF, and the later hardware version...

It seems that this is the reason