pc_ble_driver_py.exceptions.NordicSemiException: No ping response after opening COM port

RE: pc_ble_driver_py.exceptions.NordicSemiException: No ping response after opening COM port

Hung Bui — Thu, 04 May 2023 13:45:16 GMT

Hi Swanand,

They can share UART, the bootloader is not running when the application is running.
But you have to make sure you initialize UART properly in your application. Double check if you have configured everything correctly. The potential issue is that if the bootloader use UART the registers may be different from the reset value.

RE: pc_ble_driver_py.exceptions.NordicSemiException: No ping response after opening COM port

swanand — Thu, 04 May 2023 13:19:56 GMT

Hello,

Yes, the DFU update is working fine & it runs successfully. I found that my 4th package is also working and running but I am not able to view data on a tera term(serial utility) which I send on uart(uart instance 1 configured in application).

my understanding is that nrf52832 has only 1 uart peripheral. So we are doing dfu over uart in bootloader and the application also uses uart. Can I use uart in the application?

also If I erased all and then flashed mbr + uart hex file then I can see uart prints.

RE: pc_ble_driver_py.exceptions.NordicSemiException: No ping response after opening COM port

Hung Bui — Wed, 03 May 2023 12:20:12 GMT

Hi Swanand,

When you wrote "flash it" you meant program the application via programmer or you meant you did DFU update ?
I would assume what you meant by " this time zip is not working" it means the DFU update worked fine and you managed to update but it doesn't run.

In that case you may need to do debugging. You can debug and step in the code just like what you normally do.
If you see that you can not debug the code, it could be that the bootloader didn't run the application, then you need to step in the code of the bootloader and check why it doesn't jump to the application. You may need to use the debug version of the bootloader to step in the bootloader code.

What I want to say is that it's not a black box and you can just debug the bootloader and the application normally.

RE: pc_ble_driver_py.exceptions.NordicSemiException: No ping response after opening COM port

swanand — Wed, 03 May 2023 11:48:23 GMT

devzone.nordicsemi.com/.../0564.test.rar

Please find the attached zip file. I have created a zip file by using this hex.

RE: pc_ble_driver_py.exceptions.NordicSemiException: No ping response after opening COM port

swanand — Wed, 03 May 2023 11:24:05 GMT

Hi,

Thanks for your guidance. I am able to do dfu. I have updated 3 packages. But now I am facing issue

I have taken blinky code and made a zip of it and flashed that code. it worked. Again I updated the blinky code, made another zip, and flashed it again(worked). Now I added button logic in blinky code and made 3rd zip & flashed (worked). the fourth time I added UART in the blinky code and flashed a zip file. this time zip is not working.

If I erased all and then flashed mbr + 4th hex file(uart added file) it is working. But if I make a zip file of it, it is not working.

Note: I have changed RAM_START=0x20000000 to RAM_START=0x20000008. UART code is not working at RAM_START=0x20000000

RE: pc_ble_driver_py.exceptions.NordicSemiException: No ping response after opening COM port

Hung Bui — Fri, 28 Apr 2023 07:38:41 GMT

Hi Swanand,
After you DFU update the application code. You can't just modify the code and flash again. The bootloader won't accept any change to the code without going through DFU.
This is to avoid the code being manipulated or tampered. It's called boot validation. By default it's done by calculating the CRC of the image.

You can turn boot validation off by modifying the bootloader. Please take a look at dfu_enter_check() , you can comment this out :
if (!app_is_valid(crc_on_valid_app_required()))
{
NRF_LOG_DEBUG("DFU mode because app is not valid.");
return true;
}

But make sure to turn it back on when you finish with development.

RE: pc_ble_driver_py.exceptions.NordicSemiException: No ping response after opening COM port

swanand — Thu, 27 Apr 2023 12:13:23 GMT

Hi,

I opened segger embedded studio then go to the project and right clicked on options->select common->linker->selection placement macros-> change flash address to FLASH_START=0x1000 and FLASH_SIZE=0x79000 and it works.

Now I wanted to flash another zip file so I have taken uart example. I did the above changes and then build and run the code. This time the code did not work and if I revert back the changes then the code is working but if I create a zip file of that hex then the zip file is not working.

