https://w.electrodragon.com/w/index.php?action=history&feed=atom&title=RPI_PROGRPI PROG - Revision history2026-06-04T21:08:36ZRevision history for this page on the wikiMediaWiki 1.37.2https://w.electrodragon.com/w/index.php?title=RPI_PROG&diff=32840&oldid=prevChao at 09:32, 31 August 20232023-08-31T09:32:47Z<p></p>
<p><b>New page</b></p><div>== Setup ==<br />
* $sudo apt-get install openocd<br />
* $sudo apt-get install avrdude<br />
* $sudo apt-get install flashrom<br />
<br />
<br />
== OPENOCD ==<br />
* Read more information here: [[OpenOCD]]<br />
== AVR ==<br />
[[File:2019-06-04 141936.png|thumb]]<br />
* Install avrdude by: sudo apt-get install avrdude<br />
* reference https://www.monocilindro.com/2017/03/20/flashing-arduino-using-raspberry-pi-shell/<br />
* Download the avrdude.conf from our bitbucket.<br />
* Use the following commands <br />
env.sh configure chip type <br />
probe.sh detect the chip and connections <br />
flash_dump.sh read flash <br />
flash_write.sh flash flash <br />
==== Modify avrdude.conf for RPI ====<br />
# Linux GPIO configuration for avrdude.<br />
# Change the lines below to the GPIO pins connected to the AVR.<br />
<source lang="c"><br />
programmer<br />
id = "linuxgpio";<br />
desc = "Use the Linux sysfs interface to bitbang GPIO lines";<br />
type = "linuxgpio";<br />
reset = 12;<br />
sck = 24;<br />
mosi = 23;<br />
miso = 18;<br />
;<br />
</source><br />
<br />
<br />
== SWD - STM32 ==<br />
* env.sh Configure the platform to which the chip belongs, such as stm32f1x, stm32f2x, etc. When calling other scripts, you need to execute source ./env.sh first to initialize the environment variables, the same below.<br />
* probe.sh is used to detect the existence of the chip<br />
* attach.sh attach to the chip, then another window can call $telnet localhost 4444 for single step debugging<br />
* flash_dump.sh dumps the flash data from the chip<br />
* flash_erase.sh erase flash data in the chip<br />
* flash_write.sh Flash inside the chip<br />
* lock.sh stm32 series chip provides flash write protection. After the write protection is turned on, the chip cannot be debugged. The flash data is read. The product commercial recommendation is to open the write protection function.<br />
* unlock.sh cancels write protection.<br />
<br />
== I2C and SPI ==<br />
=== Flash ===<br />
* probe.sh detect the flash type<br />
* flash_dump.sh read flash <br />
* flash_write.sh write flash <br />
<br />
=== EEPROM ===<br />
Please notice V1 version use I2C0, V2 version add selection to I2C1<br />
<br />
* env.sh Configure the chip model, you can call avrdude -p ? to view the currently supported chips.<br />
* probe.sh probes the i2c bus<br />
* flash_dump.sh read flash<br />
* flash_write.sh flashing flash<br />
OR use [[I2CDetect]] to direct dump, write, and read<br />
<br />
<br />
<br />
[[category: RPI Shield]]<br />
<br />
[[category: PROG]]</div>Chao