ChibiOS Free Embedded RTOS

The STM32F37 was the right idea. But this driver is written for the adc and sdadc. The STM32F7 has 3 standard ADCv1 i think and the DFSDM supplying 4 "addtional ADCs" just making a new revision of the ADC driver just to add this, is not the right way think. Cause the DFSDM needs a differen...

The normal and standard use case is to feed a 1 Bit datastream via the IO Pins from a 2. order Delta sigma modulator, such as AMC1204. But ST has the option to feed the Filter with a 16Bit wide stream via DMA, but XMC and TI don't support this kind of usage, so i consider the software input to the f...

Yes i only changed the clock tree configuration and according defines. Next will be the registry. in terms of api the ADC api fits quite good. Events like short circuit or analog watchdog can be handled by custom callbacks. maybe it is useful to configure and handle each Filter (stm has 4 of them, a...

Hi Giovanni, i would say it could be a new HAL component, cause XMC4xxx have nearly the same peripheral called DSD. Basicly both supply digital SINC filters, inputs and output clock for delta sigma modulators, which are basicly ADCs supplying a 1Bit datastream at up to 20MHz samplerate. In the C2000...

Hi all, has anybody already written a hal driver for the DFSDM peripheral in the newer STMs? If not i will share my work here. I started with the ADCv3 driver as a base and i am willing to implement nearly the same api as an ADC. The custom board that i am writing this for is based on a STM32F767VI ...

+1

Just as an info. I activated rt in my Project even if i dont need it actually, but USB CDC is stable on STM32F3 with rt but not with os-less.

Hi All, i am running USB CDC also with the os-less hal but on a STM32F303, so far it works with just changing usbcfg.c to calling osal functions instead of ch.. api. But when USB CDC runs for a while (5min) i got struck in a hardfault. In the Usage Fault Register the bit INVSTATE is set. for me it s...

No Problem, why this crap half duplex comunication is getting me framing errors i dont know, but with an other device sending the requests every thing works fine. So i just leave it to handle the error in rxerror callback by reading RDR if RXNE is set and call the rxchar manually. Even if i cut the ...

Ok i investigated a little deeper. seems i am getting framing errors. But when the rxerr callback was called with the error the byte gets lost. So i read the RDR in the Error handler and call the rxchar callback from there when RXNE Bit in ISR was set.