ChibiOS Free Embedded RTOS

I need an interrupt for when H10, H11, H12, and I0 go high. Would I use the EXT driver with a config structure like this?


static const EXTConfig extHcfg = {
{
{EXT_CH_MODE_RISING_EDGE | EXT_CH_MODE_AUTOSTART | EXT_MODE_GPIOI, motScb},
{EXT_CH_MODE_DISABLED, NULL},
{EXT_CH_MODE_DISABLED, NULL ...

Does anyone know of a way to set up an interrupt to trigger when a certain pin is high? I don't see predefined functions for this in the HAL drivers. Any help is appreciated. Thank you in advance!!

I have determined that my application is halting on this same assert, but I am not sure where APB1 and 2 are set, and there is nothing about APB in mcuconf. Could someone please point me to where I can see the frequency of these? Thank you!

Hi everyone,

I was wondering if there is a straightforward way now to set the bits in the CR1 register for TIM3 and TIM4 on STM32F4, or should I just do:

TIM4->CR1 |= ... ?

Also wondering what the defaults are for CR1. Thank you!!

In trying to get mailboxes working I wrote a basic application with two threads, one that posted a message every 100ms and one in a while(TRUE) loop that just fetched and toggled the status LED when there was a message. What I found was that it only worked if I had a loop (while(TRUE ...

The only code for USB before I attempt the chnWriteTimeout() is in that setup function I've posted here. I'm not able to transmit data because the usbp state is never changed from USB_READY to USB_ACTIVE. I'm wondering if I'm missing something that I should be doing after the usb_setup functions and ...

Your code waits for the USB to be ready, not active, though - right? At the point in the code where it's returning, the states are USB_READY and SDU_READY when they should be USB_ACTIVE and SDU_READY.

Hi there,

I am trying to transmit data using the HAL Serial over USB Driver on an STM32F4. I am watching the value of sdup->config->usbp->state in gdb and have found that the application is returning at line 158 of serial_usb.c as shown below because sdup->config->usbp->state is USB_READY not USB ...

Found it! Thanks a ton

Hi Giovanni,

Thanks for the response. I don't see where this is documented in the reference manual -- could you please point me there? I am looking here: http://chibios.sourceforge.net/html/group___s_p_i.html

Thanks so much!