Comments on: LUFA Port, Source Control

By: Brad

Brad — Sun, 01 Mar 2009 19:52:05 +0000

One more comment, given you described version control usage (with svnsync) I think you’d be happier with a newer distributed version control system. I’ve tried many of them and my personal favorite is Bazaar (http://bazaar-vcs.org/). Unless you are Linux only, then Git might be a consideration but I still prefer Bazaar myself even on Linux.

By: Brad

Brad — Sun, 01 Mar 2009 19:36:11 +0000

In subversion there is no actual difference between a “branch” and a “tag”. They are both just copies of what most people call “trunk” at a point in time. The only difference between them is the meaning and purpose that developers apply to them.

Branches usually continue to receive commits after being created and diverge from trunk. Those changes may or may not be merged back into trunk down the road. Branches probably aren’t that useful with a dev team of 1, but you might create one to work on some experimental feature that will really destabilize things for a while. Then after you are ready either abandon it or merge it back to trunk.

Tags are mostly used to take a snapshot that you don’t plan to ever modify. For example, at each release. Then you can always get back to the way the code was at that point.

SVN doesn’t enforce and differences between a tag, a branch, or any other cop. They are just conventions. Oh and copies within a single repository are light weight. Only referenced are actually copied and then diffs between the copies (when any commits are made).

The subversion book talks about all this in more detail: http://svnbook.red-bean.com/

By: Dave

Dave — Sat, 28 Feb 2009 05:09:53 +0000

AVR32UC32B: Is an EVK1101 sufficient for your needs? I’m assuming you have a JTAG ICE MKII, which I think is the minimum programmer. DigiKey is currently showing a date of 4/12 for the EVK1101 — I have one on backorder for myself. Shoot me a private e-mail.

On multi-target: It’s inevitable that you will end up with some platform specific code. If it ‘twer me, I’d be looking for a way to isolate the hardware specific stuff into a low-level library with a well defined api. That way, it’s simply a matter of flipping a single variable in the Makefile that adds one of N .o files to the $OBJECTS variable to select the target. Going multi-target should be an interesting exercise. In the end, the code will very likely benefit from the refactoring.

By: casainho

casainho — Fri, 27 Feb 2009 16:09:56 +0000

Dean, don’t forget to ask me help on putting that AT91SAM7 working with the JTAG debugger/programmer (that I also offer). I have some experience on doing “GUI visual” debug with ARM using GNU Debugger + OpenOCD + Eclipse.

Also, that AT91SAM7 have a USB bootloader like the AVR USB, which means any user can program it using Sam-ba (utility from Atmel) on GNU/Linux, MS Windows, etc.

I wrote some quick instructions on how to setup all the tools for do the debug:
http://code.google.com/p/rockboxplayer/wiki/DevelopmentEnvironmentSetup

http://code.google.com/p/rockboxplayer/wiki/EclipseWithJTAGDebugSetup