Flashing blinky on the FRDM-K22F board

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 
已解决

Flashing blinky on the FRDM-K22F board

跳至解决方案
1,089 次查看
laszlomonda
Contributor V

Hi guys,

I'm trying to flash the Zephyr blinky application from MCUXpresso for VSCode.

I can build the application, and I connected the OpenSDA port of the FRDM-K22F to my PC.

Afterward, I clicked on Flash Programmer in the quickstart panel. I selected the LinkServer option and hit run; then, I got the "Error: No probe detected" error message.

Thanks for your help in advance!

0 项奖励
回复
1 解答
1,060 次查看
Alice_Yang
NXP TechSupport
NXP TechSupport

Hello @laszlomonda 

1)Do you have any other IDEs on your PC? For example MCUXPresso IDE? KEIL? IAR? 

Debug with one of them first? Just want to confirm whether the board can work well.

2) Try to update the bootloader firmware to Jlink_OpenSDA, then debug again. 

About how to update bootloader, please refer to:

Quick start guide:

https://www.nxp.com/webapp/Download?colCode=FRDM-K22F-QSG 

Alice_Yang_0-1698912081706.png

 

BR

Alice

在原帖中查看解决方案

0 项奖励
回复
4 回复数
1,069 次查看
laszlomonda
Contributor V

Hi Alice,

On Linux, there's no device manager, but the kernel log, which shows the device:

[  604.529584] usb 3-1.2: new full-speed USB device number 10 using xhci_hcd
[  604.659999] usb 3-1.2: New USB device found, idVendor=0d28, idProduct=0204, bcdDevice=10.00
[  604.660002] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  604.660004] usb 3-1.2: Product: DAPLink CMSIS-DAP
[  604.660005] usb 3-1.2: Manufacturer: ARM
[  604.660006] usb 3-1.2: SerialNumber: 0231000067424e45005600034a4f002bc521000197969900
[  604.786014] usb-storage 3-1.2:1.0: USB Mass Storage device detected
[  604.786160] scsi host6: usb-storage 3-1.2:1.0
[  604.797350] hid-generic 0003:0D28:0204.000C: hiddev0,hidraw1: USB HID v1.00 Device [ARM DAPLink CMSIS-DAP] on usb-0000:0e:00.3-1.2/input3
[  604.803033] cdc_acm 3-1.2:1.1: ttyACM0: USB ACM device
[  605.791348] scsi 6:0:0:0: Direct-Access     MBED     VFS              0.1  PQ: 0 ANSI: 2
[  605.791707] sd 6:0:0:0: Attached scsi generic sg1 type 0
[  605.792201] sd 6:0:0:0: [sdb] 131200 512-byte logical blocks: (67.2 MB/64.1 MiB)
[  605.792389] sd 6:0:0:0: [sdb] Write Protect is off
[  605.792392] sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00
[  605.792544] sd 6:0:0:0: [sdb] No Caching mode page found
[  605.792548] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[  605.814376] sd 6:0:0:0: [sdb] Attached SCSI removable disk

The virtual drive is also mounted.

I also have these udev rules set up, so there should be no permission issues.

Yet, Visual Studio Code doesn't doesn't show any debug probes.

What should be the solution?

0 项奖励
回复
1,061 次查看
Alice_Yang
NXP TechSupport
NXP TechSupport

Hello @laszlomonda 

1)Do you have any other IDEs on your PC? For example MCUXPresso IDE? KEIL? IAR? 

Debug with one of them first? Just want to confirm whether the board can work well.

2) Try to update the bootloader firmware to Jlink_OpenSDA, then debug again. 

About how to update bootloader, please refer to:

Quick start guide:

https://www.nxp.com/webapp/Download?colCode=FRDM-K22F-QSG 

Alice_Yang_0-1698912081706.png

 

BR

Alice

0 项奖励
回复
1,043 次查看
laszlomonda
Contributor V
Thank you! Flashing the recommended bootloader made the board appear in VS Code, and I could flash the Blinky firmware, which worked as expected.
0 项奖励
回复
1,073 次查看
Alice_Yang
NXP TechSupport
NXP TechSupport

Hello @laszlomonda 

First check device manager of your pc, confirm the debug probe is recognized,

then refer to below link to debug:

https://mcuoneclipse.com/2023/08/16/vs-code-debugging/  

 

BR

Alice

0 项奖励
回复