Jump to content

mr-atari

Members
  • Posts

    1,202
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by mr-atari

  1. On 11/18/2019 at 11:03 PM, tschak909 said:

    How's does the relocation work? I really need a chalk-talk, as I need to write a CIO handler for the R: and N: handlers for #FujiNet.

    -Thom

    For the R: handler, just drop a line if you need help.

    I have send you a couple of version to try.

    But until now, no feedback.

     

    Relocation is a bit of a pita, you have to use MEMLO and update the loaded driver accordingly.

    Then move it to the position of MEMLO, avoiding overwriting your own code or someone else, then adjust MEMLO to the new values.

    If BASIC or other software has already booted, they need to be cold initialized to except the new boundaries.

     

    I have an ESP8266 R: version that is relocatable, but the buffer is 256 bytes (fixed) and you did not want that.

     

    Grtz.

    • Like 1
  2. 1 hour ago, flashjazzcat said:

    We are talking about JMP ($0A) here? You throw an error there?

    No, it's a RTS back to DUP.

     

    JMP($0A) points to DUPDUP

     

    "Fake error-message" ;-)

     

    ;-------------------------------------------------------------------
    ;	LOAD FILE
    ;-------------------------------------------------------------------
    
    DUPLOA	JSR	BLOAD		;RETURN (RTS) HERE WHEN NO RUN-ADDRESS
    
    ;-------------------------------------------------------------------
    ;	DUP ENTRY, CHECK ERRORS
    ;-------------------------------------------------------------------
    
    DUPV	JSR	DUPBAD		;SHOW ERROR-CODE
    
    DUPDUP	LDA	#EDBUF&$FF	;ALL IO, EDBUF
    	STA	ICBAL
    	LDA	#EDBUF/256
    	STA	ICBAH

     

  3. No, it's not a bug, and it does not hang either.

    TBXL jumps back into DUP with Y set to 168.

    LiteDOS sees Y<>1 as an error.....

    Plus LiteDOS/DUP does not opens E:, assuming a clean gr.0 layout, this leaving the screen set to the last application.

     

    Sneak preview:

    LiteDOS 3.00 will have LZ4 decompression build-in the file loading routines.
    There will be a LiteDUP available that runs separate from LiteDOS.

    The "DUP" inside LiteDOS will be available for loading and directory listings only.

     

    I expect to have this uploaded December or early 2020.

    ?

    • Like 1
  4. On 11/5/2019 at 10:07 PM, tschak909 said:

    Thanks! :)

     

    Question for the SIO wizards in the group, I need to diagnose SIO timing issues, for example, if I disable all of the debug processing, all SIO activity fails.

     

    Do I need to grab a logic analyzer? or is there something I can use to help diagnose the timing issues?

    -Thom

    Technical reference notes.

    Pages 150-152

  5. Ok, fixed, current download will give you 38k free RAM.

     

    In the LiteDOS zip-file you find 2 other TBXL versions, compiled at $1100 and $1200.

    This is for users who want to reserve RAM for other things, like drivers or own usage.

    Again, Thanks to DMSC for the TBXL-versions.

     

    GOBO: Thanks for the report.

     

    image.png.fcb5cb1baf1fb7d9945be0e84462f6e0.png

    • Like 2
  6. Yes, you are right.

    Somehow the version of TBXL I have put on the download does not want to start.

    Very strange.....

     

    I will remove the download an upload a new one later this weekend.

    In the mean-time, here is the TBXL loading at $1000 I got from DMSC.

    That should have been on the disk and works just fine.

    Again, very strange....

    tb-10.com

  7. On 10/15/2019 at 12:46 AM, gobo said:

    Actually I tried LitDOS 2.08 with TBXL again but  this time using the TBXL.XEX file from the LiteDOS 2.05 ATR and it works. I guess there is something wrong with the TBXL.XEX file on the LiteDOS2.08 ATR and nothing wrong with LiteDOS 2.08 itself.

    Ok, I will check.

    Been away for some time (on my hols), I did not check AA for a while.

     

    If needed, here is a version compiled by DMSC at $0c00 for LiteDOS-XS

    You can take/use the compiler and runtime from the 2.08 disk.

     

    Plans are to upload the read-only version of LiteDOS soon.

    It can read only, so for games/apps that need to load files, or as gamedos.

    Memlo will be $0a00 for this version.

    Need to shuffle some routines around to make it work with overwriting programs, avoiding the loading routines....

     

    Grtz,

    Sijmen.

     

    tb-0C.com

    • Like 1
  8. I forgot to mention the AUX-codes for these baudrates.

    They are $08 though $0F, $08 being 600 baud and $0F 19k2

     

    So you need to use $0F, for selecting 19k2.

    Your buffer can start as low as $900

     

    Actually my driver only checks the lower 3 bits, so 8 available baudrates, those obscure <300baudrates are not supported.

  9. I have set mine now to 4800, let see what it brings.

     

    Yours (Thom) was set to 2400 before I shipped it.

    It has a sticker on it with "2400", to remind you of setting plato to 2400. ;-)

     

    Success on updating the firmware on the ESP. I leave it like it is.

    Meaning the long TTY sequence of logging onto a BBS or Plato.

    Don't know how/Don't dare to update.

    So, please, get the TTY-modus of plato in line with the ESP logon sequence, thanks.

     

    (Just thinking out loud, when you set the ESP to 19k2, you could install a firmware that boot-straps and send the driver to the Atari as the 850 does.....)

     

    Later!

  10. The tiny-terminal inside my driver is because PLATO can not connect the ESP to the server using it's TTY.

    Before the ESP get's transparent you need to send the CIPSEND-command, and that is impossible.

    PLATO is already connected to the server and data is ging back/forth (after the CIPSTART-command).

    Thus making it impossible to send (any) line of text.

     

    So, until this is solved, I need to connect to the server with the tiny-terminal.

    Then press ESC, PLATO sees the connection and starts immediately, skipping TTY.

     

    ESP-driver:

    Memory-wise, it uses page 7 and 8 for code and page 9 for buffer (roughly).

    Page 9 is free, when the user supports it's own buffer size/place.

     

    ESP, out of the box:

    This is a bit of a hassle, since you buy it set to 115k and every AT-hard-reset will set it back to 115k.

    The ATARI (PAL) can't do 115k and the NTSC flaky (just in/out-side serial specification).

    So I wrote a small program that does a simulated 115k bitrate, mixing the pokey's available 111k and 127k bitrate.

    Sending the command to the ESP to go down to 1200 (1221 to be axact, lower values are wrongly accepted by the ESP, DO NOT TRY!!).

    I can easily change this to 2400, 4800 or any other (unbound) bitrate for PLATO.

     

    Grtz, Sijmen.

  11. OK, here are my w.i.p. versions:

    I do have the impression, PLATO has changed internally and the server interaction is different.

    (Perhaps that's why FAST-IO 1.2 stopped working.)

     

    Anyhow, I tested 9600 baud and that goes OK.

     

    Baudrates 300-600-1200-2400-4800-9600 supported by the driver.

    Colors in the background, just to check if transmission still goes.

    (300 and 600 are not supported by the ESP, but I have included them for R-verters)

    PLATOTERM-LITE-ATARI-1.3-NOTOUCH-FASTIO.rom FASTIO.ASM R-ESP.ATR

    • Like 2
  12. My question about translation is for the driver.

    Currently it only supports RAW and sends Error-146 if something else is chosen.

    If plato uses it in TTY-mode, then I have to add this.

     

    Variable buffer/size and location already works, as changing the baudrate.

    But changing the baudrate only is to match the atari with the ESP.

    Changing the baudrate on the ESP is done with an AT-command.

     

    Work in progress and quit working OK:

    R-driver as bootable disk.

    Patched FAST-IO in a 1.3 version NOTOUCH, GET BYTE and STATUS only.

     

    Later!

  13. I posted this on facebook, small change to the schematics, the 3.3v regulator is to week.

    "I currently use the LM2937 (500mA), because the 2950 (100mA) kept resetting the ESP for 1-2 minutes before it stayed ON....
    And changed the 10 uF to 0.1 uF, removed the 0.1 uF between 5vReady and ground."

     

    I have put the board vertically in the SIO-plug, that just fits.

    The 7404 can be a SMD-version, but I have put a DIL in the gap on the other side.

     

    DSC08284.JPG

    DSC08285.JPG

    • Like 1
  14. On 9/23/2019 at 9:34 PM, tschak909 said:

     

    Which interface are you using? Apparently only the Atari 850 handler correctly uses the whole 2048 byte buffer allotted to concurrent mode. Seriously, the more I deal with Atari R: and RS232, the more I get angry at just how ham-strung the whole design was.

    Short question:

    Why is PLATO 1.3 reserving $C00 buffer (3k) instead of your 2048 mentioned above?

×
×
  • Create New...