"And that didn't do anything!" I relate to that hahaha

@burnstick1380

3 жыл бұрын

For me it's more like ohh that broke even more

@ug333

2 жыл бұрын

I love that you leave that stuff in. It's so critical to see and understand it's just part of the process

@thorin1045

2 жыл бұрын

It is the fun of programming, you wrote your code, checked it, and still something is wrong. And you need to find out what, a missed part of syntax, a wrong label or variable name or just your code wrong.

Can we just appreciate that this dude truly made a hello world from true scratch in assembly on an ancient processor and documented it in an easy to follow way for all of us to see and learn with?

@chitlitlah

Жыл бұрын

That's why we're here; we appreciate it. I did do some machine language programming on some of these old processors including the 6502 in one of my college classes. They plugged into these boards that we used to enter opcodes and values into memory and then we could step it forward and examine the values to see what the processor was doing. (I wish I could remember what those boards were called.) Ben definitely takes it another step though.

@ProctorSilex

Жыл бұрын

@@chitlitlah I wish my college had that much. Although we did get some hands on, it was very little and the equipment was not up to the task. Ben's projects are what I had expected computer engineering school to be before facing uncaring reality.

@pareshmhatre4019

Жыл бұрын

No!

@russianvideovlogguy

Жыл бұрын

this is going to be a stupid question, but could you code this in c and then use a compiler that's been specifically designed to output 6502 machine code?

@kaitlyn__L

Жыл бұрын

@@russianvideovlogguy that’s what most people do. And modern compilers are more efficient than human coders 99.9% of the time (not always true even in the 90s). That’s why hand-coding assembly in this day and age is such a madlad endeavour! Fun fact: when assemblers were first invented, the computer scientists who learned to keep track of all their memory and instruction addresses by hand viewed _assembly_ as the easy-mode cheat for modern hacks, much as present-day C aficionados view Python!

Using an 8bit pointer to create an “automatic” circular buffer was brilliant. I kept waiting for a modulus, but no, you one-upped my expectations. Fantastic as always.

@musicalfringe

3 жыл бұрын

Same here! I suppose AND would be the way to go with any power-of-two buffer size if you didn't have the luxury of small pointers on your CPU.

@johnm2012

Жыл бұрын

@@musicalfringe A 128-byte buffer would be almost as easy - the negative flag is set when the pointer reaches 128 so it's easy to detect.

@DzububS

2 ай бұрын

Except that writep = readp when the buffer is empty and when it's full, the way the program is written. Easy fix, just keep track of the buffer length and only write when length is less than 256 and read when it's greater than 0. That is if you want to read then inc and write then inc.

@DzububS

2 ай бұрын

Either way Ben's the man

Note, there should be a separate flag for the right and left shifts, because with one flag I could press LSHFT, RSHFT then release RSHFT and it would count as released even though LSHFT is still pressed (and same vise versa)

@Jason9637

Ай бұрын

Pressing and releasing both shifts at the same time would give you a special shift-lock mode

He threw in the 0x0F bug to appear human, but he's clearly a god 😏. Another amazing video sir!

@eduardog3000

3 жыл бұрын

But for real: it's nice that he keeps in the issues he experiences so we can learn from them and be ready for a bug like that.

@IceMetalPunk

3 жыл бұрын

The final code still has another bug: pressing both Shift keys at the same time breaks it 😂 When the first is released, letters will go back to lower-case even though you're still pressing the second; and when the second is released, because he's using xor ("eor") to clear the flag, it'll turn shift on permanently until you press and release Shift once again. So... definitely a fallible human 😁

@nilswegner2881

3 жыл бұрын

@@IceMetalPunk yeah but who presses both shift keys at the same time? That doesn't make much sense

@mrlitbottoms6968

3 жыл бұрын

@@nilswegner2881 its still a bug that someone could accidentally activate. when your programming u have to not only think of the correct use case but also the incorrect edge case, it is on the edge case that most bugs exist

@IceMetalPunk

3 жыл бұрын

@@nilswegner2881 I occasionally do just as I tap keys randomly as I fidget. But when designing software, you should *never* assume your users "would never" do something -- always code to cover all your bases.

that sped-up typing sound at 6:05 sounds so cool

@proxy1035

