Nucleo f746zg mbed9/24/2023 There are multiple variations on three common themes, so it's a bit confusing at the beginning.ġ) PJRC: Support processor sets up a RAM-executing bootloader to accept images over USB using HalfKay Ģ) FRDM (and some others): Support processor always available, accepts images either using USB storage file-writing or CMSIS-DAP ģ) Classical debugger providers (Keil, PEMicro, etc) where a debug dongle uses JTAG or SWD to program flash.įirst answer: Yes, Paul's bootloader accepts data using the HalfKay protocol. If only the Teensy 3.5/3.6 and Ethernet were available when were starting development. I use Teensys as ultra-programmable signal generators, and general support. We have been developing a pretty serious distributed industrial data acquisition/control system using FRDM boards for prototyping, and it's been reliable, powerful and convenient. Te FRDM connects a UART on the support processor to a UART on the K64, and when the host interacts with the abstract communication model "serial" port provided by the support processor, it tunnels the bytes to and from the main processor.įinally, the support processor supports CMSIS-DAP debug protocol for the classical debugging that are often required to get past knotty problems in the application. The act of writing data to that "file" causes the support processor to use the SWD facility in the K64 to program its flash. The host computer can load a new flash image into the K64 by opening and writing a file with the ".bin" extension to the virtual filesystem provided by the support processor. The FRDM board's support processor remains connected to its USB port at all times, and provides CMSIS-DAP, and a virtual serial port, and a virtual USB storage partition. That bootloader then takes control of the main processor to allow it to accept flash images from the host. The support processor in the Teensy (MKL-02), when triggered by the program button, uses the SWD (serial wire debug) facility in the main processor to load a bootloader into the main processor's RAM. Both Teensy and thhe FRDM have an additional processor to support downloading those programs and to support the "unbrickability" that is the hallmark of Paul's Teensy. However, I also notice that the mbed API for CAN was only recently enabled for Nucleo boards.The FRDM board has a structure similar to Teensy: The processor that we all use, write programs for and has the peripherals (accel, etc.), is the K64. I am fairly new to using CAN protocol, so there may be some hardware issue that I have neglected. This issue persists across all 3 of my Nucleo boards. In fact, if I completely disconnect any wiring from the CAN pins on the Nucleo board, it still claims that it is reading a message from 0x445. In addition, when I attempt to use read(), it tells me that there is a message from a random ID (0x445) whenever I call it, regardless of what the other device on the bus is doing, or even if there aren't any devices on the bus at all. However, when I attempt to write a message to the bus, I see what appears to be a valid message on my oscilloscope, but the device I am sending the message to does not respond in any way. I am attempting to create a CAN controller using a Nucleo-F746ZG with an MCP2551 transceiver. To start a new conversationĦ years, 8 months ago. Important changes to forums and questionsĪll forums and questions are now archived.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |