Hi Fabio, that gets me a bit further - although I'm not too excited about the duplication between syscfg.yml and the linker script.
Anyway, further down the road I ran into an undefined function in the linker: stm32f3_flash_dev() 'turns out that got replaced with a global structure stm32_flash_dev - however, the global structure is not in any header file while the device specific (now non-existing) function declarations are still in the stm32f*_bsp.h I've adapted my bsp implementation accordingly so I can build it successfully again. Thanks for all the help, Markus On Wed, 09 Jan 2019 07:13:42 -0200 Fabio Utzig <ut...@apache.org> wrote: > Hi Markus, > > You may need to update your BSP's `syscfg.yml`, check one included > BSPs that has the same MCU that you're using for a complete list. > Your particular failure is that your `syscfg.yml` is missing a > "STM32_FLASH_SIZE_KB" entry. > > Best, > Fabio > > On Wed, Jan 9, 2019, at 4:30 AM, markus wrote: > > Hi Lukasz, > > > > did manually build newt and run into some build failures: > > > > ..... > > Compiling repos/apache-mynewt-core/hw/mcu/stm/stm32_common/src/ > > hal_gpio.c > > Error: In file included from > > repos/apache-mynewt-core/kernel/os/include/ os/mynewt.h:23:0, > > from > > repos/apache-mynewt-core/hw/mcu/stm/stm32_common/ > > src/hal_flash.c:21: > > bin/targets/spi/generated/include/syscfg/syscfg.h:15:49: error: > > 'MYNEWT_VAL_STM32_FLASH_SIZE_KB' undeclared here (not in a > > function); did you mean 'MYNEWT_VAL_STM32_FLASH_IS_LINEAR'? #define > > MYNEWT_VAL(x) MYNEWT_VAL_ ## x ^ > > repos/apache-mynewt-core/hw/mcu/stm/stm32_common/src/hal_flash.c:30:30: > > note: in expansion of macro 'MYNEWT_VAL' > > #define _FLASH_SIZE (MYNEWT_VAL(STM32_FLASH_SIZE_KB) * > > 1024) ^~~~~~~~~~ > > repos/apache-mynewt-core/hw/mcu/stm/stm32_common/src/hal_flash.c:64:16: > > note: in expansion of macro '_FLASH_SIZE' > > .hf_size = _FLASH_SIZE, > > ^~~~~~~~~~~ > > > > Anything else I should be doing? > > I also updated master again - just in case > > * master cb9ece042 hw/drivers/lps33thw: Restore > > read error stats > > > > Thanks again, > > Markus > > > > > > > > On Tue, 8 Jan 2019 07:05:11 +0100 > > Łukasz Rymanowski <lukasz.rymanow...@codecoup.pl> wrote: > > > > > Hi Markus, > > > > > > If master is used on mynewt-core then master branch of newt tool > > > should be used. Please try this and let us know of it works for > > > you > > > > > > Best > > > Lukasz > > > > > > > > > On Tue, Jan 8, 2019, 06:18 markus <mar...@bibi.ca wrote: > > > > > > > 'been away for a few months and I can't build my projects > > > > anymore. I updated repos/apache-mynewt-core to the latest > > > > master branch (59912fc02) and it seems I'm running the latest > > > > newt tool, 1.5.0 > > > > > > > > Executing `newt build ...` gives me an error for each package in > > > > apache-mynewt-core: > > > > > > > > * Warning: Parsing pkg @apache-mynewt-core/boot/boot_serial > > > > config: strconv.ParseInt: parsing > > > > "MYNEWT_VAL(BOOT_SERIAL_SYSINIT_STAGE_MAIN)": invalid syntax; > > > > ignoring package. > > > > > > > > > > > > I couldn't find anything in the release notes - any clues as to > > > > what I'm doing wrong would be much appreciated. > > > > > > > > Thanks, > > > > Markus > > > > > >