3 жыл бұрын

it sounds like a dying floppy drive

@masheroz

3 жыл бұрын

The keyboard sounds triggers the "[Applause]" in the auto captions.

@yousorooo

3 жыл бұрын

Keyboard ASMR

@ridespirals

3 жыл бұрын

@@yousorooo exactly

@SnafuDMZ

3 жыл бұрын

Aphex Twin samples

I'm studying master in computer engineering and these videos from Ben are the best in the field

@wicket4969

3 жыл бұрын

Nice, what’s your thesis on?

@arisweedler4703

3 жыл бұрын

@@wicket4969 I don't know if you need to write a thesis for a masters in CS. I don't think you do

@dr.palsonp.h.d815

3 жыл бұрын

@@arisweedler4703 yes you do

@blablabla7796

3 жыл бұрын

@@dr.palsonp.h.d815 it depends on which country you’re from. There is no universal regulatory body for Computer Science that I’m aware of.

@dr.palsonp.h.d815

3 жыл бұрын

@@blablabla7796 usually all western masters programs require a thesis, the ones that dont are the exception

May I be the first to congratulate you on accidentally reviving the concept of "Shift-Lock". As you're toggling the flag when shift is released but setting it when pressed, pressing both shift keys together and then releasing them will toggle the shift bit back to on. :) [Edit: Typo correction]

@anschelsc

3 жыл бұрын

Yeah, I think to be fully correct you'd have to implement the two shift keys as separate flags.

@lightdark00

3 жыл бұрын

Explain your thought process. humans aren't accurate enough for "same time" conditions, one will always be first or polling would cause one to be first. My thought is you would lose caps holding both, then still have no caps releasing them both. With even boolean operations, it always returns to the default state.

@anschelsc

3 жыл бұрын

Depending how you implement it, either holding both shift keys gives you lowercase, or holding both and then letting go of one gives you lowercase, or as in the existing implementation holding both and letting go of both gives you uppercase. I consider all three of these to be incorrect behavior.

@jgharston

3 жыл бұрын

@@anschelsc Or implement ShiftUp as AND #NOT(SHIFT) instead of EOR #SHIFT.

@anschelsc

3 жыл бұрын

@@jgharston Then when you hold down both shifts, and let one up, you'll be in lowercase even though you're still holding down one of the shift keys.

2090 Building an A.I. that can simulate the human mind from scratch.

@Hiphopasaurus

3 жыл бұрын

On a 6502 of course

@realdragon

3 жыл бұрын

3450: Programming GTA X on 6502

@brammie155

3 жыл бұрын

@@realdragon ez for this god of a man

@yuvalbechar5429

3 жыл бұрын

seems like a content worth to wait for

@masonedwards7920

3 жыл бұрын

That he will offload his consciousness to.

Mercy! I needed to know this back in the late '60s and early '70s. So here we are fifty plus years later as I slip into my second childhood. 😆

After following Ben Eater's Videos for several years now, I still don't understand how anyone can "dislike" his videos... for the content that he provides, it is the best that is currently available on the net anywhere... even better than most college or university content that is publicly and freely available... if I could like more than once, I wouldn't hesitate to do so!

@vaclavtrpisovsky

3 жыл бұрын

Missing the "like" button on a small touchscreen. This just happened to me but I thankfully noticed immediately

@Sparkette

3 жыл бұрын

I wouldn't be surprised if they were all accidental. Like Václav said, or perhaps some little kid randomly clicking around on KZread. Any intentional dislikes are probably just trolls.

@franchufranchu119

3 жыл бұрын

Must be because he's using vim and not emacs

@ecosta

3 жыл бұрын

@@franchufranchu119 Or how he uses VIM. Some VIM users are quite finnicky about using VIM "properly"

@Nick-lx4fo

3 жыл бұрын

@@ecosta Or maybe they just don't understand

I found your 8 bit build videos probably a year ago and was glued to the screen in a way I didn’t expect. The final videos on conditional jumps and control word logic felt like the climax in an action flick. I soon discovered an alternative purpose for the videos: highly effective sleep aid. I’m not insinuating your videos are boring. Far from it. Rather the tone and cadence of your voice and and the quiet sound of assembling tiny components on a breadboard knock me right out. It’s like magic. I love these videos when I want to be awake, and I love them when I want to be asleep. Someday I’ll order a kit and see if my kid’s attention spans are as as solid as mine. Perhaps I could even lull them into a nap.

