forked from shumatech/BOSSA
-
Notifications
You must be signed in to change notification settings - Fork 0
/
CHANGELOG
46 lines (29 loc) · 2 KB
/
CHANGELOG
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
BOSSA 1.7.0-etherkit-1
* Added support for SAMD21G16A, SAMD21G16B.
* Changed flash block transfer size from 4096 bytes to 2048 bytes to support chips with less RAM.
BOSSA 1.7.0
* Mainline BOSSA has been merged again with Arduino version
BOSSA 1.6.1-arduino
todo
BOSSA 1.6-arduino
todo
BOSSA 1.5-arduino
* Added Codelite project for easier development and debug.
* Improved support for SAMD21 chip by using existing applet already in use for other devices.
* Added time count for operations erase, write, read and verify.
* Added Devices.h for global definitions for each devices.
* NVMFlash::write() rewritten.
* Removed some useless functions from 1.4 release.
* Added a mask for SAMD chipid: DIE and REV bitfields are not taken into account as they may vary in the time without impacting the features.
* Improved write time performance by a factor of 2x
BOSSA 1.4-arduino
* Added support for SAMD21 chip
BOSSA 1.2
NEW IN THIS RELEASE
* New BOSSA shell command line application to do basic memory, flash, and PIO diagnostics
* Workaround for SAM3U firmware bug
* Fixed a bug with setting boot to flash bit on SAM3 devices
* The OS X USB driver detects an Atmel device as a USB modem. When prompted about a new network interface, click Cancel to continue.
* Some stability issues have been seen with the OS X USB driver using BOSSA. When running BOSSA a second time to the same Atmel device, the USB driver can lock up causing BOSSA to freeze. As a workaround, always disconnect and reconnect the Atmel device before running BOSSA again.
* The firmware inside of SAM3U devices has a bug where non-word flash reads return zero instead of the real data. BOSSA implements a transparent workaround for flash operations that copies flash to SRAM before reading. Direct reads using the BOSSA shell will see the bug.
* There are reports that the USB controller in some AMD-based systems has difficulty communicating with SAM devices. The only known workaround is to use a different, preferrably Intel-based, system.