More Coding. I am building my 6502 as we speak. No silly 8 I/O lcd I am rather keen on the oled i2c. Would be nice to understand how userland works. It looks like you are writing to eeprom and not using the serial ram upload?
While developing things it has to be a combination of both - when routines new routines are made they have to end up in ROM eventually :) The next few videos should help you along :)
@@AndersNielsenAA I greatly look forward to that. I have been reading the RIOT datasheet, and the oled one too, but the oled one is talking about the control chip not the oled its self. Doesn't seem like the RIOT is used that much so there is hope I can translate the code to the VIA. I really like the idea of i2c/SPI/serial over 8bit LCD and 5 buttons. The Serial and i2c really open up possibles. I am thinking of 2 buttons Serial and i2c, and maybe SPI for file storage. I have a SD module from my Arduino that is happy to run on 5volts, and it has level shift built in for the data/control lines.
There's no delay for i2c and the ports work the same on the VIA, so you should be able to copy the i2c routines right over - as long as you rename the port and put SCL on bit 0 at least.
@@AndersNielsenAA Yes i2c can be as slow as you want, and maybe SPI as well, but serial that seems to take a bit more care with timing. I think with serial you also looked at trying 4800 bps, but it seems like 9600 bps worked out. :) As for RAM I have 16k so limitless memory. Ty for the tips, I have house cleaning and getting my sewing machine working today, or maybe tomorrow.
With the FTDI to the 65uino - yes. 65uino to RPi - no sadly. I looked it up and it doesn’t seem the Pi supports it. I think the closest solution is improving the buffer to be FIFO, slowing things down and doing work while waiting for the timer
Try sending a xoff (ctl-s) char back to the rpi. This was an alternate inband type of flow control often implemented in terminal software. Send a xon (ctl-q) char to start it sending again.@@AndersNielsenAA
Actually I might not have dug deep enough - maybe it is possible to enable RTS/CTS without too much trickery - maybe an overlay file.. But XOFF/XON would almost be too easy - I’ll have to try that.
Leave a comment here and come join the clubhouse on Discord :)
discord.gg/kmhbxAjQc3
More Coding. I am building my 6502 as we speak. No silly 8 I/O lcd I am rather keen on the oled i2c. Would be nice to understand how userland works. It looks like you are writing to eeprom and not using the serial ram upload?
While developing things it has to be a combination of both - when routines new routines are made they have to end up in ROM eventually :)
The next few videos should help you along :)
@@AndersNielsenAA I greatly look forward to that. I have been reading the RIOT datasheet, and the oled one too, but the oled one is talking about the control chip not the oled its self. Doesn't seem like the RIOT is used that much so there is hope I can translate the code to the VIA. I really like the idea of i2c/SPI/serial over 8bit LCD and 5 buttons. The Serial and i2c really open up possibles. I am thinking of 2 buttons Serial and i2c, and maybe SPI for file storage. I have a SD module from my Arduino that is happy to run on 5volts, and it has level shift built in for the data/control lines.
There's no delay for i2c and the ports work the same on the VIA, so you should be able to copy the i2c routines right over - as long as you rename the port and put SCL on bit 0 at least.
@@AndersNielsenAA Yes i2c can be as slow as you want, and maybe SPI as well, but serial that seems to take a bit more care with timing. I think with serial you also looked at trying 4800 bps, but it seems like 9600 bps worked out. :) As for RAM I have 16k so limitless memory. Ty for the tips, I have house cleaning and getting my sewing machine working today, or maybe tomorrow.
Could you implement RTS/CTS to prevent the buffer overflows?
With the FTDI to the 65uino - yes. 65uino to RPi - no sadly. I looked it up and it doesn’t seem the Pi supports it.
I think the closest solution is improving the buffer to be FIFO, slowing things down and doing work while waiting for the timer
Try sending a xoff (ctl-s) char back to the rpi. This was an alternate inband type of flow control often implemented in terminal software. Send a xon (ctl-q) char to start it sending again.@@AndersNielsenAA
Actually I might not have dug deep enough - maybe it is possible to enable RTS/CTS without too much trickery - maybe an overlay file..
But XOFF/XON would almost be too easy - I’ll have to try that.
@@AndersNielsenAA I'm very interested in what you find out!