Thank you for the quick reply!
No, I don't think it is from AC coupling noise.
I ran the STM32Cube example "Audio_playback_and_record", which is basically an OTG host based device, reading from a memory thumb drive "audio_sample.wav", without any noise, very clean. This is a bare-metal application ...
Search found 9 matches
- Sat Dec 05, 2020 7:28 pm
- Forum: STM32 Support
- Topic: Usage of USB driver in isochronous mode (STM32)
- Replies: 24
- Views: 43986
- Fri Dec 04, 2020 8:24 pm
- Forum: STM32 Support
- Topic: Usage of USB driver in isochronous mode (STM32)
- Replies: 24
- Views: 43986
Re: Usage of USB driver in isochronous mode (STM32)
Hello,
I understand this is an older thread, I have migrated this project to Chibi20.3 on stm32f4 discovery board I have. I've connected MCLK to ITR of TIM2 using a jumper wire for samplerate feedback, as discussed in earlier posts.
On building and running, I am able to get usb audio device ...
I understand this is an older thread, I have migrated this project to Chibi20.3 on stm32f4 discovery board I have. I've connected MCLK to ITR of TIM2 using a jumper wire for samplerate feedback, as discussed in earlier posts.
On building and running, I am able to get usb audio device ...
- Wed Feb 06, 2019 7:06 pm
- Forum: STM32 Support
- Topic: SysTick ISR not firing
- Replies: 2
- Views: 4018
Re: SysTick ISR not firing
Thank you, that worked for me.
chSysInit() is the case when RT is built, calls chSysEnable() which will then enable interrupts globally.
For os-less, since chSysInit() is out of the picture, osalSysEnable() was needed to be called after halInit() which enables the global interrupts.
chSysInit() is the case when RT is built, calls chSysEnable() which will then enable interrupts globally.
For os-less, since chSysInit() is out of the picture, osalSysEnable() was needed to be called after halInit() which enables the global interrupts.
- Wed Feb 06, 2019 1:02 am
- Forum: STM32 Support
- Topic: SysTick ISR not firing
- Replies: 2
- Views: 4018
SysTick ISR not firing
Hello All,
Following is my setup:
ChibiOS 18.2.0: os-less
Board: Nucleo144-STM32L496ZG
SYSCLOCK: 80MHz, HSE is enabled, 16MHz Crystal.
Osal tick frequency:
#define OSAL_ST_FREQUENCY 1000
On creating an os-less project, I am unable to get SysTick interrupts. I checked the core peripheral registers ...
Following is my setup:
ChibiOS 18.2.0: os-less
Board: Nucleo144-STM32L496ZG
SYSCLOCK: 80MHz, HSE is enabled, 16MHz Crystal.
Osal tick frequency:
#define OSAL_ST_FREQUENCY 1000
On creating an os-less project, I am unable to get SysTick interrupts. I checked the core peripheral registers ...
- Tue Oct 23, 2018 8:32 pm
- Forum: Development and Feedback
- Topic: Additional Simulator Posix HAL LLD drivers
- Replies: 10
- Views: 36730
Re: Additional Simulator Posix HAL LLD drivers
Hi,
I have attached the patch with HAL_RTC_LLD test example also. Please download this updated patch and experiment. It includes the drivers and the examples.
Test application locations:
1) HAL_SERIAL_LLD : $(CHIBIOS)/demos/various/RT-Posix-Simulator
2) HAL_CAN_LLD : $(CHIBIOS)/testhal/simulator ...
I have attached the patch with HAL_RTC_LLD test example also. Please download this updated patch and experiment. It includes the drivers and the examples.
Test application locations:
1) HAL_SERIAL_LLD : $(CHIBIOS)/demos/various/RT-Posix-Simulator
2) HAL_CAN_LLD : $(CHIBIOS)/testhal/simulator ...
- Sat Oct 20, 2018 12:30 am
- Forum: Development and Feedback
- Topic: Additional Simulator Posix HAL LLD drivers
- Replies: 10
- Views: 36730
Re: Additional Simulator Posix HAL LLD drivers
Faisal has explained the overview well. Thanks
I have added following example projects with README that explains usage scenarios:
1) HAL_SERIAL_LLD : $(CHIBIOS)/demos/various/RT-Posix-Simulator
2) HAL_CAN_LLD : $(CHIBIOS)/testhal/simulator/posix/CAN
3) HAL_UART_LLD : $(CHIBIOS)/testhal/simulator ...
I have added following example projects with README that explains usage scenarios:
1) HAL_SERIAL_LLD : $(CHIBIOS)/demos/various/RT-Posix-Simulator
2) HAL_CAN_LLD : $(CHIBIOS)/testhal/simulator/posix/CAN
3) HAL_UART_LLD : $(CHIBIOS)/testhal/simulator ...
- Thu Oct 18, 2018 6:58 pm
- Forum: Development and Feedback
- Topic: Additional Simulator Posix HAL LLD drivers
- Replies: 10
- Views: 36730
Additional Simulator Posix HAL LLD drivers
Hello,
We have developed/modified a few lld drivers to use in simulator posix environment taking inspiration from STM32:
1) HAL_CAN_LLD (Uses SocketCAN)
2) HAL_SERIAL_LLD (added TTY/PTS support)
3) HAL_UART_LLD (uses TTY/PTS)
4) HAL_RTC_LLD
Also added a "simulator_registry.h" for these peripherals ...
We have developed/modified a few lld drivers to use in simulator posix environment taking inspiration from STM32:
1) HAL_CAN_LLD (Uses SocketCAN)
2) HAL_SERIAL_LLD (added TTY/PTS support)
3) HAL_UART_LLD (uses TTY/PTS)
4) HAL_RTC_LLD
Also added a "simulator_registry.h" for these peripherals ...
- Fri Jul 06, 2018 11:52 pm
- Forum: Bug Reports
- Topic: Alignment reuirement for memory pools
- Replies: 2
- Views: 4328
Alignment reuirement for memory pools
Hi All,
I have a memory pool object and associated object memory aligned to stkalign_t as well as another pool and associated object memory without any alignment.
On looking at the source code of ChibiOS, I see chPoolAdd() is called by chPoolLoadArray() on loading both above pools after their ...
I have a memory pool object and associated object memory aligned to stkalign_t as well as another pool and associated object memory without any alignment.
On looking at the source code of ChibiOS, I see chPoolAdd() is called by chPoolLoadArray() on loading both above pools after their ...
- Sat Jan 27, 2018 3:45 am
- Forum: Bug Reports
- Topic: Potential Design Pattern bug in Chibi Abstract peripheral interfaces
- Replies: 11
- Views: 9914
Potential Design Pattern bug in Chibi Abstract peripheral interfaces
Hi All,
We are working on writing external device drivers for certain Accelerometers/Gyros and Magnetometers using the abstract peripheral interface. While going through the design pattern(object oriented C having virtual function implementations), I found a potential flaw in the design pattern ...
We are working on writing external device drivers for certain Accelerometers/Gyros and Magnetometers using the abstract peripheral interface. While going through the design pattern(object oriented C having virtual function implementations), I found a potential flaw in the design pattern ...