Hello,
Looking into the reference, STM32F072 has 8 endpoints, which could lead to three CDC devices (with one endpoint free), which is tempting.
I took USB_CDC_IAD demo from testhal/STM32F3xx and it's working fine, as far I could tell (did just quick tests), so full of optimism, I tried to fiddle ...
Search found 6 matches
- Sat Nov 11, 2017 10:04 am
- Forum: ChibiOS/HAL
- Topic: Triple USB-CDC (on STM32F072)
- Replies: 1
- Views: 2721
- Sun Jun 26, 2016 6:05 pm
- Forum: ChibiStudio
- Topic: Chibi Eclipse plugin not working under Eclipse Neon
- Replies: 17
- Views: 18295
Re: Chibi Eclipse plugin not working under Eclipse Neon
I have installed standard edition "for C/C++ developers"
installed features:
org.eclipse.cdt (9.0.0.201606062011) "Eclipse C/C++ Development Tools"
org.eclipse.cdt.build.crossgcc (9.0.0.201606062011) "CDT GCC Cross Compiler Support"
org.eclipse.cdt.gdb (9.0.0.201606062011) "GDB Common"
org.eclipse ...
installed features:
org.eclipse.cdt (9.0.0.201606062011) "Eclipse C/C++ Development Tools"
org.eclipse.cdt.build.crossgcc (9.0.0.201606062011) "CDT GCC Cross Compiler Support"
org.eclipse.cdt.gdb (9.0.0.201606062011) "GDB Common"
org.eclipse ...
- Fri Jun 24, 2016 5:44 pm
- Forum: ChibiStudio
- Topic: Chibi Eclipse plugin not working under Eclipse Neon
- Replies: 17
- Views: 18295
Chibi Eclipse plugin not working under Eclipse Neon
Cannot complete the install because one or more required items could not be found.
Software being installed: ChibiOS Eclipse Tools 2.3.0.201603121101 (org.chibios.eclipse.tools.feature.feature.group 2.3.0.201603121101)
Missing requirement: ChibiOS Eclipse Tools 2.3.0.201603121101 (org.chibios ...
- Tue Jun 21, 2016 8:15 pm
- Forum: ChibiOS/HAL
- Topic: STM32F0 and others: Hardware Modbus support
- Replies: 4
- Views: 5388
STM32F0 and others: Hardware Modbus support
Greetings,
I was implementing hardware modbus support on STM32F072 because somehow I messed Virtual Timers (for idle detection) beyond point of return.
I succeded, but run into some obstackles:
1) No API for setting RTOR register, workarounded by UARTD2.usart->RTOR |= MODBUS_15SPACE_BITS;
2 ...
I was implementing hardware modbus support on STM32F072 because somehow I messed Virtual Timers (for idle detection) beyond point of return.
I succeded, but run into some obstackles:
1) No API for setting RTOR register, workarounded by UARTD2.usart->RTOR |= MODBUS_15SPACE_BITS;
2 ...
- Mon Jun 20, 2016 3:59 pm
- Forum: ChibiOS/HAL
- Topic: PAL : GPIO output default state is high?
- Replies: 3
- Views: 6337
Re: PAL : GPIO output default state is high?
Hi,
default state is set in board.h (you can change this state through palSetXXX, palClearXXX or palWriteXXX).
BY the way, if you have to change pad mode in certain point of you application palSetPadMode() is the right API. If you have to set up the whole board just once (like a kind of ...
default state is set in board.h (you can change this state through palSetXXX, palClearXXX or palWriteXXX).
BY the way, if you have to change pad mode in certain point of you application palSetPadMode() is the right API. If you have to set up the whole board just once (like a kind of ...
- Mon Jun 20, 2016 1:51 pm
- Forum: ChibiOS/HAL
- Topic: PAL : GPIO output default state is high?
- Replies: 3
- Views: 6337
PAL : GPIO output default state is high?
Hello,
I have strange behaviour on STM32F072 MCU, when setting pin to push/pull output.
I was expecting logical Low as default state (and according reference manual and StdPeriph sample it should be), but pins have high state.
It is intended, it's a bug, or bad code?
Sample code:
palSetPadMode ...
I have strange behaviour on STM32F072 MCU, when setting pin to push/pull output.
I was expecting logical Low as default state (and according reference manual and StdPeriph sample it should be), but pins have high state.
It is intended, it's a bug, or bad code?
Sample code:
palSetPadMode ...