Furkan#8728
kodbilen
Recent community posts
I recommend you to watch ben eater's tutorials. https://www.youtube.com/playlist?list=PLowKtXNTBypGqImE405J2565dvjafglHU
I was very busy today I couldn't write a respond I'm sorry about that.
Since I'm a highschool graduate who prepares for local univercity exam I haven't taken any lessons other than my own reading and research. With my knowlage I designed a circuit and a language for it in previus days.
I have read everyhing you said many times yesterday. Pretty much everything you said was completely new to me. Now I need to rework my circuit and language design.
Neither the circuit nor lanugage is mature yet but I want to share some papers with you to give you some idea how it looks like.
Your info really helped me improve ALU. Thank you very much for your effort. Being in a cominity really helps people to improve in a topic so just like you said, I look forward to start a discord comminity too.
Sometimes modules that work in design phase might be dead after you create them. You need to do whole design phase all over again. Here is an example of that happening twice in a row.You can see the module named "INCREMENT" became dead and I created the same module as "INC" at the very begining of the video. then I design and test "PCOUNTER" module. Unfortunitly that died after creating as well.
I just finished ALU and RAM. I'm now very close to finally be able to run this cpu. When I finish I want to share the files here. I have spent about 12 hours now on this simulator and I haven't noticed any bug. Just be careful when you delete modules from %appdata% since if you delete a module that you forgot you used in another module previusly working parts that contained removed module will stop working with no notification. Biggest drawback is the fact that we have limited area to work on but I feel like I got used to it after the first 5-6 hour. My previus comment was about clocks but you can make clocks with adjustable frequancy and pulses with different durations. adjusting them is not that ideal but I don't think anymore that is a problem since I never used a clock or pulse so far. Obviusly I need at least one clock but I belive a manuel input would be actually better then a clock module. That way I can use a autoclicker and be able to preciesly change frequancy.
This was exactly what I intended to develop myself for my project. I found this completely randomly while surfing through the internet and this maked me so happy. Thank you very much.
Edit: This lacks capasitors and resistors. If you don't want to implement simple physics even a hard-coded clock module(just like "and" and "not" modules) would work. or maybe an option for imputs to work like a clock with adjustable frequancy. Any of these would greatly improve this app.
Edit Edit: I managed to make a clock with xor gates but frequancy is depent on the update rate of simulation so you cant change it.