This just pulls out the rboot arguments into a separate variable to allow overriding RBOOT_ARGS in local.mk or an application's makefile.
I have several different flash arrangements and rewriting the bootloader with different SPI schemes (DIO, QIO, 4m, 8m, etc) breaks things. Instead of changing FLASH_SIZE, FLASH_MODE, and FLASH_SPEED each time a different chip is flashed, overriding RBOOT_ARGS to be blank allows an application to write a custom bootloader (maybe without rboot's config at 0x1000) or none at all.
This just pulls out the rboot arguments into a separate variable to allow overriding
RBOOT_ARGSin local.mk or an application's makefile.I have several different flash arrangements and rewriting the bootloader with different SPI schemes (DIO, QIO, 4m, 8m, etc) breaks things. Instead of changing
FLASH_SIZE,FLASH_MODE, andFLASH_SPEEDeach time a different chip is flashed, overridingRBOOT_ARGSto be blank allows an application to write a custom bootloader (maybe without rboot's config at 0x1000) or none at all.