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
PIC32 USB CDC Error
-
- Posts: 280
- http://meble-kuchenne.info.pl
- Joined: Thu Dec 10, 2020 2:35 pm
- Location: Germany
- Has thanked: 37 times
- Been thanked: 17 times
-
- Posts: 280
- Joined: Thu Dec 10, 2020 2:35 pm
- Location: Germany
- Has thanked: 37 times
- Been thanked: 17 times
Re: PIC32 USB CDC Error
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
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
-
- Posts: 280
- Joined: Thu Dec 10, 2020 2:35 pm
- Location: Germany
- Has thanked: 37 times
- Been thanked: 17 times
Re: PIC32 USB CDC Error
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
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
-
- Matrix Staff
- Posts: 2097
- Joined: Wed Dec 02, 2020 11:07 pm
- Has thanked: 650 times
- Been thanked: 705 times
Re: PIC32 USB CDC Error
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.
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.
Martin
-
- Posts: 280
- Joined: Thu Dec 10, 2020 2:35 pm
- Location: Germany
- Has thanked: 37 times
- Been thanked: 17 times
Re: PIC32 USB CDC Error
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
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
-
- Posts: 280
- Joined: Thu Dec 10, 2020 2:35 pm
- Location: Germany
- Has thanked: 37 times
- Been thanked: 17 times
Re: PIC32 USB CDC Error
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.
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.
-
- Posts: 280
- Joined: Thu Dec 10, 2020 2:35 pm
- Location: Germany
- Has thanked: 37 times
- Been thanked: 17 times
Re: PIC32 USB CDC Error
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
I had Gemini examine the compiler message.
Do you use this tool as well?
It could lead to a solution more quickly.
Regards, SpeedPIC32