PIC32 USB CDC Error

[SpeedPIC32]

Hello Stefan

I use my own board.
runs on 20 MHz, LCD 2x16, ADM485.
this is a display for a high-precision 1bar pressure sensor from Keller.
had only quickly tested whether I can compile without a functional test on the board. I have successfully made up for this with small changes in the Pic config.

greetings SpeedPIC32

18F2550USB1.fcfx

(8.96 KiB) Downloaded 38 times

[SpeedPIC32]

Hello everyone,

Why is no one addressing my issue?
Who is willing to assist me in resolving this issue?
What should I test and how?
Thank you for your numerous suggestions.
Unfortunately, it is still not working.

Best regards, SpeedPIC32

[SpeedPIC32]

Another test.
The error occurs as soon as I call up
USB_Serial1.

Target folder: C:\Users\Uwe\Documents\Matrix
Source name: C:\Users\Uwe\Documents\Matrix\CDCTest .fcfx
Title:
Description:
Device: PIC32.32MZ.32MZ2048EFH144
Generated by: Flowcode v10.1.2.40
Date: Wednesday, August 20, 2025 09:53:28
Users: 1
Registriert für: SpeedPIC32 (24146314)
Lizenzschlüssel:ZQ34CT
https://www.flowcode.co.uk
Using <cdcICD4> user settings for compiler
Start des Compilers...
C:\Program Files (x86)\Flowcode\Compilers\pic32\batch\PIC32compCDC.bat "32MZ2048EFH144" "C:\Users\Uwe\Documents\Matrix\" "CDCTest " "32MZ"

Project CDCTest
Device 32MZ2048EFH144
Objects CDCTest _32MZ2048EFH144


C:\Users\Uwe\Documents\Matrix>xc32-gcc -mprocessor=32MZ2048EFH144 -DMX_USBHS -IC:\Users\Uwe\Documents\Matrix\. -IC:\ProgramData\MatrixTSL\FlowcodeV10\CAL\PIC32BIT\USB\CDC -IC:\microchip\harmony\v1_11 -IC:\microchip\harmony\v1_11\framework -w -c -ffunction-sections -O1 -o "CDCTest _32MZ2048EFH144\CDCTest .o" "CDCTest .c" -DMX_USBHS
CDCTest .c: In function '_IntHandlerUSBInstance0':
CDCTest .c:262:27: error: 'sysObj' undeclared (first use in this function)
DRV_USBHS_Tasks_ISR_USBDMA(sysObj.drvUSBObject);
^
CDCTest .c:262:27: note: each undeclared identifier is reported only once for each function it appears in
CDCTest .c: In function '_IntHandlerUSBInstance0_USBDMA':
CDCTest .c:266:34: error: 'sysObj' undeclared (first use in this function)
#ifdef MX_PIC32_MX
^
Error(s) in build

C:\Program Files (x86)\Flowcode\Compilers\pic32\batch\PIC32compCDC.bat Hat den Fehlercode 0x1 gemeldet

Autoclose turned off


BEENDET

CDCTest .fcfx

(9.15 KiB) Downloaded 36 times

[medelec35]

hello.
Sorry for the delay.
We are looking at this issue, but is taking longer than planned.
We will update you when we have a solution.
Can you bump this topic rather than adding duplicated topics.

[SpeedPIC32]

Can you move this topic to the top instead of adding duplicate topics?

Sorry, I don't know how to do that.
I didn't know you could move a topic.
A little note saying that you were working on it would have been reassuring. I would have had time to test the changes. Would that be helpful?

Kind regards

[SpeedPIC32]

Based on the compiler output, the error is caused by a missing variable declaration for 'sysObj' in the generated C code. This usually happens when the Flowcode USB component's configuration or a required library is either not correctly set up or is missing.

Key Points

Error Source: The C compiler (xc32-gcc) reports an undeclared identifier error for the variable sysObj within the USB interrupt handlers (_IntHandlerUSBInstance0 and _IntHandlerUSBInstance0_USBDMA).

The Problem: The line DRV_USBHS_Tasks_ISR_USBDMA(sysObj.drvUSBObject); is trying to access a member (drvUSBObject) of a variable (sysObj) that was never defined. The sysObj variable is part of the Microchip Harmony framework and is essential for managing the USB hardware.

Likely Cause: This isn't a coding error on your part but rather an issue with the code generated by Flowcode. The Flowcode software either failed to generate the necessary code to declare the sysObj variable or is using an incorrect path for the Harmony framework files.