@kjanovich

3 жыл бұрын

No I feel it dude, total same here. Its a great series to both learn from, and relax to.

@MDarkus3

2 жыл бұрын

Thanks to you Ben will start a ASMR series of video ;)

Typically, an interrupt service routine (ISR) does the minimum possible to deal with the peripheral, and then it returns, and it's up to some other routines to interpret the retrieved data. One thing to remember is that when an interrupt is processed, interrupts are disabled until either they're explicitly enabled or the return from interrupt instruction is executed. Therefore any other interrupts (from other devices) will be blocked, and possibly missed. So the routine to read the keyboard port would just fill the buffer, and any program/subroutine which reads the buffer would do the handling of modifier keys like shift. In this case, it really doesn't matter, because there isn't another device competing for CPU cycles via interrupts. But for more complex systems this sort of thing should be kept in mind.

@dr.palsonp.h.d815

3 жыл бұрын

yea the way he did it was messy

Some day in the future, I will look back at these videos and understand every single line of code.

@RedwoodRhiadra

3 жыл бұрын

If you follow along all the videos from the beginning, it shouldn't be too hard. Almost everything he did here was introduced and explained in a previous video.

Ben posts, I like.

@loneranger4282

3 жыл бұрын

1st comment, nice Also, r u a patreon bec u got access to the video before it was public lmao

@thatMatthew

3 жыл бұрын

I was rewatching his older videos and I was like "hey how have I not seen that one yet" 20 mins ago oh, that's how OH WAIT

@blizzy78

3 жыл бұрын

@@loneranger4282 Yes I am.

@ilyadaemon

3 жыл бұрын

like then watch :)

I love the way the captions hear the keyboard sound as applause. It makes it look like he’s giving an inspiring speech about handling keypresses.

Thank you Ben, now you should use this and the "worst" graphic card, to print some text on the monitor! :)

@tekvax01

3 жыл бұрын

give him time... I'm sure that's next! He's building a word processor from scratch! :P

@JoshHeidenreich

3 жыл бұрын

It'll be self hosting soon

@nikkiofthevalley

2 жыл бұрын

Problem is, he would need some kind of font handler and a graphics driver aswell, which sounds like it would be a pain and a half to program in Assembly.

I’m amazed by how much footage there is on this channel of you removing the eeprom from the programmer and putting it back on the breadboard

@JoshHeidenreich

3 жыл бұрын

Does he reuse the same clip each time...?

@mattsains

3 жыл бұрын

@@JoshHeidenreich I was wondering that but I think it’s different each time. Either that or very well edited

@paulevans9307

3 жыл бұрын

EEPROM installation supercut, anyone?

I literally swear i've learn't more information about lower level computing from this channel than I did across my whole compsci degree. Great video as always ben!

@jgharston

3 жыл бұрын

CompSci != CompEng.

@jordy15322

3 жыл бұрын

@@jgharston Yeah I get that and know the difference... But in my opinion understanding of lower level functionality of a computer helps re-enforce knowledge and understanding within higher level computing. did a little comp enginnering stuff on my degree but it was taught so half assed it was useless. Fun fact: I've regretted since the begining of my second year not choosing a computer engineering degree but was too late by that point.

@jgharston

3 жыл бұрын

@@jordy15322 Yeah, me too exactly. I was three years into my CompSci degree and still thinking "when are we going to get to some, y'know *actual* computing?" It was years after that I realised I should have looked for something with "engineering" in the course title. It was only in my very final semester that I put together hardware interfaces for controlling a set of LEDs and a printer, and wrote a PDP11 assembler - both of which I just did a brain-dump of stuff I'd done more than six years previously.

@chiblast100x

3 жыл бұрын

@@jordy15322 I can't speak to now, but depending where one went to school a couple decades back it was practically assured one would get a CE minor pursuing a CS major (and vice versa) at the BS level, and putting in two extra years one could graduate with a BS in each CS, CE and Math

@dr.palsonp.h.d815

3 жыл бұрын

