when I flash a fw with generic level server , then flash other fw with sensor server , the system runs error, if I use command "nrfjprog --eraseall -f NRF52" to erase first then flash ,the system runs well, why need to erase first?

[Tomlee]

Hi,

    I have met one bug.

when I flash a fw with generic level server , then flash other fw with sensor server ,  the system runs error,  if I use command "nrfjprog --eraseall -f NRF52" to erase first then flash ,the system runs well,   why need to erase first?

error as follow:

app_error_weak.c,  115, Mesh error 34314 at 0x00000000 (:0)

[Mttrinh]

Hi,

Are you flashing the firmware using Segger Embedded Studio or nrfjprog?

You need to erase the device first to make space for the new firmware.

[Mttrinh]

Hi,

What command line version are you using? 

Tomlee said:

2)but if I flash a fw with generic level server , then flash fw with generic level server again , in this situation it don't need to erase first , fw will also runs well

Is the firmware unchanged when you do this?

[Tomlee]

Maybe we got a wrong idea.

I use segger to compile and download fw, there are two hex files (softdevice.hex and application.hex),  right?

before using segger to download,  there should erase first (I think only erase application area) .

so now I give a question again:

base on  fw with generic level server of the board

1) if flash diff mesh server model fw (mean I change mesh model frmo generic level server model to sensor server model) why need to use command "nrfjprog --eraseall -f NRF52" to erase whole area?, otherise if just use segger to download  it works error

2) if flash same mesh server model fw(mean I just modify some function not about mesh model) , why do not need to use command "nrfjprog --eraseall -f NRF52" to erase whole area, just use segger to download , it also work well?

[Mttrinh]

Hi,

Sorry I assumed you were using the command line to flash the firmware since you mentioned nrfjrpog. 

Segger uses --sectorerase when you flash the device. Which means that the network data is still being kept, only the application is being erased. This will only work if you flash the same firmware with some minor changes. Changing models will make the provisioned data that is being kept not match with the application. So if you plan to change models you need to run --eraseall first before flashing your firmware.

[Tomlee]

Thanks your replied.

since I need to add dfu function,   if I change mesh model, then it doesn't work after updating fw with dfu

so how can I erase network data during upate fw with dfu?

[Mttrinh]

Hi,

What SDK version are you using?

You need to add these lines of code in your application:

https://github.com/NordicSemiconductor/nRF5-SDK-for-Mesh/blob/master/examples/dimming/dimming_server/src/main.c#L372-L384

That will check if your provisioning data is still valid, if not it will erase the configuration data so that you can re-provision the node.

[Tomlee]

Hi Mttrinh,

Thanks so much. I will check.

What SDK version are you using?

====nRF SDK: V17.0.2   

====Mesh SDK:  V5.0.0

Do you mean that use follow code to erase?

/* Clear model config file as loading failed */
	model_config_file_clear();
	__LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Data in the persistent memory was corrupted. Device starts as unprovisioned.\n");
	__LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Reboot device before starting of the provisioning process.\n");

[Tomlee]

I get NRF_ERROR_INVALID_DATA always, what shou I do to solve this ?

[Mttrinh]

Yes, you should add the highlighted code in the github link I referred to. It looks like you are missing model_config_file_clear().

[Tomlee]

Hi Mttrinh,

    thanks for your reply.

    but I add this code,  it still has gotten this message "NRF_ERROR_INVALID_DATA".

[Mttrinh]

Hi,

Is the function model_config_file_clear() being called after NRF_ERROR_INVALID_DATA?