Rattboi/fix makefile

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,26 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+## Bug Report
+
+### Expected Behavior
+
+What should it do?
+
+### Observed Behavior
+
+What did it actually do?
+
+### Steps to Reproduce
+
+How did you make it do that, and which firmware versions were used (git commit or release version)?
+
+### References
+
+Links to a video, or more info

.github/ISSUE_TEMPLATE/enhancement-request.md

@@ -0,0 +1,20 @@
+---
+name: Enhancement request
+about: Suggest an enhancement to an existing feature for this project
+title: ''
+labels: enhancement
+assignees: ''
+
+---
+
+**Is your enhancement request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest a new feature for this project
+title: ''
+labels: feature
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

CHANGELOG.md

@@ -23,7 +23,31 @@
 - Add hardware version support for pin definitions
 - Add 128KB bankswitching (V-INT pin)
 - Developer mode, allow the cart to stay plugged into a computer and appear as a RAMDISK
-- Figure out why Polar Rescue crashes when the sub launches
+
+## v0.23
+
+- Fixes issue where VEXTREME takes several minutes to mount as USB drive on Windows #53
+
+## v0.22
+
+- ignore all file extensions that are not .bin or .vec (case insensitive) #49
+- increased quick reset delay to 700ms #45 
+- adds HW/SW version to VEXTREME menu and games #48 
+  - see example in LED Test v1.1.bin
+
+## v0.21
+
+- :warning: Added NOTICE of Current Development
+- Fixes Polar Rescue and implements a new Reset Heurisic #37
+- Adds addressable LED control and demo #41
+    - added 3 functions to control the LEDs from a Vectrex program
+        - updateOne() - RPC 6
+        - updateAll() - RPC 4
+        - updateMulti() - RPC 7
+    - added RPC function 5 to step through rainbow control of LEDs in menu
+    - added "LED TEST" which uses updateMulti to show how to finely control
+    all of the LEDs with a test program.  Press UP on the joystick, try it slowly as well :D
+    - added addressable LED control to Veccy Bird v1.5
 
 ## v0.2
 

README.md

@@ -3,6 +3,11 @@ VEXTREME Vectrex Multicart
 
 We're carrying on and pushing forward the amazing work of [Sprite_tm](http://spritesmods.com/?art=veccart&page=1) and his Extreme Vectrex Multicart. He posted the code (GPLv3 License) and lots of screens of the PCB/initial schematic, but he never released the PCB. It's a great base for an inexpensive and open multicart, for developers and players alike!
 