@@jordy15322 Computer Science is arguable much harder than Computer Eng, stick to it, its worth much more than being able to write assembly

i like how this started as building a System and now it's turning into a system programming set of videos for the most part.

Your mention of a keyboard buffer explained to me why frozen Windows programs sometimes spring back into action processing all the keystrokes you entered while it was frozen.

Good stuff , but that interrupt routine is doing quite a bit. Usually you want to keep interrupts doing a minimal amount of work so the execution gets back to the main loop. Probably for better performance just capture scan codes in the buffer, and then dispatch a key translation when the main loop reads the next key value. For more advanced projects, you can then have context based key mappings.

@BertGrink

3 жыл бұрын

Good point.

@arisweedler4703

3 жыл бұрын

You're not complaining, you are pointing out an interesting fact. Thank you for sharing! :) One thing that I was thinking of: When he was implementing the shifted keymap, instead of a branch insn, he could have just set the shift flag to be 0x100 and added it to the keymap's address. In both cases this will do a load from 0xfd00 if the shift flag is 0 and load from 0xff00 if the shift flag is 1, so... yeah... this doesn't make it *better*, per se, but the code would be cuter. I would like to say, though: indirection at the cost of complexity for efficiency ((when you don't need the added efficiency to function)) is bad. I think Ben rightfully and consistently chooses simplicity over performance, and I praise him for it.

@ZeroPlayerGame

3 жыл бұрын

@@arisweedler4703 it's arguably better-ish because there's less jumping around... but tracking separate shift states for left and right shift would become impossible with that.

@willofirony

3 жыл бұрын

Back in the day, when I was just starting assembly language, I would get anxious, as the number of lines of code kept increasing, that the code I was writing would take an age to execute. After assembling, it usually executed in the blink of an eye. One reason is that much of the code is skipped. When I write "usually", I mean when there are no loops. Loops in an interrupt routine can be a real problem.

@BertGrink

3 жыл бұрын

@@willofirony Loops in general can be problematic; I remember that when I started looking into some PHP coding, I had a section that would take a very long time to show results, and upon closer inspection I was able to track it down to a couple of nested loops. The solution was to reverse the order of nesting, i.e. the inner loop became the outer one and vice versa. This blew my mind, so to speak.

The sei and cli aren’t actually necessary. kb_ptr is only modified outside of the interrupt handler so it doesn’t need to be in critical section and kb_wptr is read atomically (since it’s a single byte) so the read doesn’t need a critical section either.

I recently hooked a 6551 up to my bread boarded 6502, been having a blast with the kit and plan to eventually build my own sound card. Thanks for the videos, been using a circular buffer like this for processing serial input and other interrupt-y situations. A nice generally useful technique for working with input, thanks for showcasing it.

@Wraithan

3 жыл бұрын

@Stephen Anthony I happen to have a SY6551, but the WDC65C51 has well known work arounds, so it isn't a deal breaker just a little less performance at the same clock rate.

I love how he kinda skipped right over needing to replace the quotations with apostrophe's on line 50 of the shifted key matrix. Took me a minute to figure out what was going on. I should have realized something was different right away when my line turned 3 different colors. Absolutely great video! I actually like that it doesn't just work right away every time. I feel like I learn more when I have to troubleshoot crazy problems.

I don't understand how anyone, let alone 16 people could dislike a Ben Eater video. This is better than anything I learned in university when getting my CpE degree. Thank you Ben for all that you do.

It's more than 30 years ago, I've learned writing code for the 6502. But it's still amazing and I love your series about this small computer.

@topilinkala1594

11 ай бұрын

Let's see, C64 came out in 80's, so to me it's about 40 years.

Having actually (re-)written a keyboard driver / scancode translator I appreciate this. In case anybody is wondering why a different map for upper case, well just look at an actual ASCII table and compare that to the scancode table. He'd need at least another ten minutes to explain the mapping shift, so fodder for later.

"Writing code with a keyboard to make a keyboard work, now Thats thight!" :)

@sly1024

3 жыл бұрын

You know that many code compilers are written in their own language? A C++ compiler is written in C++ (just the previous version), obviously the first one had to be written in another language (assembly) though..

@ScienceDiscoverer

3 жыл бұрын

@@sly1024 And think about how first assembly was written? In binary!

