If download example light_switch on new clear chip nrf52832, that advertising is not done. But after downloading the firmware without mesh, example light_switch will broadcast for a while.
If download example light_switch on new clear chip nrf52832, that advertising is not done. But after downloading the firmware without mesh, example light_switch will broadcast for a while.
Hey Blastka!
Would you mind explaining a bit more what you mean by downloading the firmware without Mesh, and what the issue is?
Best regards,
Elfving
I downloading the firmware example from nRF5_SDK_17.0.2_d674dde, It is the firmware without Mesh. The problem is that a pure chip of a hardwired mesh does not advertise until you flash this chip with another example nRF5_SDK, and then again with a mesh. And also this broadcast may disappear again after an unknown period of time. Also i found the radio power first enable and then disabled in registers
I want you to check it with your company.
Hey again Blastka!
How are you flashing this nRF52832? Are you using the precompiled files in the SDK? Are you running a full flash erase before flashing the mesh examples?
Best regards,
Elfving
I use everything as in the examples. clean file without any modifications. I have been working with your boards for a long time, I do everything. i use Nrf programmer also.
I use build files and upload through the built-in SEGGER studio:
Target->connect
Target->erase chip
Target-> download
Hello Blastka!
There might be something left in the flash that wasn't erased. Even if the examples are not modified, something left in the flash can still be a problem. The node might for instance believe it is already provisioned, etc.
Are you seeing the same issue when you flash the nRF52832 using SES? And when you do a full flash erase first?
Best regards,
Elfving
I seeing it when flash the nRF52832 using SES and nrf Programmer. In both programs. I do always full flash erase.
I see. That is odd.
You mentioned that what works for you is to flash the FW example from nRF5 SDK, then another example, and then a mesh example from the nRF5 SDK. Are you erasing the chip from SES between each time as well?
There is a known error when flashing through SES which makes the SD not get re-initialized after flashing, if it has already gotten initialized earlier. Resetting the DK however should fix that. Could you try hitting the RESET button after flashing your Mesh example and see if that fixes anything?
Could you also try flashing it using nrfjprog?
nrfjprog -e
nrfjprog --program [filename].hex --reset
Best regards,
Elfving
I see. That is odd.
You mentioned that what works for you is to flash the FW example from nRF5 SDK, then another example, and then a mesh example from the nRF5 SDK. Are you erasing the chip from SES between each time as well?
There is a known error when flashing through SES which makes the SD not get re-initialized after flashing, if it has already gotten initialized earlier. Resetting the DK however should fix that. Could you try hitting the RESET button after flashing your Mesh example and see if that fixes anything?
Could you also try flashing it using nrfjprog?
nrfjprog -e
nrfjprog --program [filename].hex --reset
Best regards,
Elfving
It did not help.
Neither? Okey.
So the only thing that is working now is to flash the FW example from nRF5 SDK, then another example, and then a mesh example from the nRF5 SDK. Could you send me a hexdump from your nrf52832DK between each of these stages so that I could take a look at what is happening?
nrfjprog --readcode --readuicr dump.hex
Best regards,
Elfving
Thank you for your attention. It is my problem with my boards and one microcontroller was with bug.
Ah okey, that would explain it! I'm glad you figured it out.
Best regards,
Elfving