RE: pc_ble_driver_py.exceptions.NordicSemiException: No ping response after opening COM port

Hung Bui — Mon, 24 Apr 2023 07:40:50 GMT

Hi Swanand,

The easiest way to find out the different between a blank project and mbr project, I think, is to compare the .ld file and the Makefile. You can use an editor tool for example Notepad++ with Compare plugin.
If you compare the blinky_gcc_nrf52.ld in the \blinky\pca10040\mbr with the one in \blinky\pca10040\blank you can find that the RAM need to be updated as well:

And in the make file, you would need to add $(SDK_ROOT)/components/softdevice/mbr/headers \ into INC_FOLDERS.

RE: pc_ble_driver_py.exceptions.NordicSemiException: No ping response after opening COM port

swanand — Fri, 21 Apr 2023 14:54:24 GMT

can you please guide on how to move the start address of the application to address 0x1000?

I opened blinky_gcc_nrf52.ld file and changed flash starting address. earlier it was 0x00.I changed it to 0x1000

MEMORY

{

FLASH (rx) : ORIGIN = 0x1000, LENGTH = 0x80000

RAM (rwx) : ORIGIN = 0x20000000, LENGTH = 0x10000

}

But it didn't work.

RE: pc_ble_driver_py.exceptions.NordicSemiException: No ping response after opening COM port

Hung Bui — Fri, 21 Apr 2023 11:26:58 GMT

Hi Swanand,

The tricky part when you test with the _debug version and non _debug version is that you would need to do an eraseall before you test with each of them. The reason is that they require the UICR to be re-written because of different start address of the bootloader.

If you do a eraseall/recover before testing it should be fine.

You should use the \examples\peripheral\blinky\pca10040\mbr if you plan to do DFU.

It's because when you flash bootloader and MBR for DFU, the MBR is located at address 0x00000000 to address 0x0001000. Because of that the application should start from 0x00001000 instead of 0x00000000. So you need to build the application that start from this address, not the one start from 0x00.
If you DFU an application that supposed to run at 0x00 (the normal blinky) it won't work at address 0x1000.

So if you plan to move to something else, for example uart example or rtc example, you would need to do the same modification to move the start address of the application to address 0x1000.

RE: pc_ble_driver_py.exceptions.NordicSemiException: No ping response after opening COM port

swanand — Fri, 21 Apr 2023 10:37:29 GMT

Hi,

Thanks for your reply. It is working with pca10040_uart_debug but not working with pca10040_uart. How can I run with pca10040_uart?

I have another doubt I program secure_bootloader_uart_mbr_pca10040_debug.hex, mbr.hex, and then generate the package, at that time if I use blinky_pca10040_mbr.hex to generate the package then after dfu, the new image code is working fine but if I generate a zip file with normal blinky_pca10040.hex file then it shows Device programmed but that package is not working (zip file code is not working. LEDs are not blinking).

RE: pc_ble_driver_py.exceptions.NordicSemiException: No ping response after opening COM port

Hung Bui — Thu, 20 Apr 2023 12:51:02 GMT

Please don't test with mergehex or settings until you have DFU working.
Please do this:
1. Flash MBR + your blinky example . Make sure LEDs blink.

2. Erase all

3. Rebuild the bootloader with your public key.

4. Flash the bootloader and the MBR. Make sure the LED1&4 turn on showing it's in debug mode.

5. Generate the .zip image from your application and your private key

6. Do DFU update. Verify that LED blinks.

7. Press and hold button 4 when reset the board, verify that it enters DFU mode.

8. Do another DFU update.

RE: pc_ble_driver_py.exceptions.NordicSemiException: No ping response after opening COM port

swanand — Thu, 20 Apr 2023 12:27:31 GMT

Yes, I have tried to test with the bootloader and the image in secure_dfu_test_images. it is working fine. But when I create my own packet and run it, that time it shows successful but the LEDs are not blinking. I am doing the following steps.

1.
nrfutil.exe keys generate private.key

2.
nrfutil keys display --key pk --format code private.key --out_file public_key.c

