It's crazy the things we appreciate now days that just weren't thought of yet. It's so cool go see new generations going back to the old tech and breathing new life in to it. Great work bud!
Thank you very much! We take almost everything we have in our smartphones or computer for granted now, it's great to back to old tech to actually understand how it was, how it changed and what were the choices made on the path of evolution.
@@Zeal8bit That would be impressive. The question would be... can it avoid date limitations, or would it end up with its own Y2K bug? Nonetheless, this is an important development, as this would make it quite a bit more advanced than a huge number of 8-bit Computers from the Seventies and Eighties. It also makes me wonder how much further this project can be pushed, and where you will go next. Thanks for this update!
@@horseradishpower9947 Officially, the limitation for the chip is set to year 2100 for the leap year calculation, that gives us 78 years still from now. The fact is the Year register (register 0x6) is a single byte, so it presents tens and units of year (the value is thus comprised between 0x00 and 0x99). However, 56 general purpose RAM bytes are available from 0x08 to 0x3F, which means that we can store the upper digits of the year their, or even the whole year there. Agreed, this will let us have timestamped files, or even games depending on the real time like the Gameboy had. I could push this project even further but I have to set limits, else I won't finish. In fact, I still have plenty of things to implement. The final board will have an extension port, giving access to the bus, and a user port which gives access to 8 GPIOs, UART and I2C bus. This should be enough for extensions😄
@@Zeal8bit Honestly, the fact you have done this much is brilliant. RTC is a pain in my backside for my Pi. I have a module, but it is all about understanding the instructions to put it in, and then getting it all to work... so moving on to other elements makes perfect sense. Declare a success, move on to other things, and then eventually move round to improving it. Again, good luck with your project!
Fascinating how people always start with CP/M 2.2, and then they add RAM banking and an RTC first. But there is also CP/M 3, which already includes all those features and more.
From what I see, there is much more documentation and demos for CP/M 2.2 It has been ported to a lot of targets and homebrew computers while CP/M 3 is more rare. Moreover, most software you can find online are compatible with 2.2
@@Zeal8bit I know all too well how much the cp/m 3 documentation sucks. I am currently working on a port, and it's not easy. But I had it booting already, and it is totally worth it. Now I am in the process of refining the system, but I am still stuck at the bootloader. That is maybe the least documented part of it.
![How 8-bit graphics work on homebrew retro computer [Part 1]](http://i.ytimg.com/vi/Yqj1tTqxfC4/mqdefault.jpg)
![How 8-bit graphics work on homebrew retro computer [Part 1]](/img/tr.png)
very interesting to see RTC on a retro computer, like a retro-modernist stuff
Thank you!
It's crazy the things we appreciate now days that just weren't thought of yet. It's so cool go see new generations going back to the old tech and breathing new life in to it. Great work bud!
Thank you very much!
We take almost everything we have in our smartphones or computer for granted now, it's great to back to old tech to actually understand how it was, how it changed and what were the choices made on the path of evolution.
Nice. I used a bq4845 on my z80. It is addressed like a RAM chip so can use I/O instructions to work with it. It has a few other cool features too.
That's a good choice! Parallel bus makes it simpler and interface with a Z80
I wish such chip would be available in DIP or PLCC format😄
@@Zeal8bit Mine is a DIP, I did this about 7 years ago.
So... the next revision board could see a Real Time Clock added into it? That would be pretty cool.
You guessed right 😄
I have already added this RTC to the latest prototype, I will show it in an upcoming video
@@Zeal8bit That would be impressive. The question would be... can it avoid date limitations, or would it end up with its own Y2K bug? Nonetheless, this is an important development, as this would make it quite a bit more advanced than a huge number of 8-bit Computers from the Seventies and Eighties. It also makes me wonder how much further this project can be pushed, and where you will go next.
Thanks for this update!
@@horseradishpower9947 Officially, the limitation for the chip is set to year 2100 for the leap year calculation, that gives us 78 years still from now. The fact is the Year register (register 0x6) is a single byte, so it presents tens and units of year (the value is thus comprised between 0x00 and 0x99). However, 56 general purpose RAM bytes are available from 0x08 to 0x3F, which means that we can store the upper digits of the year their, or even the whole year there.
Agreed, this will let us have timestamped files, or even games depending on the real time like the Gameboy had. I could push this project even further but I have to set limits, else I won't finish. In fact, I still have plenty of things to implement. The final board will have an extension port, giving access to the bus, and a user port which gives access to 8 GPIOs, UART and I2C bus. This should be enough for extensions😄
@@Zeal8bit Honestly, the fact you have done this much is brilliant. RTC is a pain in my backside for my Pi. I have a module, but it is all about understanding the instructions to put it in, and then getting it all to work... so moving on to other elements makes perfect sense. Declare a success, move on to other things, and then eventually move round to improving it.
Again, good luck with your project!
@@horseradishpower9947 Can't you find a suitable driver online for your RTC on Raspberry?
Thank you for your support!
Fascinating how people always start with CP/M 2.2, and then they add RAM banking and an RTC first.
But there is also CP/M 3, which already includes all those features and more.
From what I see, there is much more documentation and demos for CP/M 2.2
It has been ported to a lot of targets and homebrew computers while CP/M 3 is more rare. Moreover, most software you can find online are compatible with 2.2
@@Zeal8bit I know all too well how much the cp/m 3 documentation sucks.
I am currently working on a port, and it's not easy. But I had it booting already, and it is totally worth it.
Now I am in the process of refining the system, but I am still stuck at the bootloader. That is maybe the least documented part of it.
Nice Work!
Thank you very much!