mfw issueshttps://gitlab.syscop.de/TOPCORE/mfw/-/issues2018-02-06T11:03:36Zhttps://gitlab.syscop.de/TOPCORE/mfw/-/issues/24rework hal_gpio in respect to proper unlocking of port funtions2018-02-06T11:03:36ZThorbjörn Jörgerrework hal_gpio in respect to proper unlocking of port funtionshttps://gitlab.syscop.de/TOPCORE/mfw/-/issues/23Check differences of DMA handling between TM4C123 and TM4C129 derivative2018-02-06T11:03:36ZMartin DoldCheck differences of DMA handling between TM4C123 and TM4C129 derivativeWithin issue #22 we applied a workaround to not use UART TX DMA. The output of the ticket was, that the DMA handling between TM4C123 and TM4C129 differs.
For now, it seems that only UART TX DMA is effected. But there might be further ...Within issue #22 we applied a workaround to not use UART TX DMA. The output of the ticket was, that the DMA handling between TM4C123 and TM4C129 differs.
For now, it seems that only UART TX DMA is effected. But there might be further issue, e.g. for our _hal_spi.c_ as this makes use of DMA too.
*TASK:* Check for the difference and fix accordingly!Martin DoldMartin Doldhttps://gitlab.syscop.de/TOPCORE/mfw/-/issues/19switch timeout functions from SystickHandler to pps driven2018-02-06T11:03:36ZThorbjörn Jörgerswitch timeout functions from SystickHandler to pps drivenhttps://gitlab.syscop.de/TOPCORE/mfw/-/issues/14Advance Protobuf Forwarder to forward bidirectional2018-02-06T11:03:36ZMartin DoldAdvance Protobuf Forwarder to forward bidirectionalThe Protobuf Forwarder shall be advanced s.t. messages from GS (e.g. betConf) can be forwarder by FC to FC-ARM.The Protobuf Forwarder shall be advanced s.t. messages from GS (e.g. betConf) can be forwarder by FC to FC-ARM.Martin DoldMartin Doldhttps://gitlab.syscop.de/TOPCORE/mfw/-/issues/13Implement UART using DMA2018-02-06T11:03:36ZMartin DoldImplement UART using DMAThe HAL UART implementation shall be updated to support UART DMA.The HAL UART implementation shall be updated to support UART DMA.Martin DoldMartin Doldhttps://gitlab.syscop.de/TOPCORE/mfw/-/issues/12Check all modifikators of type declarations2018-02-06T11:03:36ZThorbjörn JörgerCheck all modifikators of type declarationsAll local variables and functions should be declared static.<br>
All global variables/contexts/etc should be declared volatile.<br>
[Fun reading which mirrors our problems](http://www.barrgroup.com/Embedded-Systems/How-To/C-Volatile-Ke...All local variables and functions should be declared static.<br>
All global variables/contexts/etc should be declared volatile.<br>
[Fun reading which mirrors our problems](http://www.barrgroup.com/Embedded-Systems/How-To/C-Volatile-Keyword) xD @Martin.dold @evileli
Maybe this struct in [hal_uart.c](http://gitlab.syscop.de/highwind/embmasterdude/blob/develop/src/hal/hal_uart.c) is the problem. The pointers are declared volatile, but not the variables they are pointing to?
<pre>
#define UART_RX_DATA_BUF_SIZE 8192
#define UART_TX_DATA_BUF_SIZE 8192
#define IS_BUF_EMPTY(x, y) (x == y)
/*! Structure defining the context of an UART port. */
struct S_HAL_UART_CTX_T
{
uint32_t ui32_baseAddr;
volatile uint8_t ac_rxData[UART_RX_DATA_BUF_SIZE];
volatile uint8_t *pc_rxDataWrite;
volatile uint8_t *pc_rxDataRead;
volatile uint8_t ac_txData[UART_TX_DATA_BUF_SIZE];
volatile uint8_t *pc_txDataWrite;
volatile uint8_t *pc_txDataRead;
};
</pre>