[DPC+ ARM Development]

Here is an index to all the DPC+ARM blog posts by Darrell:

• DPC+ARM - Part 1, Virtual Machine and Linux
• DPC+ARM - Part 2, Guest Additions
• DPC+ARM - Part 3, VirtualBox update, Ubuntu update, disable Screen Lock
• DPC+ARM - Part 4, Cloning
• DPC+ARM - Part 5, C Compiler
• DPC+ARM - Part 6, DPC+ Cartridge Layout
• DPC+ARM - Part 7, 6507/ARM Exchange of Information
• DPC+ARM - Part 8, Multiple Functions
• DPC+ARM - Part 9, Functional Menu
• DPC+ARM - Part 10, Score & Timer display
• DPC+ARM - Part 11, Beginnings of the Arena Kernel
• DPC+ARM - Part 12, Gamepad Support

 

Note that Parts 1 - 5 are about setting up a VM with the ARM compiler, which is probably outdated now. Maybe someone can create a Docker image containing a ready-to-go DCP+ARM development environment?

 

And some other interesting related posts:

• The C RAM Review
• It's full of stars!
• Slick Kernel

 

[Step 4 - 2 Line Kernel]

Thanks for your explanation of DoDraw; now I finally get how this works.

 

One question though: when preparing the HumanPtr pointer and subtracting the y-position of the player, I think it is possible this ends up pointing to an address in the page prior to the page where the gfx is located. Which - depending on the y-position of the player - can sometimes result in an extra cycle when doing lda (HumarPtr),y.

 

So to be cycle-exact every time, you probably need to place the player gfx somewhere at the end of a page, right?