element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Ben Heck Featured Content
  • Challenges & Projects
  • element14 presents
  • element14's The Ben Heck Show
  • Ben Heck Featured Content
  • More
  • Cancel
Ben Heck Featured Content
Documents Atari Dragster World Record - Part 1: Building the Hardware -- Episode 317
  • Blog
  • Forum
  • Documents
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Ben Heck Featured Content to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Engagement
  • Author Author: tariq.ahmad
  • Date Created: 23 Jul 2017 12:57 AM Date Created
  • Last Updated Last Updated: 17 Nov 2017 8:24 AM
  • Views 1868 views
  • Likes 4 likes
  • Comments 11 comments
Related
Recommended

Atari Dragster World Record - Part 1: Building the Hardware -- Episode 317

image

element14's The Ben Heck Show

Join the Ben Heck team every week for amazing hacks! Watch them build and mod community-inspired projects using electronics!

Back to The Ben Heck Show homepage image

The Learning Circuit
sudo Sergeant
See All Episodes

 

 

You don't have permission to edit metadata of this video.
Edit media
x
image
Upload Preview
image

The oldest video game record left standing is for the Atari 2600 game Dragster, the first third party game ever and first title released by Activision. A modern speedster, whose done tests with emulation and spreadsheets, claims the recorded score of 5.51 seconds is not possible, the best possible score is 5.57 seconds. Ben does not care about records, he’s using it an excuse to build a RAM analyzer to make decisions on how best to play the game.

 

 

While Ben does not care about records, he’s interested in using this as an excuse to build a RAM analyzer for the Atari 2600, analyzing the BUS with newer hardware.  This external device will see when the CPU writes to the RAM and make a copy of the data to put in a memory array that can be read by a microcontroller. If they can get the RAM copier working, they can later have a microcontroller take a look at the RAM and make decisions on how best to play the game.

Ben rigs up some test equipment using some microchip PIC tail cards and some TI B0108 voltage receivers. This has an 8-bit BUS on either side to allow you to put two different voltages on it, in this case 5 volts and 3.3 volts, and does automatic conversions for you.  He tests to make sure that the BUS transceiver properly converts 5 volts into 3.3 volts. He plugs the card into a PIC Development board. This allows him to do 8-bit read/write operations on the PIC32. To scan the Atari’s memory he’ll send bytes to it. The 8-bit data bus will come in as soon as he adds the address BUS and act as a clone of the RAM so that it can monitor what the Atari is thinking.  By having a copy of the RAM, the MCU can make decisions on how best to play the game.

Ben does a voltage test with an IC tester clip. Ben has a wired up a PIC tail connector for the PIC32 MZ. He’s got some logic that does an address decode. Basically, it only sends a pulse when they are addressing the RAM.  He runs the data and the address line through these 3.3 volt to 5 volt transceivers so they can knock down the voltage to 3.3 volts for the PIC32 so the PIC32 can read it without damaging itself.

Because they are using a 6502 CPU they’ll have to make adjustments to compensate for INCrement and DECrement.  The data is not due to the possibility of having a double write immediately in the RAM by doing an INCrement or DECrement command.  Ben takes a look at a 6502 CPU timing sheet and analyzes the INCrement and DECrement instructions that caused a double write to the RAM.  He then adds circuitry to accommodate for that and counts a certain number of periods before setting a flag to tell him that the address or data is valid. This creates a rising edge triggering an interrupt on the PIC32 allowing it to load the valid data. Using external circuitry allows them to analyze the waveforms coming off to the CPU and figure out the best time to send the data to the PIC.

 

Disclaimer

  • atari 2600
  • speed run
  • hack
  • microchip
  • pic microcontroller
  • atari dragster speed run
  • microchip development expansion board
  • microcontroller
  • soldering
  • atari
  • heck
  • ben
  • memory analysis
  • tbhs_ep
  • atari dragster
  • Share
  • History
  • More
  • Cancel
  • Sign in to reply

