2022-01-30 07:24 AM
Solved! Go to Solution.
2022-01-31 06:15 AM
Hi @QAbba.1 , it's not easy to understand if you are using the sensortile (STEVAL-STLKT01V1, https://www.st.com/en/evaluation-tools/steval-stlkt01v1.html) or the sensortile.box (STEVAL-MKSBOX1V1, https://www.st.com/en/evaluation-tools/steval-mksbox1v1.html)
For the sensortile.box, if you want to debug you need an STLINK/V2 as programming interface (you can find it on any STM32 Nucleo-64 development board)
https://www.st.com/en/development-tools/st-link-v2.html
For the sensortile, it is the same, as reported on the homepage of the product: "It is recommended to use ST-LINK/V2-1 found on any STM32 Nucleo-64 development board".
For programming, you just need the .bin file and you can use the DFU mode to download the application fw on the board, but it's hard to debug it in this way.
AG
2022-01-31 06:15 AM
Hi @QAbba.1 , it's not easy to understand if you are using the sensortile (STEVAL-STLKT01V1, https://www.st.com/en/evaluation-tools/steval-stlkt01v1.html) or the sensortile.box (STEVAL-MKSBOX1V1, https://www.st.com/en/evaluation-tools/steval-mksbox1v1.html)
For the sensortile.box, if you want to debug you need an STLINK/V2 as programming interface (you can find it on any STM32 Nucleo-64 development board)
https://www.st.com/en/development-tools/st-link-v2.html
For the sensortile, it is the same, as reported on the homepage of the product: "It is recommended to use ST-LINK/V2-1 found on any STM32 Nucleo-64 development board".
For programming, you just need the .bin file and you can use the DFU mode to download the application fw on the board, but it's hard to debug it in this way.
AG