ldeveraux wrote:megari wrote:
If you wish to build the "NTP" image yourself and use the build system for updating the firmware, it should be as simple as:
Code: Select all
git checkout fw_1.1-test0
make build_hex_ntp program
This builds the "NTP" variant of the firmware and flashes the firmware on the MCU onboard the Koryuu.
Please let me know if you run into any trouble. Have fun!
I didn't know I needed a 10 pin to 6 pin adapter, so I have one on order. I thought the Olimex 6 pin cable was what I'd use.
Ah, indeed. Now that I think of it, mine did not ship with such a cable either, but I must've already had one at hand.
ldeveraux wrote:
To update my Koryuu with the "NTP" image, I'd first build the image with:
Code: Select all
git checkout fw_1.1-test0
make build_hex_ntp program
Then flash with avrdude?
The command line above does the flashing for you, so no need to run avrdude manually. It basically runs two targets in
Makefile back-to-back, as if you had run them sequentially one-by-one like so:
Code: Select all
make build_hex_ntp # Builds the firmware image
make program # Invokes avrdude with the appropriate parameters and flashes the freshly-built firmware
If you are not very familiar with build systems on Linux (and most other POSIX-like OSes), I recommend reading a bit about make, Makefiles etc, as they are a rather common occurrence in various tasks involving development and automation in Linux and other POSIX-likes.
ldeveraux wrote:The JunkerHQ wiki uses Khazama, so I figured I'd ask.
The instructions on the JunkerHQ wiki are Windows-specific, and Khazama does not seem to have been updated in a long while. It also appears to be hard-wired to a specific programmer, despite having a full avrdude binary embedded within itself.
Just for the record, for Windows users, my suggestion would be to try
AVRDUDESS, possibly after installing drivers for your programmer using
Zadig.
ldeveraux wrote:
Complicating things more, your github page just says:
"Flashing the built firmware can be accomplished by the command:"
That simply flashes the firmware after it has been built [1]. Please note that the "program" target is the latter one of the two targets run in my last message.
[1] To be more precise, the "program" target depends on having a built firmware .hex image, so if none has been built yet, it will actually automatically build one (with the default settings) and then do the flashing. Make is built exactly for these sorts of things where there are dependencies between different components or processes within a project.