summaryrefslogtreecommitdiff
path: root/boards/at91sam3u-ek
Commit message (Collapse)AuthorAgeFilesLines
* SAM3U: Use correct DMAC peripheral ID for SSC receiveHarald Welte2012-02-261-1/+1
| | | | | | | | | | | | | It seems like the SSC Rx channel has a different DMAC peripheral ID (4) than the transmit side. The official Atmel sam3u documentation (doc6403e) doesn't document that fact, and it also doesn't even state any DMAC peripheral identifiers. The at91lib code release by Atmel claims it is 3, when in reality it is 4! I found this by brute-forcing all possible peripheral identifiers.
* add missing dfu.ldsHarald Welte2012-01-081-0/+87
|
* SAM3U-EK: Add a 'dfu' makefile target, DFU boot switching codeHarald Welte2012-01-083-2/+37
|
* DFU: add support for setting the USB SERIAL by a boardHarald Welte2012-01-081-0/+2
| | | | | | this will allow us to use the Unique Chip ID as serial number in the USB descriptor, which in turn allows customers to write device-specific udev rules for persistent naming, etc.
* aat91sam3u-ek: Add #defines for DFUHarald Welte2012-01-051-0/+11
|
* import at91lib from at91lib_20100901_softpack_1_9_v_1_0_svn_v1501120100901_softpack_1_9_v_1_0_svn_v15011Harald Welte2011-07-0450-0/+25538
it's sad to see that atmel doesn't publish their svn repo or has a centralized location or even puts proper version/release info into the library itself
personal git repositories of Harald Welte. Your mileage may vary