Hi,
i am using the STM32F769. The initialized variables are linked to ram0 (alias DATA_RAM) and not initialized variables are linked to ram3 (alias BSS_RAM) which are different as the mapping is as follows:
ram0 : org = 0x20020000, len = 384k /* SRAM1 + SRAM2 */
ram1 : org = 0x20020000 ...
Search found 137 matches
- Thu Oct 04, 2018 9:48 am
- Forum: General Support
- Topic: variable mapping for STM32F769
- Replies: 1
- Views: 2906
- Wed Oct 11, 2017 6:51 am
- Forum: Small Change Requests
- Topic: STM32 LLD for UART with bus idle detection
- Replies: 4
- Views: 7437
Re: STM32 LLD for UART with bus idle detection
Hi,
is this item on track? I whould appreciate this feature.
is this item on track? I whould appreciate this feature.
- Tue Aug 15, 2017 1:39 pm
- Forum: ChibiOS/HAL
- Topic: STM32F7 hal_lld - STM32_LSEDRV
- Replies: 2
- Views: 3737
Re: STM32F7 hal_lld - STM32_LSEDRV
OK, i think my version is not the newest. It's not generated. I have to update the toolchain. Nevertheless the STM32_LSEDRV is checked for STM32_LSE_ENABLED with other ports (STM32F3).
Thanks
Thanks
- Tue Aug 15, 2017 11:40 am
- Forum: ChibiOS/HAL
- Topic: STM32F7 hal_lld - STM32_LSEDRV
- Replies: 2
- Views: 3737
STM32F7 hal_lld - STM32_LSEDRV
Hi,
i do not use the LSE. So i disabled it in mcuconf.h. Futhermore i do not define STM32_LSEDRV in board.h because i do not need it. The problem is now that the percompiler throws an error in hal_lld.h because the error check is not within #if STM32_LSE_ENABLED as implemented in the hal_lld.h of ...
i do not use the LSE. So i disabled it in mcuconf.h. Futhermore i do not define STM32_LSEDRV in board.h because i do not need it. The problem is now that the percompiler throws an error in hal_lld.h because the error check is not within #if STM32_LSE_ENABLED as implemented in the hal_lld.h of ...
- Thu Jun 22, 2017 9:53 am
- Forum: Development and Feedback
- Topic: HAL Driver for STM32 DFSDM driver
- Replies: 13
- Views: 14474
Re: HAL Driver for STM32 DFSDM driver
Hi,
what is the status of this task?
what is the status of this task?
- Mon Jun 12, 2017 3:17 pm
- Forum: General Support
- Topic: Chibi Function Types
- Replies: 1
- Views: 2747
Chibi Function Types
Hi,
where is the documentation of the function types like i-class function or s-class? Which function are used in which context? I can't find that.
Thanks
where is the documentation of the function types like i-class function or s-class? Which function are used in which context? I can't find that.
Thanks
- Wed May 24, 2017 3:29 pm
- Forum: Bug Reports
- Topic: DMA init
- Replies: 1
- Views: 2872
DMA init
Hi,
in the DMA init function in file stm32_dma.c is the following code snippet:
void dmaInit(void) {
unsigned i;
dma_streams_mask = 0U;
for (i = 0U; i < STM32_DMA_STREAMS; i++) {
_stm32_dma_streams[i].stream->CR = 0U;
dma_isr_redir[i].dma_func = NULL;
}
DMA1->LIFCR ...
in the DMA init function in file stm32_dma.c is the following code snippet:
void dmaInit(void) {
unsigned i;
dma_streams_mask = 0U;
for (i = 0U; i < STM32_DMA_STREAMS; i++) {
_stm32_dma_streams[i].stream->CR = 0U;
dma_isr_redir[i].dma_func = NULL;
}
DMA1->LIFCR ...
- Wed May 24, 2017 3:24 pm
- Forum: Bug Reports
- Topic: Dependency to kernel in uart lld
- Replies: 2
- Views: 4033
Dependency to kernel in uart lld
Hi,
there is a call to chDbgAssert in the UARTV1 lld source file. This has to be osalDbgAssert, isn't it?
Thanks
there is a call to chDbgAssert in the UARTV1 lld source file. This has to be osalDbgAssert, isn't it?
Thanks
- Mon May 15, 2017 8:01 am
- Forum: Small Change Requests
- Topic: adcSTM32EnableTS differences between ADCv2 and ADCv3
- Replies: 1
- Views: 3599
adcSTM32EnableTS differences between ADCv2 and ADCv3
Hi,
why the amount of parameter of adcSTM32EnableTS is different in ADCv2 and ADCv3?
ADCv3:
adcSTM32EnableTS(ADCDriver *adcp)
and ADCv2:
void adcSTM32EnableTSVREFE(void)
ADCv3 has two different CCR, but the temperature sensor is always connected to ADC1, isn't it? So the pointer to ...
why the amount of parameter of adcSTM32EnableTS is different in ADCv2 and ADCv3?
ADCv3:
adcSTM32EnableTS(ADCDriver *adcp)
and ADCv2:
void adcSTM32EnableTSVREFE(void)
ADCv3 has two different CCR, but the temperature sensor is always connected to ADC1, isn't it? So the pointer to ...
- Mon Apr 24, 2017 8:38 am
- Forum: Bug Reports
- Topic: RTC callback setter
- Replies: 3
- Views: 4915
Re: RTC callback setter
So i have to define RTC_SUPPORTS_CALLBACKS to FALSE that the call rtc_lld_set_callback is not implemented and use EXT instead?