Using redlinkserv standalone. Probe list csv not found

[yash_bhatt1]

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.

[converse]

First thing to try - don't start redlinkserv. If you don't start it, crt_emu_cmredlink will start it automatically with the correct options. 

[yash_bhatt1]

Hi,

Thank you for the suggestion.

This was the way we went on initially. But after the first flash (of bootloader) when we fired the command to flash the application firmware, we got the below error:

Ns: MCUXpresso IDE RedlinkMulti Driver v11.1 (Dec  4 2019 19:02:41 - crt_emu_cm_redlink build 5)
Pc: (  0) Reading remote configuration
Wc(03). No cache support.
Nc: Found chip XML file in Project_Location/Release/MK64FN1M0xxx12.xml
Pc: (  5) Remote configuration complete
Nc: Restarted LinkServer process (PID 27712).
Ns: redlink server client - failed to receive response (to op 26) from server after 2000ms - Connection timed out (rc 110)
Ns: redlink server client - failed to receive response (to op 26) from server after 2000ms - Connection timed out (rc 110)
Ns: redlink server client - failed to receive response (to op 26) from server after 2000ms - Connection timed out (rc 110)
Nc: Reconnected to existing LinkServer process.
Ns: redlink server client - failed to receive response (to op 26) from server after 2000ms - Connection timed out (rc 110)
Nc: Server OK but no connection to probe 1 core 0 (after 3 attempts) - Ee(42). Could not connect to core.
Ns: redlink server client - failed to receive response (to op 32) from server after 60000ms - Connection reset by peer (rc 104)
Wc: ============= SCRIPT: kinetisconnect.scp =============
Wc: ============= END SCRIPT =============================
Ed:02: Failed on connect: Ee(42). Could not connect to core.
Et:31: No connection to chip's debug port
Pc: (100) Target Connection Failed

We observed that if we had MCUXpresso running and after click Boot debug probe (the Red boot symbol), the commands worked perfectly fine.

We are lost on if something is missing with the command or there is any prerequisite for running the same from commandline without having the IDE at all.

Regards,

Yash

[converse]

I notice in your first post that you are using "time". What happens if you don't use it? And don't start redlinkserv.

[yash_bhatt1]

I get the same behavior in both cases.