Anonymous
User login
Please support the defense of Ukraine.
Direct or via Unclutter App
Active forum topics
Recent content
Navigation
No Ads.
No Trackers.
No Social Media.
All Content Locally Hosted.
Built on Free Software.
We have complied with zero government requests for information.
Noob question, Is it possible to have the configuration utility reside on the Pico as a config.bas file instead of manually typing it in or loading from a floppy?
<code>
10 HOME : PRINT "ENTER A2DVI SLOT (1-7): ";20 GET S30 IF (S<1) OR (S>7) THEN GOTO 2040 PRINT "LOOK AT YOUR A2DVI SCREEN!"50 VTAB 2160 S = -16256 + S*1670 POKE S+15,1180 POKE S+15,2290 POKE S+9,0100 GET A$110 C = ASC(A$)120 POKE S+9,C130 IF C <> 27 THEN GOTO 100140 POKE S+15,0150 HOME : PRINT "GOODBYE!"</code>
I took a look into this (thinking the same thing). I agree that it would be a useful mechanism to be able to enter PR#X to launch the configuration utility. However, based on 30 minutes of reading, I believe to get it to work the !IOSEL line from the edge connector would have to be connected to the PICO. The REV 2.0 hardware doesn't do this. If you look carefully at the REV 2.4 image on the A2DVI github page, (no schematic, so have to try and interpret traces on the PCB) I think you can see that trace from PIN 1 of the edge connector heading off to the PROM that was used for version 2.4 . I tend to think that a version with !IOSEL support (acting as an additional 256 byte PROM as part of the card being emulated) should be capable of that. But I'm not a dev on the project, so have little to no experience with the finer details of the code involved. (it was, afterall, only 30 (ish) minutes of investigation)Oh.. also just noted that v4.4 and 4.6 of the hardware, has the !IOSEL (and several other) signal routed to the PICO2. I think it safe to say.. EVERYONE was thinking the same thing... :)
Error, posted to wrong thread
Pages