Quick update: Well, the castellated boards look good after I deburred them. Took about 30 minutes to fully assemble one with hot air and solder paste. If I can make a solder mask I think I could do it even faster. Should be able to do several at a time in the $15 toaster oven once I get rolling but I am still waiting on my FLASH from China.. Tried to flash one this morning but keep having issues where Impact crashes or reports invalid ID on the chip.. Maybe my $20 programmer wasn't such a good deal. Could be an issue with the friction hold header pins. I plan on making a programming jig where I can put the boards face down on top of some contacts (metal screws) and quickly program them. We will see how that work.
On Sun, Oct 1, 2017 at 4:21 AM, Brian White <bw.al...@gmail.com> wrote: > Note, those directions are just the latest versions of everything I could > find. But as far as I can tell, and I think Stephen said as much in a post > sometime, that all the updates take the form of a full write, meaning you > can use any update also as a fresh/initial load or downgrade, not just to > update. > > So the end-user can switch to any version they want with no special tools > or software. > > So if you want one of the earlier versions instead of the last build > number of 4.9, you should be able to just install it, either as the builder > doing it the first time, or as the end-user wanting something different > than what the builder loaded. > > To flash any version of the firmware, you only need: > > * the update files (see bitchin100 and Stephen's directory on club100) > > * a modern pc (any os) running a tpdd server (laddie alpha, dlplus, etc) > > * serial connection (9f-25m "modem" cable, 9pin mini null-modem adapter, > any usb-serial adapter) > > And you needed all that stuff anyway just to load ordinary software. The > end-user can do it any time. > > You only need the special Xilinx programmer and software the very first > time you program the cpld (or I suppose if the cpld somehow ever gets wiped > or corrupted), so only the builder needs that, not the user. > > -- > bkw > > > > On Oct 1, 2017 3:14 AM, "Josh Malone" <josh.mal...@gmail.com> wrote: > >> The CPLD load is coded April 24, 2011 (no rst). The REX SW version is 4.9. >> >> http://tandy.wiki/Building_a_REX >> >> >> On Sat, Sep 30, 2017 at 5:25 PM, Georg Kaeter < >> georg.kae...@gk-engineering-services.de> wrote: >> >>> Is there an opportunity to get at least 3 of the "new REX" ? I would >>> like to update my M100 and 2 M102 with REX (I've already one running in my >>> M200). >>> Additional question: What Revision you're using for the generic >>> programming? >>> >>> Regards >>> Georg >>> >>> Am 30.09.2017 21:08 schrieb "Gregory McGill" <arcadeshop...@gmail.com>: >>> >>>> woohoo! good job Josh!! my 3 months of procrastination pays off :D >>>> >>>> Greg >>>> >>>> On Sat, Sep 30, 2017 at 8:26 AM, John R. Hogerhuis <jho...@pobox.com> >>>> wrote: >>>> >>>>> >>>>> On Sat, Sep 30, 2017 at 5:22 AM Josh Malone <josh.mal...@gmail.com> >>>>> wrote: >>>>> >>>>>> Success! I have a working REX built from the parts Greg sent. Turns >>>>>> out that my 102 has no memory issues -- rather, CoolTerm was being stupid >>>>>> about flow control and probably corrupting the transfer when I tried to >>>>>> load TSDOS before. The CPLD programming went swimmingly and the REX >>>>>> flashing was super easy thanks to mComm for Android (thanks Kurt!) >>>>>> >>>>>> Now I see what all the buzz is about with the REX. This is an awesome >>>>>> product Stephen! I can't wait to build more of them. >>>>>> >>>>> Congratulations Josh. The more people that can build a REX the better. >>>>> >>>>> Club100 is us. It was even when Rick was minding the store, but now >>>>> even more so. >>>>> >>>>> -- John. >>>>> >>>>> -- John. >>>>> >>>> >>>> >>
