This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

dtm rf test from bootloader

I am attempting run the rf test from the bootloader. But I have the following problems.

When I try to compile the dtm rf test into the bootloader I run out of space.

Possible solutions include

  1. compacting the bootloader and placing the dtm test into the bootloader This is not really practical give that well will need to add another sensor jig test as well.

  2. In bootloader sense whether pins pulled low by the test jig when present.

a) Launching the application firmware and again sense whether pins pulled low. Performing dtm test or sensor jig test infinite loops before the normal application.

b) Launch the dtm test or sensor jig test by jumping to an separate code region.

I would think that Launching the application firmware and running the dtm test or sensor jig test from there should work. But I don't seem to enter the test loops as expected. If this should work I can provide a code example.

Parents
  • If you really need the DTM test in the bootloader couldn't you just allocate more space for the bootloader project configuration?

    That said, the way we enter DTM mode is that our application FW checks a pin at the beginning of initialization. If it is pulled low we enter the DTM, if not we boot our normal application much like you suggest above.

Reply
  • If you really need the DTM test in the bootloader couldn't you just allocate more space for the bootloader project configuration?

    That said, the way we enter DTM mode is that our application FW checks a pin at the beginning of initialization. If it is pulled low we enter the DTM, if not we boot our normal application much like you suggest above.

Children
  • I did not know how to add more space for the bootloader project.

    Can you point me to documentation or an example how to configure and add more space to the bootloader project. Also what are the limitations on how much space can be added to the bootloader project.

  • If you look at the documentation that comes with the SDK there is a section in the Examples for the DFU bootloader. One of the sections details the DFU Keil project and shows how to set the IROM1 address. If you pick a lower address than the one they show, you will increase the memory your bootloader can have. Just be sure to keep it aligned to the 1K page boundary.

    There is no direct limitation of how much space the DFU bootloader can take other than you need to leave space for your application. You need to decide what your trade offs are.

Related