![atollic truestudio and stm32f769 atollic truestudio and stm32f769](https://user-images.githubusercontent.com/25970722/73759306-c6aa9f00-4739-11ea-89f5-a306d4af734b.png)
- #Atollic truestudio and stm32f769 how to#
- #Atollic truestudio and stm32f769 code#
- #Atollic truestudio and stm32f769 plus#
These 2 bytes will contain the temperature data.Ĭonnect your Nucleo to the TMP102 as shown in the following Fritzing diagram: We immediately follow that with a read command where we read 2 bytes from the TMP102.
![atollic truestudio and stm32f769 atollic truestudio and stm32f769](https://wiki.segger.com/images/d/d8/TrueSTUDIO_Tutorial_6.png)
Note that we need to first send out a write command from the STM32 to the TMP102 with 1 byte that contains the address of the temperature register in the TMP102 (address 0x00). If you would like to learn more about the I2C protocol, I recommend this tutorial from SparkFun.īy looking at the TMP102 datasheet, we can determine that retrieving temperature data from the temperature register would require a set of I2C write/read commands as follows: Most microcontrollers have at least 1 I2C peripheral controller built in to the silicon. It is a relatively slow protocol but has seen widespread use due to its simplicity and robustness. Inter-Integrated Circuit (I2C) is a communication bus protocol developed by Philips Semiconductor (now NXP Semiconductors) in 1982. I recommend the SparkFun TMP102 Breakout Board to test the device. It relies on I2C to communicate data to and from a host device.
![atollic truestudio and stm32f769 atollic truestudio and stm32f769](http://www.emcu.it/STM32/Atollic/How_to_use_STM32_examples_in_ATOLLIC_TrueSTUDIO_Lite/fig6.png)
![atollic truestudio and stm32f769 atollic truestudio and stm32f769](https://westsideelectronics.com/content/images/2018/12/IMG_20181224_090358_HDR.jpg)
The TMP102 is an extremely simple digital temperature sensor from Texas Instruments. Note that any Nucleo board may be used, but steps are shown for the Nucleo-L476RG. But I surely did learn a lot from it.You will need the following components to complete this tutorial: Though it does take some studying of the code/makefiles and I understand it can be off-putting if it doesn't work immediately. we have a robot with enough power in the arms to knock people unconscious, you don't usually find that in the hobbyiste maker space.Īnyway: all that just to illustrate that what you want is possible.
#Atollic truestudio and stm32f769 plus#
Ok not everything is time-critical, but it's science so things should run 100% correct plus there's sometimes people + robots involved so there's also a safety aspect, e.g.
#Atollic truestudio and stm32f769 code#
Buys Visual Studio, pays people to use it with MicroPython, has like >20k loc of C++, Labview and Matlab code all controlled by MicroPython, uses it to perform time-critcical tasks for scientific experiments. The place where I introduced MicroPython, and for which I ported it to windows/msvc, is exactly what I'd call "professional" usage. I think it will be a grate benefit for you whether this project can be used by "professional" user's and not limited to hobbyist makers who can only used free tools.
#Atollic truestudio and stm32f769 how to#
There is lack of information(documentation) regarding those macro files - what is the purpose,how to re compile them, how to use them in other compilers and in different environment?Ī professional written project with good software engineering in mind would have more information embedded with in ,as adding remarks and documentation sometime is more important then the code himself and somewhat easy to move from one compiling environment to another. I spent lot of time trying to compile it on different environment (IAR ,Keil, Ads ) and encounter lots of errors - mostly due to some header files not wiling to compile no meter what,I have try. It is a good project who create a good surrounding community, I salute you and any others who work on this project for the work you have done.