#12kb on nucleo f401re update
Thanks! Will update with visual-theremin code if/when I get it to work. though I was able to get a busy-loop with a delay to effectively dim an LED. So does this mean that USB_VCP is useless for the F401? It seems LED.intensity is also broken or not implemented. Thanks, I figured as much, having some prior experience with microcontrollers and JTAG.
#12kb on nucleo f401re serial
You'll need to connect Tx from the USB-serial adapter to Rx on the F401, Rx on the USB serial adpater to Tx on the F401, and GND from the USB-serial adapter to GND on the F401. If you're going to use UART-6 then you need to connect a USB-to-serial adapter to the appropriate pins on the board and also use the appropriate /dev/ttyACMx for the usb-to-serial adapter. Note: If you're going to use UART-2 then you need to quit whatever program you were using for the REPL before running your host program. now back to co-routine mutlitasking for a GPIO cap-sense to LED-brightness visual-theremin! stm32 nucleo(64) nucleo-f103rbnucleo-f302r8nucleo-f303renucleo-f401renucleo-f410rb STM32CubeF3V1.11. I changed the device program back to UART 2, and prepended a 'print' on the client-side and voila!
Even the hint of 'Nothing Special' has no success. Nevertheless, it is not possible to store files greater than 12K. The free space of the F401 is displayed correctly in Explorer. The update of the firmware on the Nucleo-F401RE was also successful.
#12kb on nucleo f401re driver
You also don't print anything in your host program - you just read the data over and over in an infinite loop.ĭ'OH! That was the key here. Installing the USB driver (Windows 7 64bit) was successful. Yeah I was trying all sorts of things, with ser.read() and sending different strings from the MCU side. Now your host program calls readline, which waits for a newline, and since you don't send any, it will wait forever. Strangely it seems like pyb either carries over from boot.py, or it just magically is there, as I find pyb calls to work from the non-boot.py scripts that boot.py calls. I also uncommented he import of pyb which you'll need since you call pyb.delay:
Photo of the experimental setup consisting of the ST Nucleo-401RE. That's why I tried both USB_VCP, thinking well, I guess maybe that sends JTAG-encapsulated commands when you call write on it, while the UART would have its RS232-style protocol wrapping the data. operate within 12 KB of SRAM without impacting speed. Yeah that is what I figured when I was going through the schematic from STM, and also suspected it from eyeing the traces on the board for PA2 and PA3 (they looked unconnected, as in the schematic, and by default being routed to the ST-LINK TDI and TDO pins) It would be useful to describe what you're connecting to where.īy default, UART-2 is connected to he stlink processor, which will be advertised as /dev/ttyACM0 when plugging in the NUCLEO board The Nucleo-F401RE is a board from STs Nucleo family supporting a ARM Cortex-M4 STM32F401RE microcontroller with 96KiB of RAM and 512KiB of Flash.
0 kommentar(er)
