Search found 14488 matches
- Sun Sep 08, 2024 6:58 pm
- Forum: Development and Feedback
- Topic: Further Raspberry Pi RP2xxx development on pico-sdk
- Replies: 2
- Views: 84
Re: Further Raspberry Pi RP2xxx development on pico-sdk
Hi, There are 2 main problems with the SDK on top of my mind: 1) Naming of types conflicting with OSAL and chibios in general, see semaphore_t but there are others. 2) Bad practice of inclusions with relative paths. This is why my preferred way is to use CMSIS files, if official ones are insufficien...
- Thu Sep 05, 2024 3:19 pm
- Forum: Open Discussion about the Commercial Options
- Topic: STM32h743ZI2 ETH not work
- Replies: 3
- Views: 76
Re: STM32h743ZI2 ETH not work
Creating board files is quite common, you may try guides on http://www.playembedded.org it is not something we can handle over the forum.
You may also try to ask on our Discord server and see if there is somebody willing to help you: https://discord.gg/s8b8v7VtrM
Giovanni
You may also try to ask on our Discord server and see if there is somebody willing to help you: https://discord.gg/s8b8v7VtrM
Giovanni
- Thu Sep 05, 2024 2:56 pm
- Forum: Open Discussion about the Commercial Options
- Topic: STM32h743ZI2 ETH not work
- Replies: 3
- Views: 76
Re: STM32h743ZI2 ETH not work
Hi,
Perhaps the board is different from the one used in the demo (which is old), probably there are differences and board files should be adjusted with changes.
I would verify GPIO settings related to PHY connections.
Giovanni
Perhaps the board is different from the one used in the demo (which is old), probably there are differences and board files should be adjusted with changes.
I would verify GPIO settings related to PHY connections.
Giovanni
- Wed Aug 28, 2024 12:20 pm
- Forum: Bug Reports
- Topic: LWIP: bug in sys_now Topic is solved
- Replies: 12
- Views: 5967
Re: LWIP: bug in sys_now Topic is solved
Committed with a small change, incredible how such a minor thing can impact code size so much: #if (OSAL_ST_FREQUENCY < 1000) || ((OSAL_ST_FREQUENCY % 1000) != 0) #error "LWIP requires a systick frequency that is a multiple of 1000" #endif #if (OSAL_ST_RESOLUTION >= 32) && (OSAL_ST...
- Tue Aug 27, 2024 9:42 am
- Forum: Bug Reports
- Topic: LWIP: bug in sys_now Topic is solved
- Replies: 12
- Views: 5967
Re: LWIP: bug in sys_now Topic is solved
Any feedback?
Giovanni
Giovanni
- Tue Aug 27, 2024 9:41 am
- Forum: Bug Reports
- Topic: Incorrect SerialDriver instance use for UART9 init in USARTv3/hal_serial_lld.c Topic is solved
- Replies: 3
- Views: 2021
Re: Incorrect SerialDriver instance use for UART9 init in USARTv3/hal_serial_lld.c Topic is solved
Hi,
Fixed in trunk and stable.
Giovanni
Fixed in trunk and stable.
Giovanni
- Mon Aug 26, 2024 2:03 pm
- Forum: ChibiOS/RT
- Topic: Thread sleeping, wakeup on Mailbox or Event
- Replies: 3
- Views: 2002
Re: Thread sleeping, wakeup on Mailbox or Event
Events are meant to be the "or" mechanism.
Giovanni
Giovanni
- Mon Aug 26, 2024 1:38 pm
- Forum: ChibiOS/RT
- Topic: Thread sleeping, wakeup on Mailbox or Event
- Replies: 3
- Views: 2002
Re: Thread sleeping, wakeup on Mailbox or Event
Hi,, Just wait for events, and make a "message incoming" event, when you get the event then you fetch from the mailbox using TIME_IMMEDIATE (no wait). On the sender side send both the event and the message atomically. chSysLock() chEvtBroadcastFlagsI() chMBPostTimeoutS() chSysUnlock() Giov...
- Mon Aug 26, 2024 6:26 am
- Forum: STM32 Support
- Topic: GPT Driver dynamic period
- Replies: 3
- Views: 2078
Re: GPT Driver dynamic period
The periodic callback is just that, periodic.
The other callback is called on the deactivation front of a PWM channel, on CCR match.
Giovanni
The other callback is called on the deactivation front of a PWM channel, on CCR match.
Giovanni
- Sun Aug 25, 2024 6:36 pm
- Forum: STM32 Support
- Topic: GPT Driver dynamic period
- Replies: 3
- Views: 2078
Re: GPT Driver dynamic period
Hi,
Changing period is not immediate, it is "taken" on the next ARR match, probably this is what you are experiencing. You should consider doing a custom driver if you find yourself manipulating registers directly.
Giovanni
Changing period is not immediate, it is "taken" on the next ARR match, probably this is what you are experiencing. You should consider doing a custom driver if you find yourself manipulating registers directly.
Giovanni