stm32 - ISP vs SPI: interpreting signal labels -
i'm interested in interfacing stm32-based flight controller external sensors based on spi (serial peripheral interface) protocol. have couple of fcs (flip32 f3, shown in attached photo; emax skyline 32) have section of pins marked 5v/gnd/rst/sck/miso/mosi, presume there support isp (in-system programming); i.e., these pins allow fc act slave device programmer device acts master. other boards, such multiflite nano-b-fc, provide pin headders explicitly spi (other attached image), cs (chip select) instead of rst.
am correct in these assumptions: i.e., first kind of pinout (rst/sck/miso/mosi) not support external spi sensor, , latter (cs/sck/miso/mosi) does?
flip32 f3 flight controller; isp pads upper-left:
multiflight nano-b flight controller pin header schematic:
i don't know these boards, had @ pics on internet.
the flip32 f3 seems have atmel atmega microcontroller on board. (as auxiliary mcu) assume 6 pins found isp interace mcu.
just use multimeter in continuity test mode , check if 6 pads connected isp pins of atmega.
the board's main mcu stm32 more programmed through swd (serial wire debug) interface. that's pin-reduced jtag alternative. google it.
here details if interested in atmels isp: http://www.atmel.com/images/doc0943.pdf
if firmware supports (or write 1 supports it) should able use isp interface normal spi interface is.
isp done through simple serial interface jtag, swd or in avr case spi.
best way find out: read datasheet of atmega.
Comments
Post a Comment