Top Comments

  • gam3t3ch
    gam3t3ch over 7 years ago +2
    Great episode!
  • DAB
    DAB over 7 years ago +2
    Great episode, You brought back many memories when I used to have to trace timing sequences for memory read and write events and then trace them on a logic analyzer. Great fun. DAB
  • DAB
    DAB over 7 years ago in reply to Sean_Miller +1
    Hi Sean, In a computer, the address bits were all run as a series of physical circuit board traces and referred to as an address bus. In the 6502 days, there were 16 address pins which ran to the memory…
  • Sean_Miller
    Sean_Miller over 7 years ago

    Thanks all.  So, basically an 8 bit computer meant there are 8 pins on the chip that vary high & low on the individual pins to represent what I always understood to be a hexadecimal value.  The clock would allow a way to snapshot the state of those 8 pins by having some other pins flag what to do with the state of those 8 pins.  Woh.  (Keanu Reeves)

     

    I'll binge watch the Crash Course.  6.8Million subscribers can't be wrong.

     

    With Windows masking all of this with .Net, having this discussion is finally addressing the things that baffled me in my 80's childhood.  It's almost therapeutic.image

     

    -Sean

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • beacon_dave
    beacon_dave over 7 years ago in reply to DAB

    Carrie Anne Philbin's weekly 'Crash Course Computer Science' series is quite good for this:

    https://www.youtube.com/playlist?list=PL8dPuuaLjXtNlUrzyH5r6jN9ulIgZBpdo

    Short 'coffee break' type episodes starting right from the basics and presented in a light easy-going manner for everyone to understand.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • DAB
    DAB over 7 years ago in reply to Sean_Miller

    Hi Sean,

     

    In a computer, the address bits were all run as a series of physical circuit board traces and referred to as an address bus.  In the 6502 days, there were 16 address pins which ran to the memory chips, so you had 16 lines.  The data bits were also run to each memory device and referred to as a data bus, again for the 6502, there 8 bits, so eight lines.

     

    The CPU would write the address onto the address bus and the chip select circuitry would then enable the specific memory chip, which would make its data available to the data bus.  If the CPU was writing to the memory, then it would put data onto the data bus and activate the write enable pin on the memory.  At that point the memory chip would transfer the data from the CPU into the physical memory chip.

     

    If the CPU was reading data, then it would activate the read enable pin and then transfer the data from the memory chip to the CPU.

     

    All of these read and write operations were carefully synchronized to the CPU clock so that the proper timing was maintained for all devices.  In the old days, this could be challenging.

     

    As Dave Ingles pointed out, you should do some web searching on how a computer works to better understand the complexities involved.

     

    DAB

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • beacon_dave
    beacon_dave over 7 years ago in reply to Sean_Miller

    Combination of multiple pins which forms the address bus

     

    Try this explanation:

    https://www.bbc.co.uk/education/guides/zsnbr82/revision/12

     

    or this one:

    https://www.youtube.com/watch?v=fpnE6UAfbtU

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • Sean_Miller
    Sean_Miller over 7 years ago

    I'm slow on this one.  It's not clicking for me.  Last year, I soldered up a working 6502 computer based on Grant Searle's website.  It was quite the ratnest.  It actually worked when I was done, but it still didn't sink in what is truly happening in slow motion when you "read the address".

     

    When you say address "lines" - what physically is the "line".  Does this mean the pulsing of a pin or combination of multiple pins state (high or low) in concert with a pin designated as a clock?

     

     

    Thanks,

     

    Sean

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • DAB
    DAB over 7 years ago in reply to Sean_Miller

    Hi Sean,

     

    Memory devices use address and data connections to access information stored within them.

     

    The address lines identify the specific location of the information, be it a bit, byte, word or other length of data.

     

    The data lines access the information at the specified address for either read or write.

     

    Some memory systems use parity, read and write control, error correction, encryption or circular redundancy calculations (CRC) to ensure data integrity.

     

    I hope that helps.

     

    DAB

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • makerkaren
    makerkaren over 7 years ago in reply to Sean_Miller

    Yes. Reading the 8 bits of data. (So says Ben.)

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • ninjatrent
    ninjatrent over 7 years ago

    I miss the 2600. So thankful for emulators.

     

    Bet I could beat the perfect time  

     

    Dragster was one of my favorites.

     

    Still remember that sound the engine would make when blown. Like the crack of a bullwhip.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • Sean_Miller
    Sean_Miller over 7 years ago

    What exactly are you doing when you say "read the address".  Are you recording the 8 (D0-D7) pins' state of the 6502?

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • DAB
    DAB over 7 years ago

    Great episode,

     

    You brought back many memories when I used to have to trace timing sequences for memory read and write events and then trace them on a logic analyzer.

     

    Great fun.

     

    DAB

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • More
    • Cancel
>
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube