takao21203
- Joined Apr 28, 2012
- 3,702
Ah yes I see a bit.
I2C is nothing new, has been around for a long while and is pretty much a standard.
Most serial chips either use synchronous serial (SPI) or I2C.
When you program serial I/O in most cases you deal with TFTs or serial memory and sensors.
Better learn I2C, serial memory and graphics TFT.
You can use the GAL programmer to write serial FLASH if it is not too dated.
I am not talking about the latest technology that would be leadless ICs, flex PCBs, software CPU cores on a FPGA and things like that.
But about to mothball linear regulators, 9V batteries, large LED display boards, and assembler. This stuff belongs to the early 1970s.
Innovation can be made by using older technology in a new way, but especially assembler is more a blocking to that than anything else.
Hordes of young people used assembler in the late 1980s and early 1990s. It all ended at some point of time and led to nowhere.
But logically, you should be able to use a serial EEPROM at first, before you try to program a software USART.
A software USART with no defined purpose has no right for existance.
My opinion is create solutions, don't deal with absurd toy problems. Learn to create a solution, then maybe do some toy problem circuits.
Nothing stopping you from:
-Learn I2C
-And do a software synchronous USART
-And do a software asynchronous USART as well if you feel need be and haveing fun with it.
But in that order as above.
Because I2C is a defined standard, and synchronous USART is easier.
I2C is nothing new, has been around for a long while and is pretty much a standard.
Most serial chips either use synchronous serial (SPI) or I2C.
When you program serial I/O in most cases you deal with TFTs or serial memory and sensors.
Better learn I2C, serial memory and graphics TFT.
You can use the GAL programmer to write serial FLASH if it is not too dated.
I am not talking about the latest technology that would be leadless ICs, flex PCBs, software CPU cores on a FPGA and things like that.
But about to mothball linear regulators, 9V batteries, large LED display boards, and assembler. This stuff belongs to the early 1970s.
Innovation can be made by using older technology in a new way, but especially assembler is more a blocking to that than anything else.
Hordes of young people used assembler in the late 1980s and early 1990s. It all ended at some point of time and led to nowhere.
But logically, you should be able to use a serial EEPROM at first, before you try to program a software USART.
A software USART with no defined purpose has no right for existance.
My opinion is create solutions, don't deal with absurd toy problems. Learn to create a solution, then maybe do some toy problem circuits.
Nothing stopping you from:
-Learn I2C
-And do a software synchronous USART
-And do a software asynchronous USART as well if you feel need be and haveing fun with it.
But in that order as above.
Because I2C is a defined standard, and synchronous USART is easier.