home.social

#lt6502b — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #lt6502b, aggregated by home.social.

  1. WOOT!

    Sorted the bugs (intermittent framing issue when sending) and added TX_BUSY status bit.

    Here you can see me checking connectivity and then connecting to a simple BBS (this is the console on my laptop).

    I do think I'm getting buffer overflows on some servers (m68k one and a couple of others) but this one worked a treat!

    So next I need to write a terminal emulator (which I am not looking forward to).

    #LT6502b #Retrocomputing #BBS

  2. WOOT!

    Sorted the bugs (intermittent framing issue when sending) and added TX_BUSY status bit.

    Here you can see me checking connectivity and then connecting to a simple BBS (this is the console on my laptop).

    I do think I'm getting buffer overflows on some servers (m68k one and a couple of others) but this one worked a treat!

    So next I need to write a terminal emulator (which I am not looking forward to).

    #LT6502b #Retrocomputing #BBS

  3. WOOT!

    Sorted the bugs (intermittent framing issue when sending) and added TX_BUSY status bit.

    Here you can see me checking connectivity and then connecting to a simple BBS (this is the console on my laptop).

    I do think I'm getting buffer overflows on some servers (m68k one and a couple of others) but this one worked a treat!

    So next I need to write a terminal emulator (which I am not looking forward to).

    #LT6502b #Retrocomputing #BBS

  4. WOOT!

    Sorted the bugs (intermittent framing issue when sending) and added TX_BUSY status bit.

    Here you can see me checking connectivity and then connecting to a simple BBS (this is the console on my laptop).

    I do think I'm getting buffer overflows on some servers (m68k one and a couple of others) but this one worked a treat!

    So next I need to write a terminal emulator (which I am not looking forward to).

    #LT6502b #Retrocomputing #BBS

  5. WOOT!

    Sorted the bugs (intermittent framing issue when sending) and added TX_BUSY status bit.

    Here you can see me checking connectivity and then connecting to a simple BBS (this is the console on my laptop).

    I do think I'm getting buffer overflows on some servers (m68k one and a couple of others) but this one worked a treat!

    So next I need to write a terminal emulator (which I am not looking forward to).

    #LT6502b #Retrocomputing #BBS

  6. oOO, Getting closer to a working CPLD/WiFi modem for my 6502 Laptop
    got a couple of bugs that are irritating.

    Here I'm connecting to a BBS using BASIC to send the ATDT command and then display what comes back from the modem.

    #LT6502b
    #Retrocomputing

  7. oOO, Getting closer to a working CPLD/WiFi modem for my 6502 Laptop
    got a couple of bugs that are irritating.

    Here I'm connecting to a BBS using BASIC to send the ATDT command and then display what comes back from the modem.

    #LT6502b
    #Retrocomputing

  8. oOO, Getting closer to a working CPLD/WiFi modem for my 6502 Laptop
    got a couple of bugs that are irritating.

    Here I'm connecting to a BBS using BASIC to send the ATDT command and then display what comes back from the modem.

    #LT6502b
    #Retrocomputing

  9. oOO, Getting closer to a working CPLD/WiFi modem for my 6502 Laptop
    got a couple of bugs that are irritating.

    Here I'm connecting to a BBS using BASIC to send the ATDT command and then display what comes back from the modem.

    #LT6502b
    #Retrocomputing

  10. oOO, Getting closer to a working CPLD/WiFi modem for my 6502 Laptop
    got a couple of bugs that are irritating.

    Here I'm connecting to a BBS using BASIC to send the ATDT command and then display what comes back from the modem.

    #LT6502b
    #Retrocomputing

  11. Well a lot of work on #LT6502b today.
    Now running at 10MHz (up from 7MHz), Keyboard now working and I can receive data from the WiFi Modem.
    Next is making the CPLD transmit to the WiFi Modem.
    Then trying to figure out why I can't run at 14MHz...

    #Retrocomputing #6502

  12. Well a lot of work on #LT6502b today.
    Now running at 10MHz (up from 7MHz), Keyboard now working and I can receive data from the WiFi Modem.
    Next is making the CPLD transmit to the WiFi Modem.
    Then trying to figure out why I can't run at 14MHz...

    #Retrocomputing #6502

  13. Well a lot of work on #LT6502b today.
    Now running at 10MHz (up from 7MHz), Keyboard now working and I can receive data from the WiFi Modem.
    Next is making the CPLD transmit to the WiFi Modem.
    Then trying to figure out why I can't run at 14MHz...

    #Retrocomputing #6502

  14. Well a lot of work on #LT6502b today.
    Now running at 10MHz (up from 7MHz), Keyboard now working and I can receive data from the WiFi Modem.
    Next is making the CPLD transmit to the WiFi Modem.
    Then trying to figure out why I can't run at 14MHz...

    #Retrocomputing #6502

  15. Well a lot of work on #LT6502b today.
    Now running at 10MHz (up from 7MHz), Keyboard now working and I can receive data from the WiFi Modem.
    Next is making the CPLD transmit to the WiFi Modem.
    Then trying to figure out why I can't run at 14MHz...

    #Retrocomputing #6502

  16. IT WORKS!!!

    With a bit of effort I can now receive data from the UART on my keyboard controller, into the CPLD and read it form BASIC on my 6502 laptop revision b (slim version).

    I've set the Keyboard controller to output characters from $20 to $7F, here you can see them being shown.

    There is also a "new data received" status register too!

    #CPLD #LT6502B

  17. IT WORKS!!!

    With a bit of effort I can now receive data from the UART on my keyboard controller, into the CPLD and read it form BASIC on my 6502 laptop revision b (slim version).

    I've set the Keyboard controller to output characters from $20 to $7F, here you can see them being shown.

    There is also a "new data received" status register too!

    #CPLD #LT6502B

  18. IT WORKS!!!

    With a bit of effort I can now receive data from the UART on my keyboard controller, into the CPLD and read it form BASIC on my 6502 laptop revision b (slim version).

    I've set the Keyboard controller to output characters from $20 to $7F, here you can see them being shown.

    There is also a "new data received" status register too!

    #CPLD #LT6502B

  19. IT WORKS!!!

    With a bit of effort I can now receive data from the UART on my keyboard controller, into the CPLD and read it form BASIC on my 6502 laptop revision b (slim version).

    I've set the Keyboard controller to output characters from $20 to $7F, here you can see them being shown.

    There is also a "new data received" status register too!

    #CPLD #LT6502B

  20. IT WORKS!!!

    With a bit of effort I can now receive data from the UART on my keyboard controller, into the CPLD and read it form BASIC on my 6502 laptop revision b (slim version).

    I've set the Keyboard controller to output characters from $20 to $7F, here you can see them being shown.

    There is also a "new data received" status register too!

    #CPLD #LT6502B

  21. Well the CPLD UART is coming along, another big step... Now when it's done receiving a byte, it transfers it to a register, which can then be read at anytime by the CPU. So that the CPU doesn't read garbage if it tries to read mid transfer (double buffer).

    more to do yet as I need two such registers and I also want the register to be cleared once it's been read, but this is BIG progress.

    This is all done in WINCUPL, not VHDL/Verilog.

    #CPLD #LT6502b

  22. Well the CPLD UART is coming along, another big step... Now when it's done receiving a byte, it transfers it to a register, which can then be read at anytime by the CPU. So that the CPU doesn't read garbage if it tries to read mid transfer (double buffer).

    more to do yet as I need two such registers and I also want the register to be cleared once it's been read, but this is BIG progress.

    This is all done in WINCUPL, not VHDL/Verilog.

    #CPLD #LT6502b

  23. Well the CPLD UART is coming along, another big step... Now when it's done receiving a byte, it transfers it to a register, which can then be read at anytime by the CPU. So that the CPU doesn't read garbage if it tries to read mid transfer (double buffer).

    more to do yet as I need two such registers and I also want the register to be cleared once it's been read, but this is BIG progress.

    This is all done in WINCUPL, not VHDL/Verilog.

    #CPLD #LT6502b

  24. Well the CPLD UART is coming along, another big step... Now when it's done receiving a byte, it transfers it to a register, which can then be read at anytime by the CPU. So that the CPU doesn't read garbage if it tries to read mid transfer (double buffer).

    more to do yet as I need two such registers and I also want the register to be cleared once it's been read, but this is BIG progress.

    This is all done in WINCUPL, not VHDL/Verilog.

    #CPLD #LT6502b

  25. Well the CPLD UART is coming along, another big step... Now when it's done receiving a byte, it transfers it to a register, which can then be read at anytime by the CPU. So that the CPU doesn't read garbage if it tries to read mid transfer (double buffer).

    more to do yet as I need two such registers and I also want the register to be cleared once it's been read, but this is BIG progress.

    This is all done in WINCUPL, not VHDL/Verilog.

    #CPLD #LT6502b

  26. Well, I've not found a suitable UART speed for comms between the 20MHz AVR for keyboard and modem and the CPLD, it's 55336 baud, the AVR has a 0.4% error which gives 55556 baud, which *should* be ok with the CPLD running on a divided down 28.332MHz.
    So it spits out 1 ASCII character a second to the CPLD.
    Later this week I'll get the UART code into the CPLD and write a bit of basic to read it, hopefully it works.
    #Retrocomputing #LT6502b #ILaughAtStandards

  27. Well, I've not found a suitable UART speed for comms between the 20MHz AVR for keyboard and modem and the CPLD, it's 55336 baud, the AVR has a 0.4% error which gives 55556 baud, which *should* be ok with the CPLD running on a divided down 28.332MHz.
    So it spits out 1 ASCII character a second to the CPLD.
    Later this week I'll get the UART code into the CPLD and write a bit of basic to read it, hopefully it works.
    #Retrocomputing #LT6502b #ILaughAtStandards

  28. Well, I've not found a suitable UART speed for comms between the 20MHz AVR for keyboard and modem and the CPLD, it's 55336 baud, the AVR has a 0.4% error which gives 55556 baud, which *should* be ok with the CPLD running on a divided down 28.332MHz.
    So it spits out 1 ASCII character a second to the CPLD.
    Later this week I'll get the UART code into the CPLD and write a bit of basic to read it, hopefully it works.
    #Retrocomputing #LT6502b #ILaughAtStandards

  29. Well, I've not found a suitable UART speed for comms between the 20MHz AVR for keyboard and modem and the CPLD, it's 55336 baud, the AVR has a 0.4% error which gives 55556 baud, which *should* be ok with the CPLD running on a divided down 28.332MHz.
    So it spits out 1 ASCII character a second to the CPLD.
    Later this week I'll get the UART code into the CPLD and write a bit of basic to read it, hopefully it works.
    #Retrocomputing #LT6502b #ILaughAtStandards

  30. Well, I've not found a suitable UART speed for comms between the 20MHz AVR for keyboard and modem and the CPLD, it's 55336 baud, the AVR has a 0.4% error which gives 55556 baud, which *should* be ok with the CPLD running on a divided down 28.332MHz.
    So it spits out 1 ASCII character a second to the CPLD.
    Later this week I'll get the UART code into the CPLD and write a bit of basic to read it, hopefully it works.
    #Retrocomputing #LT6502b #ILaughAtStandards

  31. Ok, so, I have the next part working of my CPLD UART... it now populates a buffer, with the correct values!!
    Green = serial in (LSB first),
    Orange is parallel out (LSB at the bottom)

    Next step is to transfer that to a register that can be read!

    I will probably up my sample clock to 16x, as that seems like the common thing, and 4x may not be 100% reliable. But for simulation, 4x is enough.

    #CPLD #LT6502b

  32. Ok, so, I have the next part working of my CPLD UART... it now populates a buffer, with the correct values!!
    Green = serial in (LSB first),
    Orange is parallel out (LSB at the bottom)

    Next step is to transfer that to a register that can be read!

    I will probably up my sample clock to 16x, as that seems like the common thing, and 4x may not be 100% reliable. But for simulation, 4x is enough.

    #CPLD #LT6502b

  33. Ok, so, I have the next part working of my CPLD UART... it now populates a buffer, with the correct values!!
    Green = serial in (LSB first),
    Orange is parallel out (LSB at the bottom)

    Next step is to transfer that to a register that can be read!

    I will probably up my sample clock to 16x, as that seems like the common thing, and 4x may not be 100% reliable. But for simulation, 4x is enough.

    #CPLD #LT6502b

  34. Ok, so, I have the next part working of my CPLD UART... it now populates a buffer, with the correct values!!
    Green = serial in (LSB first),
    Orange is parallel out (LSB at the bottom)

    Next step is to transfer that to a register that can be read!

    I will probably up my sample clock to 16x, as that seems like the common thing, and 4x may not be 100% reliable. But for simulation, 4x is enough.

    #CPLD #LT6502b

  35. Ok, so, I have the next part working of my CPLD UART... it now populates a buffer, with the correct values!!
    Green = serial in (LSB first),
    Orange is parallel out (LSB at the bottom)

    Next step is to transfer that to a register that can be read!

    I will probably up my sample clock to 16x, as that seems like the common thing, and 4x may not be 100% reliable. But for simulation, 4x is enough.

    #CPLD #LT6502b

  36. Fun with WinSim.

    After much battling with dodgy tools from the 90s, I've now got two useful signals. One to start the UART receive and it's counter, and one to stop when the 10th bit is received.

    Tomorrow, shift register to capture the bits.

    #Retrocomputing #LT6502b #CPLD

  37. Fun with WinSim.

    After much battling with dodgy tools from the 90s, I've now got two useful signals. One to start the UART receive and it's counter, and one to stop when the 10th bit is received.

    Tomorrow, shift register to capture the bits.

    #Retrocomputing #LT6502b #CPLD

  38. Fun with WinSim.

    After much battling with dodgy tools from the 90s, I've now got two useful signals. One to start the UART receive and it's counter, and one to stop when the 10th bit is received.

    Tomorrow, shift register to capture the bits.

    #Retrocomputing #LT6502b #CPLD

  39. Fun with WinSim.

    After much battling with dodgy tools from the 90s, I've now got two useful signals. One to start the UART receive and it's counter, and one to stop when the 10th bit is received.

    Tomorrow, shift register to capture the bits.

    #Retrocomputing #LT6502b #CPLD

  40. Fun with WinSim.

    After much battling with dodgy tools from the 90s, I've now got two useful signals. One to start the UART receive and it's counter, and one to stop when the 10th bit is received.

    Tomorrow, shift register to capture the bits.

    #Retrocomputing #LT6502b #CPLD

  41. I've been trying to get my KeyScan (ATMEGA644P) to output onto the 65c02 databus at the correct time and for the correct duration...
    I don't think it's going to work, sometimes I get no data back, when I tweak the timing I somehow get a 16bit value back (impressive from an 8 bit CPU eh?).

    So, I may have to put a UART into the CPLD, and "WinSim" doesn't seem to simulate properly. So it'll be try and keep trying until it works, or I run out of space.

    Has anyone done a UART in a CPLD?

    #LT6502b

  42. I've been trying to get my KeyScan (ATMEGA644P) to output onto the 65c02 databus at the correct time and for the correct duration...
    I don't think it's going to work, sometimes I get no data back, when I tweak the timing I somehow get a 16bit value back (impressive from an 8 bit CPU eh?).

    So, I may have to put a UART into the CPLD, and "WinSim" doesn't seem to simulate properly. So it'll be try and keep trying until it works, or I run out of space.

    Has anyone done a UART in a CPLD?

    #LT6502b

  43. I've been trying to get my KeyScan (ATMEGA644P) to output onto the 65c02 databus at the correct time and for the correct duration...
    I don't think it's going to work, sometimes I get no data back, when I tweak the timing I somehow get a 16bit value back (impressive from an 8 bit CPU eh?).

    So, I may have to put a UART into the CPLD, and "WinSim" doesn't seem to simulate properly. So it'll be try and keep trying until it works, or I run out of space.

    Has anyone done a UART in a CPLD?

    #LT6502b

  44. I've been trying to get my KeyScan (ATMEGA644P) to output onto the 65c02 databus at the correct time and for the correct duration...
    I don't think it's going to work, sometimes I get no data back, when I tweak the timing I somehow get a 16bit value back (impressive from an 8 bit CPU eh?).

    So, I may have to put a UART into the CPLD, and "WinSim" doesn't seem to simulate properly. So it'll be try and keep trying until it works, or I run out of space.

    Has anyone done a UART in a CPLD?

    #LT6502b

  45. I've been trying to get my KeyScan (ATMEGA644P) to output onto the 65c02 databus at the correct time and for the correct duration...
    I don't think it's going to work, sometimes I get no data back, when I tweak the timing I somehow get a 16bit value back (impressive from an 8 bit CPU eh?).

    So, I may have to put a UART into the CPLD, and "WinSim" doesn't seem to simulate properly. So it'll be try and keep trying until it works, or I run out of space.

    Has anyone done a UART in a CPLD?

    #LT6502b

  46. Well it completed.
    No lines so I think the fix has solved the timing issue.
    32 iterations, 1024x600 Mandelbrot on #LT6502b

  47. Well it completed.
    No lines so I think the fix has solved the timing issue.
    32 iterations, 1024x600 Mandelbrot on #LT6502b

  48. Well it completed.
    No lines so I think the fix has solved the timing issue.
    32 iterations, 1024x600 Mandelbrot on #LT6502b

  49. Well it completed.
    No lines so I think the fix has solved the timing issue.
    32 iterations, 1024x600 Mandelbrot on #LT6502b

  50. Well it completed.
    No lines so I think the fix has solved the timing issue.
    32 iterations, 1024x600 Mandelbrot on #LT6502b