I believe there are a couple of ways to do what you are trying to do.
The first is to go into the BSP and start to add fields to the BoardParams structure. This involves updating a number of files in the BSP and means that you need to ensure that the bootloader is updated each time you change anything.
The second an I believe simpler way is to simply define a number of structures to contain the data that you need and to then save them in the NV area using the NVRAM Drive API. This has a number of functions that help you out.
THe attached file is what I use for storing a few values that are used to set up my system. The structures will need to be modified to contain the data you need to store but the overall outline with my NVRCFG_Init() and NVRCFG_Save() functions should work for you.
The first way (adding to the devBoardParamsType structure in boardParams.h) is not really a way you’d want to go because you’re modifying the default NVRAM structure, and that could cause NVRAM corruption issues in the future (porting forward, for example, to a new NET+OS version).
The second way is good so long as the values you want to change aren’t changed that frequently. Keep in mind you’re writing to the NVRAM sector, and the way NOR flash works is to read it all into RAM, make the changes to the Flash sector, erase the sector, and then write it all back. If your user powers off the unit while it’s doing that, you will not only corrupt your settings, but those stored in the default NVRAM structure. I would say it’s ok if it’s being changed as much as your IP settings (which is stored in the default NVRAM structure).
A third method would to be to create a file in the Flash File System, and read/write to that. The up side is that if it gets corrupt, it at worst corrupts the file, or at best, the file system can recover and use the last file saved before the corruption. The down side is that you have to allocate a number of sectors of flash for this that may be more useful in application storage space.
I am including a root.c that I put together some time ago. I believe it does something close to what you want to do. Since I have had it around for a while I checked and all of the APIs and data structures used are described in the API reference guide. I'd advise you use it as a GUIDE only.