I am getting into testing Bluz as a product and I am trying to figure out how to best handle the following scenario:
- I compile new firmware against 2.2.50-beta3
- I upload firmware to my product and release the firmware
- I turn on a board that was provisioned and flashed with 2.2.50 over J-Link (it’s ID was added to the product)
At this point the board comes online and attempts to install the Released Firmware as it was instructed to do. However, it either gets stuck on solid magenta, or it ends up booting into safe mode, flashing yellow.
I am wondering if anything told it to upgrade to 2.2.50-beta3?
What is the correct workflow to make this work? I envision this happening when the system software has updated while the product was sitting on a shelf and has never been used. There doesn’t seem to be a way with a product to enforce newer system software in addition to the new user code.