I'm actually more excited to see a new Ben Eater video on youtube than anything else.
His stuff is just fantastic. Even though it's lower level than I've ever worked, it's extremely entertaining and educational.
His 6502 series is just great, but I want to highlight another couple of videos he did:
"Let's build a circuit that displays an image on a VGA monitor! In this video, I talk about how VGA signals work and build a circuit that provides the correct timing of sync signals so that a monitor recognizes the signal."
His video series was very enlightening. Seeing absolute lowest level how that stuff is done is a wonderful insight into why stuff is the way it is today.
Skimming through this, this is the first piece of code that my eyes drilled into more deeply:
LCD__clear_video_ram:
pha ; preserve A via stack
tya ; same for Y
pha
ldy #$20 ; set index to 32
.loop:
lda #$20 ; set character to 'space'
sta VIDEO_RAM,Y ; clean video ram
dey ; decrease index
bne .loop ; are we done? no, repea
sta VIDEO_RAM ; yes, write zero'th location manually
pla ; restore Y
tay
pla ; restore A
rts
Surely we don't need to keep loading the space character into A on every iteration?
Since Y starts at a hard-coded value that is (well) below $80, this could use "bpl .loop" and drop the "sta VIDEO_RAM" special case.
You are more than right. This is just my first assembly project in 20 years, put together from scratch in a couple of days. Therefor I am more than greatful for every constructive hint, that helps me improve. Thanks!
Semi-related, I've been enjoying Robert Baruch's videos[1] on creating a FPGA implementation of the 6800, using nMigen and formal verification. First videos are almost like live coding, then he skips to a more compact format.
As a regular programmer, it's quite interesting to get into how the bits actually end up getting the work done.
Watching Ben Eater's videos renewed my interest in making some simple computers out of old hardware, mainly because the older hardware is simple enough that you can work with it on a breadboard.
The interest eventually morphed into doing something with all of the old parts I've hoarded. Going through the bins of parts, I've found things like 8051 microcontrollers (P80C550) and UARTs (AM85C30) and some old RTC units (MC146818). I ended up picking up a few 68010's (among other things) off of eBay with the hope of building a breadboard Linux computer, as slow as that may be. I believe the 68010 may be the only CPU in a DIP package still supported in some capacity by Linux (as long as you provide an MMU).
Hopefully this will actually get me back into writing/making videos about my projects.
I love, love, love Ben's videos, and this is an awesome project.
But to be as painfully pedantic as possible: can we please use the word 'monitor', here? Calling it a 'microkernel' really gives one the wrong initial impression.
Are there any good resources for learning electronics for someone with a strong programming background and understand digital logic? Ben Eater videos assume knowledge of electronics and would like to know more
I found “Digital Computer Electronics” by Malvino and Brown really helpful. It starts from scratch. Was also a recommendation from Ben Eater, but you will only find used copies, since the book is not in print no more.
Can't go wrong with the art of electronics. Not quite a classical textbook but also not a cookbook - takes you from basic theory to analogue to digital to computers etc.
There's not much to it at a basic level - theory wise, you need Ohm's law, Kirchhoff's Voltage/Current Laws, a few theorems (Then you add knowledge of active components, obviously)
I just read your source code a bit, and there are a lot of things wrong.
First, you should ALWAYS clear the carry when using ADC or set the carry when using SBC
For example:
.increase:
adc #1
sta POSITION_MENU
I have no idea if you increment or add two, since the carry is not cleared.
clc
lda CURRENT_RAM_ADDRESS_L
adc #$01
sta CURRENT_RAM_ADDRESS_L
lda CURRENT_RAM_ADDRESS_H
adc #$00
sta CURRENT_RAM_ADDRESS_H
this is done by the usual INC CURRENT_RAM_ADDRESS_L BNE *+2 INC CURRENT_RAM_ADDRESS_H
There's a kinder way to share this. Ben's teaching a number of things here (basic electronics, computer architecture, assembly..) in an incredibly inviting and rewarding way. I'm confident he's reaching people at varying skill levels. Let's keep that energy going.
[+] [-] Diederich|6 years ago|reply
His stuff is just fantastic. Even though it's lower level than I've ever worked, it's extremely entertaining and educational.
His 6502 series is just great, but I want to highlight another couple of videos he did:
"Let's build a circuit that displays an image on a VGA monitor! In this video, I talk about how VGA signals work and build a circuit that provides the correct timing of sync signals so that a monitor recognizes the signal."
https://www.youtube.com/watch?v=l7rce6IQDWs
[+] [-] ravedave5|6 years ago|reply
[+] [-] aidos|6 years ago|reply
[+] [-] kazinator|6 years ago|reply
Since Y starts at a hard-coded value that is (well) below $80, this could use "bpl .loop" and drop the "sta VIDEO_RAM" special case.
In .select_option, I'd looking into doing a jump table. Ideas here: https://wiki.nesdev.com/w/index.php/Jump_table
[+] [-] jroesner|6 years ago|reply
[+] [-] that_jojo|6 years ago|reply
[+] [-] magicalhippo|6 years ago|reply
As a regular programmer, it's quite interesting to get into how the bits actually end up getting the work done.
[1]: https://www.youtube.com/watch?v=85ZCTuekjGA&list=PLEeZWGE3Pw...
[+] [-] Teknoman117|6 years ago|reply
The interest eventually morphed into doing something with all of the old parts I've hoarded. Going through the bins of parts, I've found things like 8051 microcontrollers (P80C550) and UARTs (AM85C30) and some old RTC units (MC146818). I ended up picking up a few 68010's (among other things) off of eBay with the hope of building a breadboard Linux computer, as slow as that may be. I believe the 68010 may be the only CPU in a DIP package still supported in some capacity by Linux (as long as you provide an MMU).
Hopefully this will actually get me back into writing/making videos about my projects.
[+] [-] that_jojo|6 years ago|reply
But to be as painfully pedantic as possible: can we please use the word 'monitor', here? Calling it a 'microkernel' really gives one the wrong initial impression.
Still, very neat. Now write a BASIC!
[+] [-] fernly|6 years ago|reply
No doubt an educational project. However, all the versions of Microsoft 6502 BASIC were collected and annotated by a Michael Steil in 2008.
Docs: https://www.pagetable.com/?p=46
Source: https://github.com/mist64/msbasic
[+] [-] kbrackbill|6 years ago|reply
[+] [-] nategri|6 years ago|reply
[+] [-] danaur|6 years ago|reply
[+] [-] jroesner|6 years ago|reply
[+] [-] mhh__|6 years ago|reply
There's not much to it at a basic level - theory wise, you need Ohm's law, Kirchhoff's Voltage/Current Laws, a few theorems (Then you add knowledge of active components, obviously)
N.B. Understanding complex numbers is a big help.
[+] [-] miohtama|6 years ago|reply
https://www.atarimagazines.com/compute/issue57/turbotape.htm...
Also let's not forget Bill Gates's 17 bytes loader
https://hackaday.com/2017/03/24/doing-it-with-fewer-bytes-th...
[+] [-] localhost|6 years ago|reply
"Load, Save, Verify, Execute 8 K in 38 seconds versus PETs 2 Minute 45 seconds, plus more!"
There was a newer version that I had which was called the ROM Rabbit vs. this version that you had to load and save each time.
[1] http://archive.6502.org/publications/pet_paper/pet_paper_v3_...
[+] [-] kevstev|6 years ago|reply
[+] [-] edoceo|6 years ago|reply
[0] https://futurama.fandom.com/wiki/Bender_Bending_Rodríguez
[+] [-] unknown|6 years ago|reply
[deleted]
[+] [-] jcmeyrignac|6 years ago|reply
For example: .increase: adc #1 sta POSITION_MENU
I have no idea if you increment or add two, since the carry is not cleared.
this is done by the usual INC CURRENT_RAM_ADDRESS_L BNE *+2 INC CURRENT_RAM_ADDRESS_H cpy #0 is useless.lda POSITION_CURSOR cmp #0 cmp #0 is useless
jsr / rts can be replaced by jmp
clear_ram is super slow
[+] [-] transitorykris|6 years ago|reply
[+] [-] atum47|6 years ago|reply