
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
#1310 makes it easier to write from openocd with feather-m4 and others.
However, two problems remain.
1. touchSerialPortAt1200bps() is executed when programmer is specified
As for 1, the following json does not have the flash-1200-bps-reset setting and will not cause a problem.
However, it is not reasonable to separate json, so you need to set flash-1200-bps-reset = false when -programmer is specified.
If you solve this problem, we will be able to write to the board in panic state.
(Normally flash-1200-bps-reset cannot be performed on a board in panic state.)
Also, we will be able to do rewrites very quickly.
2. Sometimes bootloader mode is triggered after writing
I think the reason for this problem is that the reset is performed multiple times when writing.
I don't know why, but changing
program *.hex reset exittoprogram *.hex verify reset exitsolved the problem.I don't know if this is the right solution, but I'd like to fix it in some way.
The text was updated successfully, but these errors were encountered: