Flowcode Support Board

Hello again.

A well-known error is back again,
because the problem itself has not been solved.
All old programmes make the same error. I have tried to eliminate the error as before, but this time it doesn't work either.

Please fix it as soon as possible.

Target folder: C:\Users\uwe\Documents\Flowcode Projekte\USBCDC
Source name: C:\Users\uwe\Documents\Flowcode Projekte\USBCDC\Flowcode_cdc_usb.fcfx
Title:
Description:
Device: PIC32.32MZ.32MZ2048EFH100
Generated by: Flowcode v9.2.0.33
Date: Wednesday, November 03, 2021 15:57:03
Users: 1
Registered to: SpeedPic32 (24146314)
Licence key: UCCVMA
NOT FOR COMMERCIAL USE
https://www.flowcode.co.uk
Using <PICkit3 PK3CMD External Power> inbuilt settings for compiler
Launching the compiler...
C:\Program Files (x86)\Flowcode\Compilers\pic32\bin\xc32-gcc.exe -mprocessor=32MZ2048EFH100 -O1 -o "C:\Users\uwe\Documents\Flowcode Projekte\USBCDC\Flowcode_cdc_usb.elf" "C:\Users\uwe\Documents\Flowcode Projekte\USBCDC\Flowcode_cdc_usb.c"
C:\Users\uwe\Documents\Flowcode Projekte\USBCDC\Flowcode_cdc_usb.c:462:23: fatal error: CDC_Setup.h: No such file or directory

^
compilation terminated.

C:\Program Files (x86)\Flowcode\Compilers\pic32\bin\xc32-gcc.exe reported error code 0xFF

Autoclose turned off


FINISHED

Hello FC Team

Once again the error concerns the PIC 32 MX and MZ chips.
I am starting a new project
I choose a PIC, e.g. the PIC32MX470.
I choose USB Serial
I enter the initialisation in Main
I start the compilation to hex
I enter a project name
and lo and behold error 0xFF comes up
C:\Program Files (x86)\Flowcode\Compilers\pic32\bin\xc32-gcc.exe reported error code 0xFF
No matter which chip from the MX or MZ series

How can this happen?
Am I the only one with this problem?
Can you check this out, anyone reading this!
It will not take long

For your information: I have always installed all updates and no further projects after the one with the MCP356X.

Please short info
Thanks to all who test this briefly.

Hello I have it

in the compiler options was for whatever reason a wrong entry set as default, sorry

Many thanks for letting us know. Glad you got it sorted.