Eval¶

Biwak supports bootloader via linkerscript.

There needs to be some communication between BL and APP;

APP --> BL: start app or bl?
BL --> APP: Version of BL; does this combination work- Should be checked when flashing.

Lower bottom of stack can not be used because this can change with newer firmware release.

• Communication via option bytes: This way RAM has not to be preserved; incomplete updates are handled. Some cost.
• ISR-Table is relocated by Kokon
• When BL was used, Application does not need to config the clock any more. Can save a lot of flash
• Kokon should send article number and Bootloaderfirmware, so flash tool can verify if this is the correct image
• App clears option bytes again

Problem is: Bootloader and application probably have different configurations. An seperate build has to be triggered. -> Arena supports subsets now.

Ablauf¶

Command/Result muss aufgebaut werden

• kokonFlasher -> Request status, wait for status, need to enter bootloader?
• kokonFlasher -> Command: enterBootloader
• kokon -> Status: Bootloader
• kokonFlasher -> Command: Scan/
• kokon -> Status: Send Kokon version, board id, article id
• kokonFlasher -> Check ids and versions
• kokonFlasher -> Command: reboot to productive

Blobs via TDT are missing