I wrote a program to use I2C with stm32f407vgt on my board but it doesn't work. I checked the clock(scl) and it was OK , then i tested the same program on stm32f429 discovery board without changing any settings and it worked. any idea about what should i do ?
my micro is stm32f407 and i use internal clock source.
Thanks hamid
Related
Good day everyone.
There is a need to connect via jtag / swd to stm32f205.
There is a chip soldered by all pins.
There is a Chinese st-link v2
I guess I need rst, swclk, swdio 3.3vdd
in datasheet it is 7, 49, 46, 48 pins
I'm not sure if I connected correctly and stm utility also does not see the chip.
I ask you to guide me on the right path and explain where I went wrong and how to do it right.
Thank you in advance.
I guess your forgot to install the STLink driver on your host machine.The pins you connected are OK as there is no need to connect the Gnd using this USB-STLink module.
For Linux Hosts you can find the packge in official repositories (use aptitude).
Further installation guildelines could be found here.
Your pins are ok (I hope you have not forgotten to connect the GND pin, since you have not mentioned it).
Let me remind you to choose SWD program mode in your programmer rather than JTAG.
I want to measure the current consumption of the uC on my STM32 Nucleo-64 evaluation board (NUCLEO-L073RZ). The manual says, that I just have to remove the JP6/IDD jumper and then connect the pins to an ammeter:
But if I just remove the JP6 jumper (no pin connection), the uC is still running (I can still debug/communicate via I2C). I would have expected, that if the JP6 is removed, the uC is no longer powered and therefore not accessible anymore...
Can somebody please explain me, where is my error in reasoning?
Here is the link to the corresponding STM32 Nucleo-64 manual (page 23):
https://www.st.com/content/ccc/resource/technical/document/user_manual/98/2e/fa/4b/e0/82/43/b7/DM00105823.pdf/files/DM00105823.pdf/jcr:content/translations/en.DM00105823.pdf
Connecting the USB to the debug port IS powering the MCU through the debug pod. Try removing the 2 ST-LINK jumpers on upper left an inch from the the USB connector. That disconnects the built-in ST-LINK from the MCU. That might remove the power from the debug pod to the MCU.
I found the reason: the problem was my fuse in the multimeter was broken and the irritating LED on the Nucleo is always ON (independently of the MCU is running or not)...
I have an ESP32 board, with Micropython installed properly, and connecting to local the internet.
Since it have to do a scheduled jobs- its clock need to be synced. After boot it get a generic date 1/1/2000.
How can Micropython updates int clock using ntp.pool.org or other?
Guy
From this post on the Micropython forum:
There is primitive NTP support in the ESP32 port (borrowed from the
ESP8266 port). In short:
import ntptime
ntptime.settime() # Synchronise the system time using NTP
Caveat: There is no timezone support so the system time will be set to
UTC.
From this discussion, you need to make sure you have an active internet connection before trying to set the time, and you should expect to get occasional timeout errors and handle these appropriately.
For reference the source of the ntptime module is here
You can get a DS3231 RTC. I’m currently using one and it works great.
I am trying to establish a serial connection between the RPI3 and an Arduino. Because that wasn't working I connected a USB to TTY cable from my laptop to the Rx/Tx pins of RPI. I was eventually able to use PuTTy to connect to it.
I am running Android Things on the RPI and the android code I have running is supposed to be a loopback (reading from UART and writing back what was read).
Here is where I am confused....
When PuTTy connected I was presented with a command line console on the RPI.
How do I get the Rx/Tx pins on the RPI to just be serial connections into and from my application and NOT a way to log into the console?
Is that a bad idea? I suppose if I ever needed to log into the RPI this would make it more difficult...
I figured out what I was doing wrong...
When following the setup directions at the below site I was using the Bluetooth mode instead of the Application mode. When I followed the directions for Application mode I was able to start using UART0 for serial comms
Set the console attribute to the following in cmdline.txt:
console=tty0
Add the following line in config.txt:
dtoverlay=pi3-disable-bt
Remove the following lines from config.txt:
enabled_uart=1
core_freq=400
https://developer.android.com/things/hardware/raspberrypi.html#disabling_the_console
Beginning with Developer Preview 3, in which USB-Serial devices support added, You can use external USB-UART dongles like this instead of UART of Raspberry Pi 3.
I am trying to connect a Temp and Humi probe Adafruit AM2315 and it seams that the only thing I need to do is to get i2c running on my Pi2. I can't seams to find the proper instructions or command line to get it config and running ? Can someone help ?
did you connect it directly to the RPi2 I2C pins, or did you use the 10KOhm resistors too..?
It seems it needs two rapid connections to wake up first, before starting to send commands, see here:
http://raspberrypihobbyist.blogspot.it/2015/02/using-am2315-temperaturehumidity-sensor.html
David