@josugambee3701

3 жыл бұрын

@@ScienceDiscoverer Actually, the first assembler was present in the very first core memory module installed in an electronic computer. Nobody knows how it got there.

ahh man you open my mind to hole new level. programming for 10 years and I just realize how small I know things. good work

There's something magical about seeing the letters appear on the tiny screen as you type them!

I love these videos. Working at this level of simplicity in 8bits is extremely satisfying because everything just makes sense on the surface, without need for too many abstractions.

People who are disliking Ben Eater's awesome videos are school professors

@MarkBurrell1964

2 жыл бұрын

I sincerely hope you are wrong there, but who knows. For what it's worth I taught degree / masters level computer architecture for years and even wrote a book on computer architecture.... And Ben Eater is teaching me stuff! Thanks Ben, I'm having a brilliant time playing with hardware again and coding 6502 for the first time in 30 years.

Just been following along with your 6502 Computer videos. I can tell that lots of effort goes into these videos, thanks for the great content, and keep up the good work!

@MikeSims70

3 жыл бұрын

I wholeheartedly concur with this concise and accurate statement, ☺

May 2031: today in the breadboard computer, ray tracing video adapter with dual 8K displays

Plot twist: he’s already got vim running on his breadboard.

Always enjoy watching your videos! Brings back fond memories of my college days! :)

the 65c02 has phx, phy, plx, and ply opcodes btw :) (4:32)

I was just recommended this channel, and how happy I am! Watching you gradually add function to your interface was extremely satisfying and calming. Thanks for the great content!

Awesome as always. You editing skills are at another level too. I can understand amount of effort put into make this video. Much appreciated Ben.

Quite possibly the most involved "Hello, World" application I have ever seen in my 27 years of programming.

These videos have been instrumental in helping me understand and appreciate how the very basics of computers work. I can't wait to see more.

thank you for sharing this amazing project and series

This series is just fantastic. I know just some basic x86 asm but it's close enough I can go along here. Thank you!

Wonderful! This takes me back to 1983 when I bought an Apple II and a copy of the ORCA/M assembler. Thanks Ben.

Always great, Ben! Can't wait to pick up a kit of my own!

Very grateful for all your work Mr. Eater. QMK Finally just made sense in just 20 minutes. Thanks! I'm looking forward to starting kits 1-4!! Shout out from TX

Super helpful animations within the vid, loved it!

Watching this series has taught me how to write and understand basic assembly language, which is so cool! Thank you Ben!

OMG, this popped up as possible interest to me and I watched this to the end as it brought back memories to my life in the mid 70s to 80s. I was watching the assembler instructions and surprising to me, I was recognizing all the 6502 instruction set you typed in. Thanks for the memories ...

I did stuff like this (circular buffers) with a 6800 back in 1979. Thanks for inspiring me to get back into hardware again. I bought your 6502 kits, but it wasn't enough. I upgraded to a 65C816 running at 8Mhz. It now has 1Mb ram and 96K of eeprom and an NHD-0440WH 40 x 4 display. I finally figured out how to get a PCF8584 working so I have I2C to a DS3231 for date/time and more I2C peripherals in the pipeline. I can't seem to get my AM9511A-4 (FPU) working and I'm about to give up and look into alternatives. Thanks again.

Thanks, Ben. Great videos!

Sir, thanks for all these videos. you are a real hero for me. thanks a lot

wonderful as always!

Awesome Ben! I am curious how you will expand this project from here.

@mceajc

3 жыл бұрын

I hope the graphics interface will make another appearance, and replace the LCD screen - then there will be the opportunity for a mouse-controlled cursor. I'm surprised that a dot-matrix printer has not (yet) made an appearance as an essential output peripheral!

@lightdark00

3 жыл бұрын

A mouse to move the curser on the screen!

@josephc8482

3 жыл бұрын

I'm wondering if he will attempt to make a simple game like hangman on the lcd. Just to show everything coming together and interacting. That said, in his patreon, he did hint that he wants to do another video comparing the PS/2 interface with USB, but the 6502 is too slow for USB, so it will be a stand-alone demo rather than a 6502 breadboard project.

@genjii931

3 жыл бұрын

