ChibiOS Free Embedded RTOS

Did you check devcfg registers? The configuration might be incorrect for your device. The configuration bits seems to be compatible between 2xx and 7xx.
Also did you set correctly the frequency of the core in mcuconf? Also on 1xx/2xx shadow registers are not present.

I trying MIPS32 port (latest) on PIC32MX250F128B. Family 3xx/4xx/5xx has a few differences compared to the 1xx/2xx, for example the register AD1PCFG for set digital/analog I/O is not present, but there are ANSELA and ANSELB. There's always a mess around analog inputs in PIC MCUs. Can you share the ...

Hi etmatrix, thank for testing the port and sharing the LD scripts. I'll try to make a basic template for the linker scripts and make the demo define only some offsets and sizes. I attached my linkers script they should be correct, but my demo application (USB-CDC) don't run on my PIC32MX What do yo...

Few updates: PIC32: PWM LLD the PIC HW is a "bit" odd in terms that it does not generate interrupt on compare in PWM mode, so no such events supported the other mode of Output Compare module is promising but I can't get expected output so I'll try to find an oscilloscope to continue with i...

Shame on me, the frequency defined in PWM configuration is ought to be underneath timer frequency, not PWM frequency. I misread the configuration. This makes things clear though it forces the user to read the spec of the MCU anyway to define the correct period. For instance for PIC32 it makes follow...

Maybe I'm raising so stupid questions because I'm trying to fit PIC32's PWM HW into PWM HAL model which was designed for completely different HW.

Thanks Giovanni for the explanation. I would disagree about #define pwmChangeChannellDutyCycle pwmEnableChannel as you may have more code there than needed to change the duty cycle or even worth the code is not suitable for that purpose. pwmEnableChannel states to enable channel and set duty cycle. ...

Hi etmatrix, I'm using prebuilt toolchain from mips.com(mips-sde-elf-gcc (GCC) 4.4.6) but there should not be any difference between native build of the toolchain and binary delivery. I noticed some performance regression with gcc 4.6(or 4.7 don't remember exactly) so pay attention there. Be careful...

Also it's a bit confusing to change the period as you change frequency and duty cycle with the call to pwmChangePeriod. Or the driver should internally recalculate the width accordingly ...

But only by means of pwmEnableChannel. There should be pwmChangeWidth and pwmChangeFrequency. IMHO exposing pulse width in ticks is not portable. I can't run same code on different devices, or worse with different generations. Say, I have 8-bit timer associated with PWM and at some point I need bett...