Does anyone know if the macro ZWORLD_RESERVED_SIZE is automatically utilized by the userblock functions to prevent you from overwriting the ADC calibration data? There are lots of notes saying to note the location, and the macro assists with that. But now should I use addresses higher than ZWORLD_RESERVED_SIZE? Or does the offset address of 0 already take care of that?
Reading the source, I’d say it doesn’t take it into account, but then the sample programs would be overwriting that data on boards like the 3400.
Thank you,
-Patrick
if you can use more space in user block, you can use the Write_idblock.c program, and change the NUMUSER4KBLOCKS…
but take care with the other items…
I have a similar question. I am using an RCM3700 setup. I would like to use readUserBlock(void *dest, unsigned addr, unsigned numbytes) and writeUserBlock(unsigned addr, void *source, unsigned numbytes) to store static information, such as calibration constants.
Edit: I looked through Write_idblock.c, but it uses memcpy and xmem functions not UserBlock functions.
, I did run idblock_report.c and got the following information idBlockSize = 0x00000084 bytes
userBlockSize=0x3F7C (which happens to be 0x4000-0x0084)
ID+User Blocks area top address = 0x00080000
User block image A address = 0x0007C000
User block image A is valid.
does this mean that for the two functions above i can use 0x7C00 through 0x7F7C for data? or does that mean i use 0-0x3F7B and it will be put in the correct place?
What happens if my id becomes larger?