Eval » Historie » Version 8
Maximilian Seesslen, 09.09.2024 15:22
| 1 | 1 | Maximilian Seesslen | h1. Eval |
|---|---|---|---|
| 2 | |||
| 3 | Biwak supports bootloader via linkerscript. |
||
| 4 | 2 | Maximilian Seesslen | |
| 5 | There needs to be some communication between BL and APP; |
||
| 6 | |||
| 7 | 7 | Maximilian Seesslen | APP --> BL: start app or bl? |
| 8 | BL --> APP: Version of BL; does this combination work- Should be checked when flashing. |
||
| 9 | 2 | Maximilian Seesslen | |
| 10 | Lower bottom of stack can not be used because this can change with newer firmware release. |
||
| 11 | |||
| 12 | * Communication via option bytes: This way RAM has not to be preserved; incomplete updates are handled. Some cost. |
||
| 13 | * ISR-Table is relocated by Kokon |
||
| 14 | * When BL was used, Application does not need to config the clock any more. Can save a lot of flash |
||
| 15 | 1 | Maximilian Seesslen | * Kokon should send article number and Bootloaderfirmware, so flash tool can verify if this is the correct image |
| 16 | 3 | Maximilian Seesslen | * App clears option bytes again |
| 17 | 4 | Maximilian Seesslen | |
| 18 | 5 | Maximilian Seesslen | Problem is: Bootloader and application probably have different configurations. An seperate build has to be triggered. -> Arena supports subsets now. |
| 19 | 8 | Maximilian Seesslen | |
| 20 | h2. Ablauf |
||
| 21 | |||
| 22 | Command/Result muss aufgebaut werden |
||
| 23 | |||
| 24 | * kokonFlasher -> Command: enterBootloader |
||
| 25 | * kokon -> Status: Bootloader |
||
| 26 | * kokonFlasher -> Command: Scan/ |
||
| 27 | * kokon -> Status: Send Kokon version |
||
| 28 | * kokonFlasher -> Command: reboot to productive |