Bootloader FAQ

Q: How much flash memory does the Torrox C2000 bootloader occupy?

Approximately 16 KB, plus 16 bytes reserved at the end of the flash range of the application for the bootloader’s bookkeeping metadata. The rest of the flash remains available for your application.

Q: Which interfaces are supported for firmware updates?

Currently, CAN Bus and UART/SCI are supported by the bootloader and the bootloader client. We plan to extend that list, if the interface, that you need is currently not in the list above, get in touch with us.

Q: Is the bootloader protocol documented so I can build my own update client?

Yes, the protocol is documented. But, we recommend to use our client library that fully implements the protocols. The library is written in plain C and provides abstractions of the used interfaces and OS services. You can get the sources of that library.

Our own clients are build on top the library. We have clients that implemented their client even on microcontroller hardware, using the client library.

Q: Do I need a source code license when I want to build my own update client?

No, you can get the client library, that we use for our clients and build your own client on top of it.

Q: How is the bootloader installed?

You receive a hex file and then, you can use what ever method your hardware supports. The usual way is to use JTAG.

Q: What do I need to integrate my application with the bootloader

You just need to change your linker script, so that the application start address is moved behind the end of the bootloader. The available flash size to you application has to be reduced by the sizehe bootloader and additional 16 bytes.

We provide linker script examples for all supported device families.