Serial communications, storage, and graphics ability would be the most likely candidates, I would think. Mouse, not so much. Mice didn't come into common usage until the 16-bit GUI days, and this computer is pretty far from that at this point.

This video tied it all nicely. As I'm tying this comment out, I'm imagining the little transistors in all of the circuits flipping on and off like crazy. Your videos really make it easier to understand than when I was in school. My teachers were great, but maybe my Interest then wasn't as great as it is now. So, thank you!

You have that ability to make things appears so simple. It's great !

i love your content, it is so fun to watch

Thanks, Ben, for this fantastic material. Vim has a Ctrl+N shortcut to autocomplete a word. Extremely useful.

Ben, thanks for the upload!

Lovely. Thanks! It brings back memories of learning some very simple assembly on my C64 when I was in my teens (a time almost beyond living memory now!). While I'd never want to go back to passing carries around for multi-byte arithmetic, I do miss most other aspects of the simplicity of 6502 assembly!

Holy Moly! This is really cool! Even though I speak Z80 Assembler natively, I'm slowly beginning to understand 6502 coding. Big thanks to Ben. 😁

@MrTridac

3 жыл бұрын

I'm switching back and forth between Z80 and 6502, and it always feels like switching between C++ and BASIC. Luckily I love both. (except BASIC, I don't love that)

If there were massive destruction of this earth, this is the only guy who can make computers from scratch! Following you since last 6 years. Huge #respect

This is an amazing training session for 6502 assembly! I didn't think I could follow this, but I got it all the way. Thank you! I'm tempted to type up the code so I can learn from the mimicry. This would be like typing the Basic programs from a 1980s magazine.

@markanderson2904

5 ай бұрын

Or it would be like Mozart copying Bach in order to study/learn.

I can't explain why this is so captivating

This series really reinforces to me how creative and inventive early computer people had to be to make all this work. You take things like the keyboard just plug and play and off you go but never really think about how much is happening behind the scenes just to type some characters. PS. Thank you for making these videos!!

6502 assembler is SO much more relaxing when someone else is writing it... Excellent series. Thank you.

Just amazing to see how to make something like this work.

Another great video!

This is so useful! I am about to build a PS2 interface to my Atari ST, with a ATmega CPU, but still.. All the workings and concepts are here. Thanks!

@squirlmy

3 жыл бұрын

Are you aware of Soarer's Converter? or all the TMK-based projects? github.com/tmk/tmk_keyboard/wiki/TMK-Based-Projects ? I wasn't sure at first if your the Atari ST has the ATmega, because your converter could also use an ATmega. It would be funny if your keyboard is more powerful than the CPU!

This is so cool!! Ben has reached the "Hello, world!" stage now :D

4:06 The sped-up typing is insanely satisfying

Very nice video. Regarding the shift key handling, I do think that handling two keys with only one flag might cause a little glitch: if you press both shift keys, and then release only one of them, software will behave as if you did not hold the latter; it will print non-capitalised letters. It's allways fun trying to find any "errors" in the work presented; however one can only be grateful for this opportunity, thanks to your great work!

@davidfrischknecht8261

3 жыл бұрын

I was thinking the same thing about the handling.

Hi Ben, love your videos! In the handling of the release of the shift keys, you used "eor", which would flip the bit. This means that if the following key sequence happened, the shift flag would stay enabled with no shift key being pressed: - Press left shift (sets the shift flag) - Press right shift (does nothing, since the flag is already set) - Release one shift (clears the shift flag) - Release the other shift (sets the shift flag, because of the XOR) Maybe the only way to solve this case is to handle each shift key in its own flag?

@JoeldaSilvaVicenteFilho

3 жыл бұрын

or instead of flipping the flag, set it to the actual value

@aritzh

3 жыл бұрын

@@JoeldaSilvaVicenteFilho however this would mean that after releasing the first shift key, but keeping the other pressed, the letters would be written in lowercase

@mrseanbob

3 жыл бұрын

I came looking for this same comment. I think you’d need a separate flag for each shift key.

@JoeldaSilvaVicenteFilho

3 жыл бұрын

@@aritzh true

@mrmimeisfunny

3 жыл бұрын

Or yknow, do it properly lda kb_flags and #~SHIFT ;vasm allows that. I checked. sta kb_flags I cringed when he did "eor" because that is asking for bugs. Though I didn't spot that specific one.

