Yes, I think the SRAM mapped case should be an option, but selected by default. Anyway, something must be pushed along the STM32F0 basic support. Neil

Hi Neal, 2017-09-13 14:10 GMT+02:00 Neil Armstrong <narmstrong@...>: There are use cases where you really do not need the dynamic updates (mine for example - updates are done by the supervising

As there is no response from Baohong I will assume it is relative value. Assuming that, I have few questions about types used for functions that perform some waiting or set alarms. Shouldn't we stay

Exact Yes it should, then it should disable all the dynamic update and generation of the vector table.

Hi Neal, I had a look at the linker script https://github.com/zephyrproject-rtos/zephyr/blob/master/include/arch/arm/cortex_m/scripts/linker.ld which is also used for STM32F0. Transfer of the vector

I have to link a static precompiled library This is my directory tree: . |-- MyApp | `-- src | `-- GUI_glue | |-- Config | `-- OS |-- STemWin | |-- inc | `-- Lib `--

Hi, I created a port of NFFS (Newtron Flash File System) for Zephyr - see https://github.com/zephyrproject-rtos/zephyr/pull/1288. NFFS is the filesystem created and used by Apache Mynewt

Hi, Since Cortex-M0 cannot relocate the vector base with a processor register, the vector must be moved. Yes you can map the first kbytes of the flash to the first 32k bytes of 0, but you won't tun

Hi, a new release candidate of the SDK has been released at: https://github.com/zephyrproject-rtos/meta-zephyr-sdk/releases/tag/0.9.2-rc4 This is has a fix for openocd which did not work

Hi Neil, the patch forces the STM32F0 vector table to be in SRAM as CONFIG_FLASH_BASE_ADDRESS and CONFIG_SRAM_BASE_ADDRESS are not 0. I would appreciate to save precious SRAM and do the remap only if

I am currently trying to build an application on Zephyr and my application requires the current time and date. I realized I cannot call functions from the time.h C library since the time.h in the

Second update of Watchdog API RFC. https://github.com/zephyrproject-rtos/zephyr/pull/1260 Michał Kruszewski Sent with ProtonMail Secure Email.

Hi Maciej, Bobby, Could test the following patch ? If it works, it's the correct way to handle this situation, and should be included in the stm32f0 support

Hi All, On STM32F0 SoCs, the forst 32K cam be remapped to an internal SRAM, but this must be done *before* the relocate_vector_table() call. I will push a patch to add a relocate hook for Cortex-M0

Hi All, I have some concern about this commit eb48a0a73c11c2a9cd4c3c91864ca4e0cf52dae8 (arm: armv6-m: Support relocating vector table). On STM32, flash is not at address 0, but can be relocated like

For those of you using pyocd to debug, please give the following PR a try: https://github.com/mbedmicro/pyOCD/pull/333 You’ll need to build pyocd from source, which isn’t too hard, and enable

This was done already

Hi Andrew, Will you update the Getting Started guides to include the package in the command-line instructions? Thanks, Carles From:<zephyr-devel-bounces@...> on behalf of "Boie,

Now that the merge window is open and we are working towards 1.10, we have a new host system dependncy: gperf. It is a tool that has existed for a long time, it generates C code that implements

Hi, We are pleased to announce the release of Zephyr v1.9.0. Major enhancements planned with this release include: Bluetooth 5.0 Support (all features except Advertising Extensions) Bluetooth