AnsweredAssumed Answered

Using redlinkserv standalone. Probe list csv not found

Question asked by yash.bhatt1@einfochips.com on Jul 30, 2020
Latest reply on Aug 11, 2020 by yash.bhatt1@einfochips.com

Hi,

 

We are trying to use program the FRDM-K64F board using SWD via commandline.

We are using the following command:

./redlinkserv --connectscript kinetisconnect.scp

time ./crt_emu_cm_redlink --flash-load-exec  "bootloader.bin" -g --debug 2  --vendor NXP -p MK64FN1M0xxx12 --load-base=0x0 --ConnectScript kinetisconnect.scp -ProbeHandle=1 -CoreIndex=0 --flash-driver= -x Project_Location/Release --flash-dir /usr/local/mcuxpressoide-11.1.0_3209/ide/plugins/com.nxp.mcuxpresso.tools.bin.linux_11.1.0.201912041804/binaries/Flash  --flash-dir Project_Location/.mcuxpressoide_packages_support/MK64FN1M0xxx12_support/Flash   --flash-hashing

 

Using the above sequence of command, we are able to flash the bootloader successfully.

BUT when we fire the next command to flash the firmware, it fails with "Server OK but no connection to probe 1 core 0 (after 3 attempts) - Ee(42). Could not connect to core." error.

 

We observe that when we have MCUxpresso running with the redlink server booted via the IDE, we are able to flash both the images (without firing the redlinkserv command this time). And it seems that the redlinkserv is not booting properly in our case as we dont see the same output as printed in the IDE when looking for probes. The output we are seeing is as follows:

 

> Kinetis Connect Script
> Error: Probe table CSV file not found
> No probes found
> Probe Not Found

 

We have made following changes to the kinetisconnect.scp file as suggested in the file itself.

-- REM 200   ProbeList

-- REM a% = ProbeFirstFound

-- REM 260   ProbeOpenByIndex a%

++ 200 ProbeList

++ 210 a% = ProbeFirstFound

++ 260 ProbeOpenByIndex a%

 

We want to be able to flash the board without depending on the ide. What are we missing here? Please help us out.

Any help will be appreciated.

Outcomes