FAQs
English (US) 日本語 | Japanese 中文 | Chinese (Simplified)

MK64FN1M0VMD12 | Flashing Issue

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

MK64FN1M0VMD12 | Flashing Issue

‎10-16-2024 06:17 AM
685 Views
HariHaran4274
Contributor I

Hello Community

We are trying to flash the MK64FN1M0VMD12 on a custom board with the help of FRDMK64F Evaluation Board (ported to SEGGER J-link).
 
We are following the same Connections, as NXP recommended 
Note: J11 trace cut is done to use the EVB to flash the external MCU.
 
 image.png
When we try to flash the external MK64FN1M0VMD12 we are facing the issue,
 
 
fl::target -lc "bringup1"
fl::target -b 0x1fff0000 0x40000
fl::target -v off -l off
cmdwin::fl::device -d "FTFE_PFlash1M0" -o "128Kx64x1" -a 0x0 0xfffff
cmdwin::fl::image -f "C:\\Users\\vvsa\\Downloads\\mcu-bringup1.bin" -t "Auto Detect" -re on -r 0x0 0xfffff -oe off
cmdwin::fl::erase image
 Beginning Operation ...    
-------------------------
Auto-detection is successful.  
  File is of type Binary/Raw Format.  
 
Performing target initialization ...    
 Downloading Flash Device Driver ...  
Error:  Couldn't write flash driver to target.  Can not read target memory at location: 0x000000001FFF0000.Please make sure that the chip selects are properly configured.
The CWPP response code is: ARM GDI Protocol Adapter : An error occurred while trying to write memory. The Debugger can not write memory..
An invalid preference was passed to the GDI protocol plugin(ARM GDI Protocol Adapter)
Error: Couldn't write flash driver to target.Can not read target memory at location: 0x000000001FFF0000.
Please make sure that the chip selects are properly configured.
The CWPP response code is: ARM GDI Protocol Adapter : An error occurred while trying to write memory. The Debugger can not write memory..
 
 
but we are able to flash MCU present on the EVB itself.
 
Kindly help us on this..
 
0 Kudos
Reply
2 Replies

‎10-16-2024 10:22 AM
656 Views
Pavel_Hernandez
NXP TechSupport
NXP TechSupport

Hello, my name is Pavel, and I will be helping on your case, I reviewed your information. The J9 is only for an end communication from the debugger, I mean with this could not communicate an external MCU.

The J9 is using for updating the firmware on the MK20 that acts as debugger on the board.
The J10 is for flash the MK64 interface as SWD to use with an external debugger.

This is a scenario that is not explored by NXP but maybe this thread could help you.

Using FRDM-K64F Board to debug another Kinetis Board | MCU on Eclipse

Best regards,
Pavel

0 Kudos
Reply

‎10-16-2024 11:14 AM
651 Views
HariHaran4274
Contributor I

Hello Pavel, Thanks for the reply.

If that is the case, i will update you the test scenarios we have done so for.

1. Segger J-link with custom board :  we have connected the Segger J-link with our custom board, there also we have faced the same issue.

console output : 

fl::target -lc "gpiobin"
fl::target -b 0x1fff0000 0x40000
fl::target -v off -l off
cmdwin::fl::device -d "FTFE_PFlash1M0" -o "128Kx64x1" -a 0x0 0xfffff
cmdwin::fl::image -f "C:\\Users\\vvsa\\Downloads\\gpio.bin" -t "Auto Detect" -re on -r 0x0 0xfffff -oe off
cmdwin::fl::erase image
Beginning Operation ...
-------------------------
Auto-detection is successful.
File is of type Binary/Raw Format.

Performing target initialization ...
Downloading Flash Device Driver ...
Reading flash ID ...
Erasing Sector 0x00000000 to 0x00000FFF
Erasing Sector 0x00001000 to 0x00001FFF
Erasing Sector 0x00002000 to 0x00002FFF
Erasing Sector 0x00003000 to 0x00003FFF
Erasing Sector 0x00004000 to 0x00004FFF
Erasing Sector 0x00005000 to 0x00005FFF
Erasing Sector 0x00006000 to 0x00006FFF
Erasing Sector 0x00007000 to 0x00007FFF
Erasing Sector 0x00008000 to 0x00008FFF
Erasing Sector 0x00009000 to 0x00009FFF
Erasing Sector 0x0000A000 to 0x0000AFFF
Erasing Sector 0x0000B000 to 0x0000BFFF
Erasing Sector 0x0000C000 to 0x0000CFFF
Erasing Sector 0x0000D000 to 0x0000DFFF
Erasing Sector 0x0000E000 to 0x0000EFFF
Erasing Sector 0x0000F000 to 0x0000FFFF
Erasing Sector 0x00010000 to 0x00010FFF
Erasing Sector 0x00011000 to 0x00011FFF
Erasing Sector 0x00012000 to 0x00012FFF
Erasing Sector 0x00013000 to 0x00013FFF
Erasing Sector 0x00014000 to 0x00014FFF
Erasing Sector 0x00015000 to 0x00015FFF
Erasing Sector 0x00016000 to 0x00016FFF
Erasing Sector 0x00017000 to 0x00017FFF
Erasing Sector 0x00018000 to 0x00018FFF
Erasing Sector 0x00019000 to 0x00019FFF
Erasing Sector 0x0001A000 to 0x0001AFFF
Erasing Sector 0x0001B000 to 0x0001BFFF
Erasing Sector 0x0001C000 to 0x0001CFFF
Erasing ...
Erase Command Succeeded
cmdwin::fl::write
Beginning Operation ...
-------------------------
Using restricted address range 0x00000000 to 0x000FFFFF
Programming file C:\Users\vvsa\Downloads\gpio.bin
Auto-detection is successful.
File is of type Binary/Raw Format.

Downloading Flash Device Driver ...
Reading flash ID ...
Auto-detection is successful.
File is of type Binary/Raw Format.

Downloading 0x00010000 bytes to be programmed at 0x00000000
Downloading 0x0000C638 bytes to be programmed at 0x00010000
Executing program ....
Executing program .....
Program Command Succeeded

2. Segger j-link with FRDMK64F : we have connected the Segger J-link to the J9 of FRDMk64f with j8 and j12  trace cut. here, we are able to flash the MCU.

Console output: 

fl::target -lc "bringup1"
fl::target -b 0x1fff0000 0x40000
fl::target -v off -l off
cmdwin::fl::device -d "FTFE_PFlash1M0" -o "128Kx64x1" -a 0x0 0xfffff
cmdwin::fl::image -f "C:\\Users\\vvsa\\Downloads\\mcu-bringup1.bin" -t "Auto Detect" -re on -r 0x0 0xfffff -oe off
cmdwin::fl::erase image
Beginning Operation ...
-------------------------
Auto-detection is successful.
File is of type Binary/Raw Format.

Performing target initialization ...
Downloading Flash Device Driver ...
Error: Couldn't write flash driver to target. Can not read target memory at location: 0x000000001FFF0000.Please make sure that the chip selects are properly configured.
The CWPP response code is: ARM GDI Protocol Adapter : An error occurred while trying to write memory. The Debugger can not write m
emory..
An invalid preference was passed to the GDI protocol plugin(ARM GDI Protocol Adapter)
Error: Couldn't write flash driver to target.Can not read target memory at location: 0x000000001FFF0000.
Please make sure that the chip selects are properly configured.
The CWPP response code is: ARM GDI Protocol Adapter : An error occurred while trying to write memory. The Debugger can not write m
emory..

 

Please find the connections on both scenarios below,

image (1).pngimage (2).png

 

 

0 Kudos
Reply