Segger Embedded Studio(Crossworks). Write data to UICR.

RE: Segger Embedded Studio(Crossworks). Write data to UICR.

jfDEVmoto — Wed, 16 Aug 2017 10:42:22 GMT

fine, I did write "Keep" instead of "keep".... This did not raise any error but was not taken into account... However, I see that now, my hex file writes 8 bytes at 0x10001014 instead of just 4 when I used the "onlyfortEst" assignment. Might not be a big deal, but I can't understand this behavior, as the size of the section is 4

RE: Segger Embedded Studio(Crossworks). Write data to UICR.

jfDEVmoto — Tue, 15 Aug 2017 13:11:53 GMT

I got it but it does not seem to be effective on my side. I'll check again.

RE: Segger Embedded Studio(Crossworks). Write data to UICR.

Vladimir — Tue, 15 Aug 2017 10:03:40 GMT

Yes, see RK's comment to "answer" here.

Add: keep="Yes"

in the programsection and the linker script will have to keep option set in it.

RE: Segger Embedded Studio(Crossworks). Write data to UICR.

jfDEVmoto — Mon, 14 Aug 2017 21:11:51 GMT

Thanks for this thread, it did help me a lot. I still don't have a working dfu as I did with keil toolchain but at least bootloader starts and uicr is written. Have you found a way to get rid of the "onlyForTest" assignment ? I do have to use it to see my UICR section in hex file.

RE: Segger Embedded Studio(Crossworks). Write data to UICR.

RK — Tue, 07 Jun 2016 09:09:19 GMT

This file format is documented if you know where to look, there's quite a few options for those program sections and the other file formats are also documented.

www.rowleydownload.co.uk/.../index.htm

RE: Segger Embedded Studio(Crossworks). Write data to UICR.

Vladimir — Tue, 07 Jun 2016 09:04:05 GMT

Yes, that was the case. And with keep="Yes" I have all my options and don't have to use this weird uint32_t onlyForTest = m_uicr_bootloader_start; Thanks again, RK.

RE: Segger Embedded Studio(Crossworks). Write data to UICR.

RK — Tue, 07 Jun 2016 08:36:27 GMT

if that's the case then just add

keep="Yes"

in the programsection and the linker script will have the keep option set in it.

RE: Segger Embedded Studio(Crossworks). Write data to UICR.

Vladimir — Tue, 07 Jun 2016 08:11:02 GMT

It is looks like that compiler/linker doesn't care about "volatile" var and just remove it from code (all code optimizations set to none).

So at least at Segger Embedded Studio it is not enough to just declare

volatile static const uint32_t m_uicr_bootloader_start  __attribute__ ((section(".uicrBootStartAddress"))) = 0x55555555;

To see data at .uicrBootStartAddress section I have to use this m_uicr_bootloader_start variable somethere in code, something like:

int main(void)
{

uint32_t onlyForTest = m_uicr_bootloader_start;

...

}

After downloading this to chip I have at right address my 0x55555555:

C:\Program Files (x86)\Nordic Semiconductor\nrf5x\bin>nrfjprog.exe --memrd 0x10001014
0x10001014: 55555555                              |UUUU|

Strange, but I can live with it for now.

RE: Segger Embedded Studio(Crossworks). Write data to UICR.

RK — Mon, 06 Jun 2016 14:25:05 GMT

mine definitely shows up in the correct section. If the linker had removed it it wouldn't be there at all. SO none doesn't make sense and it not being in the file doesn't make sense. It seems for all the world like it's treating it like initialized data and expecting it to be copied at program start instead of readonly data which is in the flash file.

Take another look tomorrow and you may see it instantly.

RE: Segger Embedded Studio(Crossworks). Write data to UICR.

Vladimir — Mon, 06 Jun 2016 14:18:55 GMT

View->Symbol Browser - I see uicrBootStartAddress symbol. With right address, but in "information" option "Section" set to "none" (section that the symbol is defined in). Is that right to be "none" in that case?

So, at .map file I have uicrBootStartAddress with the right address, but at elf file there no data at that address. So somehow linker(?) decided remove it.

Tomorrow I'll think about it again. Thanks anyway, RK!

RE: Segger Embedded Studio(Crossworks). Write data to UICR.

RK — Mon, 06 Jun 2016 14:04:23 GMT

not much more to suggest at this point. Can't see an error, looks right to me and I have a couple of projects with UICR sections in them which I do that way.

Only thing left to try, View-> Symbol Browser and use the search to find where that symbol has been put, assuming it's not decided that it isn't used and just removed it .. but I don't recall having to tell it to keep the data explicitly.

RE: Segger Embedded Studio(Crossworks). Write data to UICR.

Vladimir — Mon, 06 Jun 2016 14:00:16 GMT

Elf file at the end has 0x00079690 - last data to be written to flash, and after that - 0x20002c00 - RAM. So nothing at UICR (0x10001014). I've changed $(FLASH_NAME:UICR) to "UICR", but in elf still no data for UICR address.

RE: Segger Embedded Studio(Crossworks). Write data to UICR.

RK — Mon, 06 Jun 2016 13:40:34 GMT

SES should have a viewer for ELF files if you double click on it, see if there's anything in the file at the address you used.

I just looked at one of my Crossworks (basically the same product) projects which has a UICR section, in fact it's just a UICR project and nothing else, I have this

const struct
{
	uint8_t	MAC_ADDRESS[6];
	char		PIN[6];
	uint32_t	RESET_CODE;
} RELAY_DATA  __attribute((section("uicr")))  = {
	.MAC_ADDRESS = { 0xff, 0xff, 0xff, 0xff, 0xff, 0xff },
	.PIN         = { '0', 0', '0', '0', '0', '0' },
	.RESET_CODE  = 0x12345678,
};

The name of the section in the flash_placement file should be "UICR", not $(FLASH_NAME:UICR). That uses the value of FLASH_NAME if it exists and 'UICR' if it doesn't. Using just UICR is better, although I don't think that's your problem.

RE: Segger Embedded Studio(Crossworks). Write data to UICR.

Vladimir — Mon, 06 Jun 2016 13:31:17 GMT

After adding "static const" still have same problem. As for elf file... actualy, have not read elf files before. As I understand it should has all programm sections/segments in it. My elf file looks like 99% binary data and couple of strings including my ".uicrBootStartAddress".

RE: Segger Embedded Studio(Crossworks). Write data to UICR.

RK — Mon, 06 Jun 2016 12:54:02 GMT

Don't think that's going to work. The variable declaration isn't constant so it'll have reserved space in the UICR expecting to copy the variable in at runtime I think, which isn't what you want.

Try making the variable static constant so it actually puts it in the file. Take a look at the ELF file as well.