+:warning: Please read this NOTICE of Current Development :warning:
+===
+
+**This project is a work in progress, and is not ready for mass production.**  Please observe the currently [posted issues](https://github.com/technobly/vextreme/issues) and there may be more lurking that are not yet identified.  The hardware and software is evolving.  You are free to build any version, contribute and/or follow along.  Please note that support of these pre-releases will be very limited and if you embark on an epic adventure to build one or a few, you should feel comfortable with this type of embedded hardware and software development.  There will be road bumps, but the journey is half the fun of the destination.  When things appear to be stable and we've worked out most of the kinks, we'll change the version to v1.0.  Only then is it advisable to mass produce.
+
 3D Renders
 ===
 
@@ -13,15 +18,16 @@ Video Updates
 
 Be sure to subscribe to my Youtube channel for updates!  Here's my [Vectrex playlist](https://www.youtube.com/watch?v=zkJ-z77fJCw&list=PL7MgXfpGKg6CCaIQejZVb5CsTg3-5mHU0&index=1) if you want to stay laser focused on this project.
 
+VEXTREME Discord Server
+===
+Join the [VEXTREME Discord server](https://discord.gg/VDssGVJ) to chat with us about the development
+
 BOM and Parts ordering
 ===
 
 All the parts are described in [veccart.csv](bom/veccart.csv)
 
-Also, you can use this [Digi-Key shared cart](https://www.digikey.com/short/pv2qr0) if you're in a hurry.  It has will have part references right on the packages for you!
-
-:pencil: Note: The USB-C connector I chose is not available at Digi-Key, check Google for "Korean Hroparts Elec TYPE-C-31-M-12".
-
+Also, you can use this [Digi-Key shared cart](https://www.digikey.com/short/zpdmtp) if you're in a hurry.  It has will have part references right on the packages for you!
 
 Ordering PCB's
 ===
@@ -36,8 +42,9 @@ Building and Flashing STM firmware
 ### This assumes you have these prerequisits installed:
 
 - Docker
-- dfu-util
+- dfu-util v0.9
 - Make
+- Windows will also require these [Zadig instructions](https://github.com/profezzorn/ProffieOS/wiki/zadig)
 
 ### Build the stm32-build docker image
 ```
@@ -66,7 +73,9 @@ Found DFU: [0483:df11] ver=2200, devnum=22, cfg=1, intf=0, path="20-1.4.3", alt=
 
 ### Build and flash the STM32 image via dfu-util
 ```
-code/veccart $ make clean all flash
+code/veccart $ make clean all flash USE_HW=v0.3
+
+// NOTE: Use v0.2 above if you have v0.2 HW, or you may use v0.3 if you make the proper mods to your board.  See "Modifying v0.2 to v0.3"
 
 // You should end up with something like this
 
@@ -94,6 +103,7 @@ code/multicart $ make docker-build
   - Name: VEXTREME
   - Format: MS-DOS (FAT)
   - Scheme: Master Boot Record
+  - 512 byte page size
 
 - Be patient, it's slow!  Don't worry, copying binaries later will be fast!!
 
@@ -114,6 +124,16 @@ code/multicart $ make copy
 asm6809  -B -o multicart.bin multicart.asm
 ```
 
+Modifying v0.2 to v0.3
+===
+
+![v0.3 Mod 1](images/v0.3-mod1.png)
+
+- To get the new reset feature of v0.3, as of v0.24 software you will need to jumper V-OE pin 12 of the cart fingers (or U3 pin 9) to STM32 pin 29 (PB10).  This may change in the future, don't sell your soldering iron!
+- The wire mod above also allows you to play Animaction on VEXTREME!
+- More TBD
+
+
 Adding Vectrex Game ROMs (Binaries)
 ===
 

_config.yml

@@ -0,0 +1 @@
+theme: jekyll-theme-cayman

code/ci/release.sh

@@ -0,0 +1,91 @@
+#!/bin/bash
+
+# Usage:
+# $ USE_SW=<tagged-version-to-release> ./release.sh
+# Example: USE_SW=v0.24 ./release.sh
+
+# we are going for the 3 fingered claw approach (try <task>)
+yell() { echo "$0: $*" >&2; }
+die() { yell "$*"; fail; exit 111; }
+try() { "$@" || die "cannot $*"; }
+
+GRN="\033[32m"
+RED="\033[31m"
+NOC="\033[0m"
+
+# Execute in ci/ folder
+STM32_DIR=../veccart
+MENU_DIR=../multicart
+RELEASE_DIR=../releases
+SOURCE_RELEASE=v0.23
+SOURCE_RELEASE_URL=https://github.com/technobly/VEXTREME/releases/download/v0.23/VEXTREME-v0.23.zip
+: ${USE_SW:?"REQUIRED! Usage: USE_VER=v0.24 ./release.sh"}
+
+main() {
+    try rm -rf $RELEASE_DIR/$USE_SW
+    try rm -f $RELEASE_DIR/vextreme-$USE_SW.zip
+    if [ ! -d "$RELEASE_DIR/$SOURCE_RELEASE" ]; then
+        if [ ! -e "$RELEASE_DIR/VEXTREME-v0.23.zip" ]; then
+            cd $RELEASE_DIR
+            curl -L "$SOURCE_RELEASE_URL" > "VEXTREME-v0.23.zip"
+            unzip VEXTREME-v0.23.zip
+        fi
+    fi
+
+    USE_HW=v0.2
+    try cd $STM32_DIR
+    try make clean all USE_HW=$USE_HW -s #&> /dev/null
+    try mkdir -p $RELEASE_DIR
+    try mkdir -p $RELEASE_DIR/$USE_SW
+    try mkdir -p $RELEASE_DIR/$USE_SW/stm32
+    try mkdir -p $RELEASE_DIR/$USE_SW/stm32/hardware-$USE_HW
+    try cp veccart.bin $RELEASE_DIR/$USE_SW/stm32/hardware-$USE_HW/stm32-sw.$USE_SW.hw.$USE_HW.bin
+    try cp veccart.elf $RELEASE_DIR/$USE_SW/stm32/hardware-$USE_HW/stm32-sw.$USE_SW.hw.$USE_HW.elf
+    try cp veccart.hex $RELEASE_DIR/$USE_SW/stm32/hardware-$USE_HW/stm32-sw.$USE_SW.hw.$USE_HW.hex
+    try cp veccart.list $RELEASE_DIR/$USE_SW/stm32/hardware-$USE_HW/stm32-sw.$USE_SW.hw.$USE_HW.list
+
+    USE_HW=v0.3
+    try make clean all -s USE_HW=$USE_HW #&> /dev/null
+    try mkdir -p $RELEASE_DIR/$USE_SW/stm32/hardware-$USE_HW
+    try cp veccart.bin $RELEASE_DIR/$USE_SW/stm32/hardware-$USE_HW/stm32-sw.$USE_SW.hw.$USE_HW.bin
+    try cp veccart.elf $RELEASE_DIR/$USE_SW/stm32/hardware-$USE_HW/stm32-sw.$USE_SW.hw.$USE_HW.elf
+    try cp veccart.hex $RELEASE_DIR/$USE_SW/stm32/hardware-$USE_HW/stm32-sw.$USE_SW.hw.$USE_HW.hex
+    try cp veccart.list $RELEASE_DIR/$USE_SW/stm32/hardware-$USE_HW/stm32-sw.$USE_SW.hw.$USE_HW.list
+
+    try cd $MENU_DIR
+    try make clean all #&> /dev/null
+    try mkdir -p $RELEASE_DIR/$USE_SW/VEXTREME
+    try cp multicart.bin $RELEASE_DIR/$USE_SW/VEXTREME/multicart.bin
+    try cp $RELEASE_DIR/$SOURCE_RELEASE/VEXTREME/vec.bin $RELEASE_DIR/$USE_SW/VEXTREME/vec.bin
+    try cp -R $RELEASE_DIR/$SOURCE_RELEASE/VEXTREME/roms $RELEASE_DIR/$USE_SW/VEXTREME/roms
+
+    try cd $RELEASE_DIR
+    try zip -vr VEXTREME-$USE_SW.zip $USE_SW -x "*.DS_Store" #&> /dev/null
+
+    pass
+    return 0;
+}
+
+pass() {
+    echo -e ${GRN}' 8888888b.     d8888  .d8888b.   .d8888b. '${NOC}
+    echo -e ${GRN}' 888   Y88b   d88888 d88P  Y88b d88P  Y88b '${NOC}
+    echo -e ${GRN}' 888    888  d88P888 Y88b.      Y88b. '${NOC}
+    echo -e ${GRN}' 888   d88P d88P 888  "Y888b.    "Y888b. '${NOC}
+    echo -e ${GRN}' 8888888P" d88P  888     "Y88b.     "Y88b. '${NOC}
+    echo -e ${GRN}' 888      d88P   888       "888       "888 '${NOC}
+    echo -e ${GRN}' 888     d8888888888 Y88b  d88P Y88b  d88P '${NOC}
+    echo -e ${GRN}' 888    d88P     888  "Y8888P"   "Y8888P" '${NOC}
+}
+
+fail() {
+    echo -e ${RED}' 8888888888     d8888 8888888 888      888 '${NOC}
+    echo -e ${RED}' 888           d88888   888   888      888 '${NOC}
+    echo -e ${RED}' 888          d88P888   888   888      888 '${NOC}
+    echo -e ${RED}' 8888888     d88P 888   888   888      888 '${NOC}
+    echo -e ${RED}' 888        d88P  888   888   888      888 '${NOC}
+    echo -e ${RED}' 888       d88P   888   888   888      Y8P '${NOC}
+    echo -e ${RED}' 888      d8888888888   888   888       "  '${NOC}
+    echo -e ${RED}' 888     d88P     888 8888888 88888888 888 '${NOC}
+}
+
+main

code/dev/devmode/.gitignore

@@ -0,0 +1,2 @@
+*.bin
+*.lst

code/dev/devmode/Dockerfile

@@ -0,0 +1,15 @@
+FROM alpine:3.9.4
+
+RUN apk add --no-cache --virtual .build-deps build-base wget \
+    && wget -O asm6809.tar.gz http://www.6809.org.uk/asm6809/dl/asm6809-2.12.tar.gz \
+    && tar -xvf asm6809.tar.gz -C /tmp \
+    && rm asm6809.tar.gz \
+    && cd /tmp/asm6809-2.12 \
+    && ./configure \
+    && make \
+    && make install \
+    && rm -rf /tmp/asm6809-2.12 \
+    && apk del .build-deps \
+    && apk add --no-cache make
+
+WORKDIR /build

code/dev/devmode/Makefile

@@ -0,0 +1,24 @@
+# This uses asm6809 from
+# http://www.6809.org.uk/asm6809/dl/2.3/
+AS = asm6809
+
+default: docker
+
+docker-build: Dockerfile
+	docker build . -t asm6809
+
+all: docker
+
+docker:
+	docker run --rm -v `pwd`:/build -u `id -u ${USER}`:`id -g ${USER}` asm6809 make devmode.bin
+
+devmode.bin: devmode.asm
+	$(AS)  -B -o $@ $^
+
+clean:
+	rm -f devmode.bin
+
+copy: led-test.bin
+	sudo mount /dev/sde1 /mnt
+	sudo cp devmode.bin /mnt
+	sudo umount /mnt