i am seeing some strange issues, but maybe my total misunderstanding the whole structure of the software.
first of all, is the bootloader necessary ? if i am not interested in mission planner or other things, just want to use st-link for flash my software to control sensors and escs … do i need bootloader ?
perhaps thats my issue, without usign bootloader, and the ardupilot crashses rightaway…
the tool i am using is gcc-arm-none-eabi-6-2017-q2-update… (i found that 2018-q4-major does not work).
also, notice very strange issue… i create my new board and copied files from F4BY (just to see what happen)… it successfully built with “waf --configure myboard”, but if i did “waf --configure myboard --debug”, then it failed to compiled. the strangest thing is that if i did “waf --configure F4BY --debug” it works fine, even though two directories have exact the same files.
also, the documentation maybe outdated regarding porting to a new board, because i think (at least from my poking around), i would need to add board name to Tools/scripts/build_binaries.py and also, add new ID in libraries/AP_HAL/AP_HAL_Boards.h