Recommended Actions

Check Flowcode USB Component Settings: Open your Flowcode project and carefully review the properties of your USB component. Ensure all settings related to the PIC32MZ2048EFH144 device and the CDC profile are correct.

Verify Harmony Framework Path: The compiler log shows the path to the Harmony framework: C:\microchip\harmony\v1_11. Confirm this is the correct and a valid path on your computer. If not, you may need to update the path within Flowcode's compiler settings.

Update/Reinstall Flowcode Libraries: The compiler output shows FlowcodeV9 in the include path (C:\ProgramData\MatrixTSL\FlowcodeV9\CAL\PIC32BIT\USB\CDC), but you're using Flowcode v10.1.2.40. This version mismatch is a strong indicator of the problem. Uninstalling and reinstalling Flowcode v10, or specifically updating the PIC32 libraries, is likely to resolve the issue.

[SpeedPIC32]

Hello,
I had Gemini examine the compiler message.
Do you use this tool as well?
It could lead to a solution more quickly.

Regards, SpeedPIC32

[SpeedPIC32]

Thanks to Gemini, the errors have been fixed.



Absolutely! I'm happy to summarize the steps we took to successfully compile your Flowcode project with the PIC32MZ and Microchip Harmony v1.11.

It was a complex process in which we resolved all issues in three main areas: **environment paths (batch file)**, **Harmony paths (compiler)**, and **Flowcode C code (CAL files)**.

---

## Steps successfully completed

Here is a chronological summary of the corrections that led to successful compilation:

### 1. Correction of the batch file environment (`PIC32compCDC.bat`)

The first step was to fix issues in the Flowcode compiler script file responsible for the PIC32 series.

* **Harmony path adjustment:** We set the environment variable `MX_HARMONY` in the batch file to the correct path **`C:\microchip\harmony\v1_11`**.
* **Missing Harmony compilation step:** We fixed the error that occurred when attempting to execute the directory `C:\microchip\harmony\v1_11\framework\usb\device\cdc` as a command. This was just an incorrectly logged command in the Flowcode script, but it blocked the compilation of the Harmony files. We made sure that the subsequent `xc32-gcc` commands, which actually compile the Harmony files, used the correct paths.

---

### 2. Correction of the Harmony include paths

Once the batch file had passed the Harmony paths correctly, we had to ensure that all header files could be found in order to successfully compile the Harmony source files.

* **Complete include list:** We added the necessary Harmony paths to the **`xc32-gcc`** command line to make all Harmony components (USB, system, drivers) available to the linker:
* `-IC:\microchip\harmony\v1_11`
* `-IC:\microchip\harmony\v1_11\framework`
* `-IC:\microchip\harmony\v1_11\framework\usb`
* `-IC:\microchip\harmony\v1_11\framework\usb\device\cdc`
* `-IC:\microchip\harmony\v1_11\framework\system`
* `-IC:\microchip\harmony\v1_11\framework\system\devcon`
* `-IC:\microchip\harmony\v1_11\framework\system\int`

---

### 3. Patch the Flowcode CAL C code (`PIC32BIT_CAL_USB_Serial.c`)

The last errors were internal inconsistencies in Flowcode's own hardware abstraction layer (CAL), which uses the Harmony libraries. These errors were fixed by manually correcting the file **`C:\ProgramData\MatrixTSL\FlowcodeV10\CAL\PIC32BIT\PIC32BIT\_CAL\_USB\_Serial.c`**:

* **`Initialise` (semicolon):** Removal of the misplaced semicolon from the `while` condition of the initialization function (line ~111).
* **`ReadString` (type conflict):** Changed the return type of the function `FC_CAL_USB_Serial_ReadString_1` from `MX_UINT16` to **`void`** (line ~284) to resolve a type conflict.
* **`ReadByte` (signature and variable): **
* The function **`FC_CAL_USB_Serial_ReadByte_1`** was adapted to the signature generated in the header (return type **`MX_UINT16`** and addition of the parameter **`MX_UINT8 timeout_ms`**) (line ~200).
* The missing return variable **`FCL_RETURN`** was **manually declared** in the function body (`MX_UINT16 FCL_RETURN;`) to fix the last error **`‘FCL_RETURN’ undeclared`** after Flowcode's macro failed to do so correctly.

**Result:** All these steps resulted in the compiler being able to process the entire code, including the Harmony libraries, without errors, triggering the linker step and displaying the final **`Compilation successful`** message.

Translated with DeepL.com (free version)