initial

.gitattributes

@@ -0,0 +1,11 @@
+*.gprj linguist-language=XML
+*.cst linguist-language=Text
+*.sdc linguist-language=Text
+*.ipc linguist-language=Text
+*.mod linguist-language=Text
+*.mi linguist-language=Text
+*.do linguist-language=Text
+*.cfg linguist-language=Text
+*.fs linguist-language=Text
+*.gao linguist-language=XML
+

.gitignore

@@ -0,0 +1,7 @@
+impl/gwsynthesis/**
+impl/temp/**
+impl/pnr/**
+simulation/sim/**
+simulation/transcript
+!impl/pnr/device.cfg
+*.user

.gitmodules

@@ -0,0 +1,3 @@
+#[submodule "T65"]
+#	path = src/T65
+#	url = https://github.com/mist-devel/T65.git

INSTALLATION_WINDOWS.md

@@ -0,0 +1,111 @@
+# Installation using a Windows PC
+
+This document explains how to install all the necessary files on the
+Tang Nano 20K and the M0S Dock in order to use it as a A2600Nano
+device.
+
+This has been tested on Windows 11. It should work on older versions too.
+
+Software needed:
+
+  - [Gowin V1.9.10](https://www.gowinsemi.com/en/support/home/) **to synthesize the core**
+  - [BouffaloLabDevCube](https://dev.bouffalolab.com/download) **to flash the BL616**
+  - [Latest release](https://github.com/vossstef/A2600nano/releases/latest) of A2600Nano **FPGA** bitstream
+  - [Latest release](https://github.com/harbaum/MiSTeryNano/releases/latest) of MiSTeryNano **BL616 µC firmware** (if not otherwise stated in the release note.)
+
+In order to use the SD card:
+
+  - Cartridge images 
+
+# Flashing the Tang Nano 20k
+
+First download the Gowin IDE. The Education version is sufficient and
+won't need a licence.
+
+Install the IDE on your system (follow the installation instructions
+from Gowin).  After the Installation you should have it as an shortcut
+on your desktop or in your start menu.
+
+ - Press the ```S2``` button on the Tang Nano 20K and keep it pressed
+ - Connect the Tang Nano 20k to the USB on your computer. You should hear the connecting sound of Windows.
+ - Release the ```S2``` button
+ - Start Gowin. **You should see the following screen**
+
+![](https://github.com/vossstef/A2600Nano/blob/main/.assets/gowin1.jpg)
+
+Now press on the “programmer” marked red on the picture above. **You
+should see following screen:**
+
+![](https://github.com/vossstef/A2600Nano/blob/main/.assets/device.png)
+
+-   Press save on the dialog
+-   From there you can add a device for programming by pressing on the little
+    icon with the green plus
+-   At least one file have to be flashed:
+    - The core itself: ```A2600Nano.fs```
+-   Than you can choose from the drop downs the parameter you see on the
+    pictures.
+
+**Important**:
+
+  - ```A2600Nano.fs``` is written to address 0x000000
+
+
+  - For the FS file please choose the ```A2600Nano.fs``` you just downloaded
+  - User Code and IDCODE can be ignored
+  - Mark each of your configs and press the little icon with the green play
+    button. You should see a progress bar and then:
+
+![](https://github.com/vossstef/A2600Nano/blob/main/.assets/c64_flash.png)
+**At a glance the memory layout of the SPI Flash:**
+|                           | |          |          |         | | |
+|-                          |-         |-         |-         |-        |-|-|
+| Type                      | TN20k    | TP20k    |TP25k     | TM138k  |TN9k | |
+| FPGA bitstream            | 0x000000 | 0x000000 | 0x000000 | 0x000000 |-|ROM size |
+
+**shell / command line Programming alternative**
+
+Windows shell and Gowin Programmer<br>
+```programmer_cli  -r 36 --fsFile A2600Nano.fs --spiaddr 0x000000 --cable-index 1 --d GW2ANR-18C```<br>
+
+
+**That´s it for the Tang Nano 20k**
+
+## Flashing the BL616 µC
+
+For the BL616 you have to extract and start the BuffaloLabDevCube. 
+
+**If you use the internal BL616 present on the Tang Nano 20K you loose
+your possibility to flash the Tang over the USB connection.** It is thus
+strongly recommended to use an external BL616 (e.g. a M0S Dock).
+
+However, when using the internal BL616 you will be able to flash the
+[original firmware](https://github.com/harbaum/MiSTeryNano/blob/main/bl616/friend_20k)
+to the internal BL616 again to restore the flasher functionality of
+the Tang Nano 20K. Using an external M0S is nevertheless recommended.
+
+-   Press the ```BOOT``` button on your M0S Dock before you plug the USB connection
+    on your PC. You should hear the hardware detecting sound.
+-   Start the BuffaloLabDevCube from the directory where you decompressed it it
+    ask you what chip should be used. Select BL616/BL618 and press “finish”
+
+![](https://github.com/vossstef/A2600Nano/blob/main/.assets/buffstart.png)
+
+- You'll now see the program screen. On the right it should auto detect your
+  device with a COM port. If not take a look in the device manager to check for
+  the correct device detection.
+- On the top click on MCU and browse to the firmware image file named
+  ```misterynano_fw_bl616.bin``` (contains a unified firmware both for Atari ST and C64Nano and A2600Nano)
+- Choose “Open Uart” and than press “Create & Download”. The firmware should now be
+  flashed
+
+![](https://github.com/vossstef/A2600Nano/blob/main/.assets/bufffinish.png)
+
+## Prepare the SD card
+
+Format the SD card in FAT32. Copy your cartrige files files on
+it. You can organize your files in subdirectories. These files can later
+be selected using the on-screen-display (OSD).
+Default Mountpoints:  
+Copy a 2600 rom cartrige image to your sdcard and rename it to a2600crt.bin as default boot image.
+

LICENSE

@@ -1,21 +1,23 @@
-                    GNU AFFERO GENERAL PUBLIC LICENSE
-                       Version 3, 19 November 2007
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
 
  Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
  Everyone is permitted to copy and distribute verbatim copies
  of this license document, but changing it is not allowed.
 
                             Preamble
 
-  The GNU Affero General Public License is a free, copyleft license for
-software and other kinds of works, specifically designed to ensure
-cooperation with the community in the case of network server software.
+  The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
 
   The licenses for most software and other practical works are designed
 to take away your freedom to share and change the works.  By contrast,
-our General Public Licenses are intended to guarantee your freedom to
+the GNU General Public License is intended to guarantee your freedom to
 share and change all versions of a program--to make sure it remains free
-software for all its users.
+software for all its users.  We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors.  You can apply it to
+your programs, too.
 
   When we speak of free software, we are referring to freedom, not
 price.  Our General Public Licenses are designed to make sure that you
@@ -24,34 +26,44 @@ them if you wish), that you receive source code or can get it if you
 want it, that you can change the software or use pieces of it in new
 free programs, and that you know you can do these things.
 
-  Developers that use our General Public Licenses protect your rights
-with two steps: (1) assert copyright on the software, and (2) offer
-you this License which gives you legal permission to copy, distribute
-and/or modify the software.
-
-  A secondary benefit of defending all users' freedom is that
-improvements made in alternate versions of the program, if they
-receive widespread use, become available for other developers to
-incorporate.  Many developers of free software are heartened and
-encouraged by the resulting cooperation.  However, in the case of
-software used on network servers, this result may fail to come about.
-The GNU General Public License permits making a modified version and
-letting the public access it on a server without ever releasing its
-source code to the public.
-
-  The GNU Affero General Public License is designed specifically to
-ensure that, in such cases, the modified source code becomes available
-to the community.  It requires the operator of a network server to
-provide the source code of the modified version running there to the
-users of that server.  Therefore, public use of a modified version, on
-a publicly accessible server, gives the public access to the source
-code of the modified version.
-
-  An older license, called the Affero General Public License and
-published by Affero, was designed to accomplish similar goals.  This is
-a different license, not a version of the Affero GPL, but Affero has
-released a new version of the Affero GPL which permits relicensing under
-this license.
+  To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  You must make sure that they, too, receive
+or can get the source code.  And you must show them these terms so they
+know their rights.
+
+  Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+  For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+  Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so.  This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software.  The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable.  Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products.  If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+  Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary.  To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
 
   The precise terms and conditions for copying, distribution and
 modification follow.
@@ -60,7 +72,7 @@ modification follow.
 
   0. Definitions.
 
-  "This License" refers to version 3 of the GNU Affero General Public License.
+  "This License" refers to version 3 of the GNU General Public License.
 
   "Copyright" also means copyright-like laws that apply to other kinds of
 works, such as semiconductor masks.
@@ -537,45 +549,35 @@ to collect a royalty for further conveying from those to whom you convey
 the Program, the only way you could satisfy both those terms and this
 License would be to refrain entirely from conveying the Program.
 
-  13. Remote Network Interaction; Use with the GNU General Public License.
-
-  Notwithstanding any other provision of this License, if you modify the
-Program, your modified version must prominently offer all users
-interacting with it remotely through a computer network (if your version
-supports such interaction) an opportunity to receive the Corresponding
-Source of your version by providing access to the Corresponding Source
-from a network server at no charge, through some standard or customary
-means of facilitating copying of software.  This Corresponding Source
-shall include the Corresponding Source for any work covered by version 3
-of the GNU General Public License that is incorporated pursuant to the
-following paragraph.
+  13. Use with the GNU Affero General Public License.
 
   Notwithstanding any other provision of this License, you have
 permission to link or combine any covered work with a work licensed
-under version 3 of the GNU General Public License into a single
+under version 3 of the GNU Affero General Public License into a single
 combined work, and to convey the resulting work.  The terms of this
 License will continue to apply to the part which is the covered work,
-but the work with which it is combined will remain governed by version
-3 of the GNU General Public License.
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
 
   14. Revised Versions of this License.
 
   The Free Software Foundation may publish revised and/or new versions of
-the GNU Affero General Public License from time to time.  Such new versions
-will be similar in spirit to the present version, but may differ in detail to
+the GNU General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
 address new problems or concerns.
 
   Each version is given a distinguishing version number.  If the
-Program specifies that a certain numbered version of the GNU Affero General
+Program specifies that a certain numbered version of the GNU General
 Public License "or any later version" applies to it, you have the
 option of following the terms and conditions either of that numbered
 version or of any later version published by the Free Software
 Foundation.  If the Program does not specify a version number of the
-GNU Affero General Public License, you may choose any version ever published
+GNU General Public License, you may choose any version ever published
 by the Free Software Foundation.
 
   If the Program specifies that a proxy can decide which future
-versions of the GNU Affero General Public License can be used, that proxy's
+versions of the GNU General Public License can be used, that proxy's
 public statement of acceptance of a version permanently authorizes you
 to choose that version for the Program.
 
@@ -633,29 +635,40 @@ the "copyright" line and a pointer to where the full notice is found.
     Copyright (C) <year>  <name of author>
 
     This program is free software: you can redistribute it and/or modify
-    it under the terms of the GNU Affero General Public License as published
-    by the Free Software Foundation, either version 3 of the License, or
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
     (at your option) any later version.
 
     This program is distributed in the hope that it will be useful,
     but WITHOUT ANY WARRANTY; without even the implied warranty of
     MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-    GNU Affero General Public License for more details.
+    GNU General Public License for more details.
 
-    You should have received a copy of the GNU Affero General Public License
+    You should have received a copy of the GNU General Public License
     along with this program.  If not, see <https://www.gnu.org/licenses/>.
 
 Also add information on how to contact you by electronic and paper mail.
 
-  If your software can interact with users remotely through a computer
-network, you should also make sure that it provides a way for users to
-get its source.  For example, if your program is a web application, its
-interface could display a "Source" link that leads users to an archive
-of the code.  There are many ways you could offer source, and different
-solutions will be better for different programs; see section 13 for the
-specific requirements.
+  If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+    <program>  Copyright (C) <year>  <name of author>
+    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
 
   You should also get your employer (if you work as a programmer) or school,
 if any, to sign a "copyright disclaimer" for the program, if necessary.
-For more information on this, and how to apply and follow the GNU AGPL, see
+For more information on this, and how to apply and follow the GNU GPL, see
 <https://www.gnu.org/licenses/>.
+
+  The GNU General Public License does not permit incorporating your program
+into proprietary programs.  If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.  But first, please read
+<https://www.gnu.org/licenses/why-not-lgpl.html>.