playing with micro-sd from hobbytronics, returned to a nano to test it works, ok albeit at SPI_QUARTER_SPEED
so pointed sketchbook to sketchbook_stm32 for Arduino_STM32, compiled for a red/blue pill and got
Warning: platform.txt from core ‘Arduino ARM (32-bits) Boards’ contains deprecated recipe.c.combine.pattern=”{compiler.path}{compiler.c.elf.cmd}” {compiler.c.elf.flags} -mcpu={build.mcu} “-T{build.variant.path}/{build.ldscript}” “-Wl,-Map,{build.path}/{build.project_name}.map” {compiler.c.elf.extra_flags} -o “{build.path}/{build.project_name}.elf” “-L{build.path}” -mthumb -Wl,–cref -Wl,–check-sections -Wl,–gc-sections -Wl,–entry=Reset_Handler -Wl,–unresolved-symbols=report-all -Wl,–warn-common -Wl,–warn-section-align -Wl,–warn-unresolved-symbols -Wl,–start-group “{build.path}/syscalls_sam3.c.o” {object_files} “{build.variant.path}/{build.variant_system_lib}” “{build.path}/{archive_file}” -Wl,–end-group -lm -gcc, automatically converted to recipe.c.combine.pattern=”{compiler.path}{compiler.c.elf.cmd}” {compiler.c.elf.flags} -mcpu={build.mcu} “-T{build.variant.path}/{build.ldscript}” “-Wl,-Map,{build.path}/{build.project_name}.map” {compiler.c.elf.extra_flags} -o “{build.path}/{build.project_name}.elf” “-L{build.path}” -mthumb -Wl,–cref -Wl,–check-sections -Wl,–gc-sections -Wl,–entry=Reset_Handler -Wl,–unresolved-symbols=report-all -Wl,–warn-common -Wl,–warn-section-align -Wl,–warn-unresolved-symbols -Wl,–start-group “{build.path}/core/syscalls_sam3.c.o” {object_files} “{build.variant.path}/{build.variant_system_lib}” “{build.path}/{archive_file}” -Wl,–end-group -lm -gcc. Consider upgrading this core.
Warning: platform.txt from core ‘Arduino ARM (32-bits) Boards’ contains deprecated recipe.ar.pattern=”{compiler.path}{compiler.ar.cmd}” {compiler.ar.flags} {compiler.ar.extra_flags} “{build.path}/{archive_file}” “{object_file}”, automatically converted to recipe.ar.pattern=”{compiler.path}{compiler.ar.cmd}” {compiler.ar.flags} {compiler.ar.extra_flags} “{archive_file_path}” “{object_file}”. Consider upgrading this core.
Warning: platform.txt from core ‘STM32 Boards (STM32duino.com)’ contains deprecated compiler.path={runtime.ide.path}/hardware/tools/gcc-arm-none-eabi-4.8.3-2014q1/bin/, automatically converted to compiler.path={runtime.tools.arm-none-eabi-gcc.path}/bin/. Consider upgrading this core.
Warning: platform.txt from core ‘STM32 Boards (STM32duino.com)’ contains deprecated recipe.ar.pattern=”{compiler.path}{compiler.ar.cmd}” {compiler.ar.flags} {compiler.ar.extra_flags} “{build.path}/{archive_file}” “{object_file}”, automatically converted to recipe.ar.pattern=”{compiler.path}{compiler.ar.cmd}” {compiler.ar.flags} {compiler.ar.extra_flags} “{archive_file_path}” “{object_file}”. Consider upgrading this core.
Warning: platform.txt from core ‘STM32F3 boards’ contains deprecated compiler.path={runtime.ide.path}/hardware/tools/gcc-arm-none-eabi-4.8.3-2014q1/bin/, automatically converted to compiler.path={runtime.tools.arm-none-eabi-gcc.path}/bin/. Consider upgrading this core.
Warning: platform.txt from core ‘STM32F3 boards’ contains deprecated recipe.ar.pattern=”{compiler.path}{compiler.ar.cmd}” {compiler.ar.flags} {compiler.ar.extra_flags} “{build.path}/{archive_file}” “{object_file}”, automatically converted to recipe.ar.pattern=”{compiler.path}{compiler.ar.cmd}” {compiler.ar.flags} {compiler.ar.extra_flags} “{archive_file_path}” “{object_file}”. Consider upgrading this core.
Warning: platform.txt from core ‘STM32F4 boards’ contains deprecated compiler.path={runtime.ide.path}/hardware/tools/gcc-arm-none-eabi-4.8.3-2014q1/bin/, automatically converted to compiler.path={runtime.tools.arm-none-eabi-gcc.path}/bin/. Consider upgrading this core.
Warning: platform.txt from core ‘STM32F4 boards’ contains deprecated recipe.ar.pattern=”{compiler.path}{compiler.ar.cmd}” {compiler.ar.flags} {compiler.ar.extra_flags} “{build.path}/{archive_file}” “{object_file}”, automatically converted to recipe.ar.pattern=”{compiler.path}{compiler.ar.cmd}” {compiler.ar.flags} {compiler.ar.extra_flags} “{archive_file_path}” “{object_file}”. Consider upgrading this core.
Warning: platform.txt from core ‘GD32 Boards (STM32duino.com)’ contains deprecated compiler.path={runtime.ide.path}/hardware/tools/gcc-arm-none-eabi-4.8.3-2014q1/bin/, automatically converted to compiler.path={runtime.tools.arm-none-eabi-gcc.path}/bin/. Consider upgrading this core.
Warning: platform.txt from core ‘GD32 Boards (STM32duino.com)’ contains deprecated recipe.ar.pattern=”{compiler.path}{compiler.ar.cmd}” {compiler.ar.flags} {compiler.ar.extra_flags} “{build.path}/{archive_file}” “{object_file}”, automatically converted to recipe.ar.pattern=”{compiler.path}{compiler.ar.cmd}” {compiler.ar.flags} {compiler.ar.extra_flags} “{archive_file_path}” “{object_file}”. Consider upgrading this core.
Board Arduino_STM32:STM32F3:discovery_f3 doesn’t define a ‘build.board’ preference. Auto-set to: STM32F3_DISCOVERY_F3
Board Arduino_STM32:STM32F4:netduino2plus doesn’t define a ‘build.board’ preference. Auto-set to: STM32F4_NETDUINO2PLUS
Board Arduino_STM32:STM32F4:discovery_f407 doesn’t define a ‘build.board’ preference. Auto-set to: STM32F4_DISCOVERY_F407
Board Arduino_STM32:STM32F4:stm32f4stamp doesn’t define a ‘build.board’ preference. Auto-set to: STM32F4_STM32F4STAMP
Missing ‘maintainer’ from library in /home/stephen/sketchbook/libraries/ILI9225
Error compiling.
might serve as a heads up?
stephen
Perhaps they have depricated one of the work around they put in at 1.6.2 (or 1.6.3 etc … I really cant remember)
i.e the platform.rewrite.keys stuff
But looking at the output you posted it looks like another issue.
Its not exacly clear which bit of the “recipe” that it doesnt like
Also, it could just be that the nightly version is broken.
It may be better just to test in a day or two, and if its still broken to post an issue on GitHub (in Arduino/Arduino)
srp
I think its probably about time to get rid of the plaform.rewrite keys stuff, which is only present to support Arduino 1.5.x, as I’m pretty sure no one is using that version(s) any more, and there is no reason not to use one of the stable 1.6.x verions e.g. 1.6.4
Here are logs from Library Manager and compilation- portable Arduino 1.6.6 with official and unofficial Arduino_stm32 on Windows 10 x64
(There is a work around for the boards.txt issue by putting in empty boards.txt files)
The other errors I’ll need to investigate further.
And when I try to compile an empty sketch for the Due I get these warnings.
Warning: platform.txt from core 'Arduino ARM (32-bits) Boards' contains deprecated recipe.c.combine.pattern="{compiler.path}{compiler.c.elf.cmd}" {compiler.c.elf.flags} -mcpu={build.mcu} "-T{build.variant.path}/{build.ldscript}" "-Wl,-Map,{build.path}/{build.project_name}.map" {compiler.c.elf.extra_flags} -o "{build.path}/{build.project_name}.elf" "-L{build.path}" -mthumb -Wl,--cref -Wl,--check-sections -Wl,--gc-sections -Wl,--entry=Reset_Handler -Wl,--unresolved-symbols=report-all -Wl,--warn-common -Wl,--warn-section-align -Wl,--warn-unresolved-symbols -Wl,--start-group "{build.path}/syscalls_sam3.c.o" {object_files} "{build.variant.path}/{build.variant_system_lib}" "{build.path}/{archive_file}" -Wl,--end-group -lm -gcc, automatically converted to recipe.c.combine.pattern="{compiler.path}{compiler.c.elf.cmd}" {compiler.c.elf.flags} -mcpu={build.mcu} "-T{build.variant.path}/{build.ldscript}" "-Wl,-Map,{build.path}/{build.project_name}.map" {compiler.c.elf.extra_flags} -o "{build.path}/{build.project_name}.elf" "-L{build.path}" -mthumb -Wl,--cref -Wl,--check-sections -Wl,--gc-sections -Wl,--entry=Reset_Handler -Wl,--unresolved-symbols=report-all -Wl,--warn-common -Wl,--warn-section-align -Wl,--warn-unresolved-symbols -Wl,--start-group "{build.path}/core/syscalls_sam3.c.o" {object_files} "{build.variant.path}/{build.variant_system_lib}" "{build.path}/{archive_file}" -Wl,--end-group -lm -gcc. Consider upgrading this core.
Warning: platform.txt from core 'Arduino ARM (32-bits) Boards' contains deprecated recipe.ar.pattern="{compiler.path}{compiler.ar.cmd}" {compiler.ar.flags} {compiler.ar.extra_flags} "{build.path}/{archive_file}" "{object_file}", automatically converted to recipe.ar.pattern="{compiler.path}{compiler.ar.cmd}" {compiler.ar.flags} {compiler.ar.extra_flags} "{archive_file_path}" "{object_file}". Consider upgrading this core.
WARNING: Category '' in library SPI is not valid. Setting to 'Uncategorized'
WARNING: Category '' in library Wire is not valid. Setting to 'Uncategorized'
Sketch uses 10,660 bytes (2%) of program storage space. Maximum is 524,288 bytes.
I think they are intending to fix this in the next release, as my issue https://github.com/arduino/Arduino/issues/3935
now has these responses to it
ffissore closed this 7 minutes ago
@ffissore ffissore added Component: Core Type: Duplicate Architecture: SAM labels 7 minutes ago
@ffissore ffissore added this to the Release 1.6.6 milestone 7 minutes ago
@cmaglie cmaglie was assigned by ffissore 7 minutes ago
I got this response on GitHub
Also these have been fixed. But until these updates to SAM core won’t get released, the warning will keep on popping up
So basically. Dont use 1.6.6 at the moment as it does not work for us and its currently not clear what we need to change.
I will need to wait for the official release of the new SAM core, before I can figure out what the changed and what we need to change
If you edit each library.properties file and add a keyword value pair for each library:
maintainer=Joebob <[email protected]>
Its also missing some stuff from boards.txt for build.board on the F3 boards (that we don’t use ) and one of the F4 boards.
I can fix these, but a lot of people are going to keep asking questions about the warnings / errors until we can fix them.
Note. I noticed someone else mailed the IDE developers mailing list about this, requesting doc’s.
As every the IDE team don’t seem to view the IDE as something anyone else is using, i.e anyone other than the Arduino dev team
I can live with warnings.
-rick
I’m not quite sure why a lot of the warnings are appearing, they are associated with inline functions – (Rick I know this is a long standing issue), but it looks more like its a change to the warning level under which the code is being compiled rather than the known issue of __always_inline_ clashing with the compile definition of the same name
I guess I could bite the bullet and perhaps change all the __always_line_ stuff in the core, but this is rather high risk, and at the moment I think there are other problems with 1.6.6 in the way they have changed the “recipe” stuff.
I think we need to let the dust settle a bit on 1.6.6 before jumping to conclusions about why there are these warnings, rather than wasting time making loads of changes, only for the IDE team to possibly change things in 1.6.6. before its officially released
daft idea, they’d do the prod/play anyway. however it would be on a clearly separate and clean code tree
the 1.6.5 would remain as ‘was’ ready for a more complete fix to be applied later.
idle thoughts of an up all night(2nd or 3rd consecutive retired hw/sw bod:-)
the cat kept wanting out, easier to leave door open and suffer the cool night air
stephen
So I really don’t think this is worth wasting time on (and download bandwidth), until its officially released, and they have fixed all the issues for their own boards.