# HG changeset patch # User David Douard # Date 1464730390 -7200 # Node ID 3d0bed1a79c818221891baf92635b6c9ad0a90e3 # Parent d56199d873d4c3dba5d8444ac3e1358e5571817d [prologix] typos diff -r d56199d873d4 -r 3d0bed1a79c8 content/prologix.rst --- a/content/prologix.rst Tue Apr 19 23:19:42 2016 +0200 +++ b/content/prologix.rst Tue May 31 23:33:10 2016 +0200 @@ -60,22 +60,22 @@ Obviously, Windows stuff only, and no documentation on how to upgrade the device on Linux. -But the fact it uses avrdude_ is good sign it might to find solutions +But the fact it uses avrdude_ is good sign it might be possible to find solutions on Linux. According the names of the hex files, it seems there have 2 versions of the hardware, one with a ATMega16 and one with a ATMega164P (mine uses a 164P). -Now, the question is: haw is the AVR programmed? There are dozens of +Now, the question is: how is the AVR programmed? There are dozens of 'backends' available on avrdude. -Doing a ``string`` on the main exe in thie archive, PxUpdate.exe, +Doing a ``string`` on the main exe in the archive, PxUpdate.exe, shows a few interesting things, especially this:: strings PxUpdate.exe | grep -i avr avrdude.exe -p %s -P \\.\COM%d -c avr109 -u -e -U flash:w:%s AVRBOOT -So we know the commande line used by this firmware update tool, and we +So we know the command line used by this firmware update tool, and we known it uses the AVR's bootloader as decribed in the AVR109_ application note. @@ -133,9 +133,9 @@ So there is something else required to put the device under firmware -upgrade state. I was wondering is there is an undocumented controller -commands (anything starting with ``++`` is interpreted as a controller -command, so I searched for the ``++`` string in ``PxUpdate.exe``:: +upgrade state. I was wondering if there is an undocumented controller +command (anything starting with ``++`` is interpreted as a controller +command), so I searched for the ``++`` string in ``PxUpdate.exe``:: strings PxUpdate.exe | grep ++ Microsoft Visual C++ Runtime Library