3.
nrfutil pkg generate --hw-version 52 --application-version 1 --application blinky_pca10040.hex --key-file private.key --sd-req 0 my_blinky.zip

4.
build uart secure bootloader code (Using embedded segger studio)

5.
nrfutil settings generate --family NRF52 --application blinky_pca10040.hex --application-version 1 --bootloader-version 2 --bl-settings-version 1 settings.hex

6.
nrfutil settings display settings.hex

7.
mergehex --merge settings.hex secure_bootloader_uart_mbr_pca10040.hex --output output.hex

8.
flash following hex files (using nRF connect)
mbr.hex
output.hex 

9.
nrfutil dfu serial -pkg my_blinky.zip -p COM10 -b 115200 -fc 0

RE: pc_ble_driver_py.exceptions.NordicSemiException: No ping response after opening COM port

Hung Bui — Thu, 20 Apr 2023 08:04:40 GMT

Hi Swanand,
No you don't need to re-flash MBR and bootloader very time you want to do DFU. However, you need to make sure the device is in DFU mode when do DFU. By default if you have done a DFU update, to be able to put the device to DFU mode again you need to hold button 4 and do a reset/power reset.

Please don't test with bootloader setting. You don't need bootloader setting to test DFU update.

Have you tried to test with the bootloader and the image in secure_dfu_test_images instead of your application and bootloader ?
You should see the LED blink after you update the blinky_mbr.zip . If it work, try to update the second time by putting the device in DFU mode again. ( You should see LED1 and LED4 lid)

RE: pc_ble_driver_py.exceptions.NordicSemiException: No ping response after opening COM port

swanand — Wed, 19 Apr 2023 11:18:35 GMT

Do I need to flash the MBR hex file and output.hex file (bootloader + bootloader setting) every time whenever I want to do DFU?

I am using mbr.hex file located at D:\nRF5_SDK_17.1.0_ddde560\examples\dfu\secure_dfu_test_images\uart\nrf52832

After nrfutil dfu serial -pkg my_blinky_mbr.zip -p COM10 -b 115200 -fc 0 command, I am getting the following response

C:\Users\Lenovo\Desktop\DFU_PKG\test1>nrfutil dfu serial -pkg my_blinky_mbr.zip -p COM10 -b 115200 -fc 0
[####################################] 100%
Device programmed.

C:\Users\Lenovo\Desktop\DFU_PKG\test1>

But still LEDs are not blinking.

RE: pc_ble_driver_py.exceptions.NordicSemiException: No ping response after opening COM port

Hung Bui — Wed, 19 Apr 2023 07:53:15 GMT

Hi Swanand,

You would need to double check if the bootloader is running when you test.

I would suggest to start again by doing a full erase of the chip.
If you use nrfjprog.exe you can call "nrfjprog --recover"

Then you can flash the bootloader and MBR again to test.

You can try debugging the bootloader to see if it's running after you flash.

RE: pc_ble_driver_py.exceptions.NordicSemiException: No ping response after opening COM port

swanand — Wed, 19 Apr 2023 05:27:22 GMT

Hello,

I am using Development Kit, nRF52832

https://www.tme.com/in/en/details/nrf52-dk/development-kits-others/nordic-semiconductor/?brutto=1&currency=USD&gclid=CjwKCAjw__ihBhADEiwAXEazJqeXMXIDukWCs8SEZTjG3WnDB_F9ixCgIa37lCZRoxRPJQxvu8bN7BoCA50QAvD_BwE

I am able to run dfu code 1 time only. Now if I repeat the same steps then I get "No ping response error"

RE: pc_ble_driver_py.exceptions.NordicSemiException: No ping response after opening COM port

Hung Bui — Tue, 18 Apr 2023 13:36:52 GMT

Hi Swanand,

Could you let us know which hardware board you are testing with ?
Have you made sure you can communicate with PC via UART at COM10 ? (for example with uart example)
Did you modify the bootloader to use the correct UART pins ?
If you test it on a Dev Kit would it work ?

The logs say that it can not communicate with the bootloader. So most likely something wrong with the UART communication.