cannot complie to HEX after installing V10 Paid licence

For general Flowcode discussion that does not belong in the other sections.
rsbake24ja
Posts: 7
http://meble-kuchenne.info.pl
Joined: Fri Dec 18, 2020 4:14 am

Re: cannot complie to HEX after installing V10 Paid licence

Post by rsbake24ja »

Hi Steve
That worked I can now compile to C.
I cannot compile to HEX. The message is cannot find file. I can see the file in the directory. It has a V10 symbol next to it is that the problem? I have added image of registry

Target folder: D:\Users\roy\Documents\Flowcode8\2024
Source name: D:\Users\roy\Documents\Flowcode8\2024\PIC24FV_28PIN.fcfx
Title:
Description:
Device: PIC16.24F.24FV32KA302
Generated by: Flowcode v8.2.2.15
Date: Wednesday, July 31, 2024 08:40:25
Users: 1
Registered to: xxxxxxxxxxxx
License key: xxxxxxxxx
NOT FOR COMMERCIAL USE
https://www.matrixtsl.com
Launching the compiler...
D:\Program Files (x86)\Flowcode\Common\Compilers\pic16\batchfiles\pic16_C30_comp.bat "PIC24FV_28PIN" "D:\Users\roy\Documents\Flowcode8\2024\" "24FV32KA302"
ERROR: Can not launch process: The system cannot find the file specified.


D:\Program Files (x86)\Flowcode\Common\Compilers\pic16\batchfiles\pic16_C30_comp.bat reported error code -1

Autoclose turned off


FINISHED
Attachments
screen shot registry.png
screen shot registry.png (139.59 KiB) Viewed 2683 times

Steve-Matrix
Matrix Staff
Posts: 1513
Joined: Sat Dec 05, 2020 10:32 am
Has thanked: 212 times
Been thanked: 351 times

Re: cannot complie to HEX after installing V10 Paid licence

Post by Steve-Matrix »

It seems that v8 is now finding the toolchain location but is failing to launch the appropriate file.

There are a few posts in the old forums that may help. For example, this one seems to offer a solution:
https://www.matrixtsl.com/mmforums/view ... 658#p90658

On my PC the toolchain appears to work ok. My Compiler Option settings are in the image below:

pic16_compiler_options.png
pic16_compiler_options.png (21.53 KiB) Viewed 2673 times

And I have checked the location of the toolchain and it does contain the "batchfiles\pic16_C30_comp.bat" file, which has the following contents:

Code: Select all

@REM expected parameters are...
@REM   %1 = long filename (without extension)
@REM   %2 = shortname of directory
@REM   %3 = device name

@set temppath=%path%
@path=%~dp0..\bin;
@PUSHD %~2
xc16-gcc -c -mcpu=%3 -omf=coff -funsigned-char -fno-short-double -Os -I"%~dp0..\support\h" -I"%~dp0" -std=gnu99 %1.c -o %1.o
@POPD
@IF %ERRORLEVEL% NEQ 0 GOTO Error

@ECHO.
@ECHO Compilation successful!
@path=temppath
@EXIT 0

:Error
@ECHO.
@ECHO Error returned from [xc16-gcc.exe]
@path=temppath
@EXIT 1
Please check to see if these are the same on your PC.

rsbake24ja
Posts: 7
Joined: Fri Dec 18, 2020 4:14 am

Re: cannot complie to HEX after installing V10 Paid licence

Post by rsbake24ja »

Hi Steve
Sorry the delay. Yes my batch file matches what you have as shown below .
I was tinkering with the idea of pulling v8 from the machine and reinstalling on the machines D drive next to v10.
Both compilers on v8 and v10 are working ok for 8 bit chips.

@REM expected parameters are...
@REM %1 = long filename (without extension)
@REM %2 = shortname of directory
@REM %3 = device name

@set temppath=%path%
@path=%~dp0..\bin;
@PUSHD %~2
xc16-gcc -c -mcpu=%3 -omf=coff -funsigned-char -fno-short-double -Os -I"%~dp0..\support\h" -I"%~dp0" -std=gnu99 %1.c -o %1.o
@POPD
@IF %ERRORLEVEL% NEQ 0 GOTO Error

@ECHO.
@ECHO Compilation successful!
@path=temppath
@EXIT 0

:Error
@ECHO.
@ECHO Error returned from [xc16-gcc.exe]
@path=temppath
@EXIT 1

Post Reply