You remind me so much of John Carmack! Your voice, inflections, and brilliance. ❤

15 Java programmers have had their keyboard buffers overflown.

the most amazing part about this is how you typed the keymap scan code table from scratch so quickly. I thought it was fast enough as random jibberish. until it actually worked! - and then my mind was blown.

@RedwoodRhiadra

3 жыл бұрын

He's not really doing it from scratch - he's got a copy of what he needs to type offscreen and is reading that while he types. Plus the video is sped up there, which hides any delays as he looks back and forth between the screen and his offscreen copy.

@normanstevens4924

Жыл бұрын

@@RedwoodRhiadra Isn't it just traversing the keyboard with a particular zig zag pattern, i.e. start with a key on the bottom row, then the key slightly to the left on the next row, followed by the key on the third row just to the right of that one and the key on the fourth row to the left of that. Repeat for each column of keys.

@RedwoodRhiadra

Жыл бұрын

@@normanstevens4924 It's been a while since I looked at the video, but I don't think it's that simple.

I had been waiting with bated breath for this video :)

This is awesome! Thank you!

Super video! I applauded for RUB 100.00 👏👏

Great as always

Video stupendo! Ho applaudito per 2,00 € 👏

This is a great example of just how efficient assembly language can be. Each feature is implemented in just a handful of instructions. Each instruction is just a few bytes. I didn’t count, but the key map probably takes up more memory than all the rest of the code.

@squirlmy

3 жыл бұрын

maybe it's because of growing up with 6502 computers and peeks and pokes, but I'm not so impressed with assembly efficiency. That's literally what it's made to be for, a step above hexadecimal(which is almost always only used for reverse-engineering, not coding!) I guess if your first programming language was something like Python, or even Perl, you'd be impressed with assembler.

@TheDanEfranChannel

3 жыл бұрын

@@squirlmy Oh, I grew up with 6502 programming too, mostly BASIC and assembly. Certainly comparing to an interpreted language accentuates this sense that assembly is efficient; a modern compiled language is more on par with assembly in practice. I just like how what we call "lines of code" and perhaps envision as sophisticated control structures with a lot of machinery behind them...can often be expressed in machine language as just a handful of bytes that perform very simple state changes in the processor. It's neat.

Let me like before watching. I have the guarantee that I will never be disappointed by Ben.

Hi Ben, you added all this new hardware to detect and create a clean IRQ pulse when you didn't have too.... you already had the hardware in place with the 6522. All you needed to do was use the Timer 2 in "Pulse Counting mode", and voila! Just set it up to count down 11 pulses applied to PB6 and it automatically fires the IRQ output when it reached zero. Then read in the data from your shift register into PortB, and you're good. You'll just need to add more code to check the IFR to see what generated the interupt. Would be a good way to show how to handle multiple interupts anyway. Keep up the good work man!

Hi! First of all, "Great Videos", its always nice to remember the basics and the importance of some "minor" details. As for this specific video, I think your ISR is being overloaded. I would suggest a minimal ISR just to stuff the bytes in the FIFO buffer, and move all the processing/decoding to the main program body. The usual rule of thumb is to keep an ISR as short and fast as possible.

Thanks Ben!!

I am gonna binge watch all his videos today.

This is more assembly programming than computer architecture, but still fun to watch.

I wish I knew the key map by heart and could type it that fast! So educational, as usual!

Ben is the person that convinced me to learn 6502 assembly -- I love it! (unlike amd64 assembly. it's awful and ridiculously too complex for my brain. congrats to those who wrote the first compilers for this architecture)

Excellent brother 👍

excellent! Thank you!

Awesome!! I think you’ll need one of those 4 line LCD displays, cuz a “Vim on 6502” is on the way I can sense that :D

You are gonna make me buy parts and start making hobby electronics. Appreciated.

I appreciate that he’s using the Model M to type the code to run the Model M 😆 I can’t wait to go back to the office where I have desk space to use mine again.

19:35 "You can come up with your own designs..." ... and end up with a commodore 64

I live for these videos

This is pretty much exactly the design I came up with for a keyboard driver for a DOS Lightcycles game I wrote in C in the '90s.

Great channel