Advedit C64 Editor: Full-Screen Editing on the C64 Ultimate
#AdveditC64 #C64Ultimate #Commodore64 #cc65 #RetroDev #8bit #Homebrew #CProgramming
https://theoasisbbs.com/advedit-c64-editor-full-screen-editing-on-the-c64-ultimate/?feed_id=7341&_unique_id=69552ced10843
#CC65
Day 2 Successful compile, .RAS to .PRG
Got done a “hello.ras” compile to #MEGA65 using #TRSE #CLI. It involved a bit of mucking around but once set up works. Key bits:
* Type Hello.ras (hw.ras) #example for MEGA65 <https://github.com/leuat/TRSE/blob/master/Publish/tutorials/MEGA65/Tutorials/easy/01_hello_world.ras>
* Download, compile #CC65 compiler <https://github.com/cc65/cc65>
* Find document for TRSE CLI usage <https://lemonspawn.com/trse-command-line-interface/>
* Write a #ShellScript for CLI #build
* Compile and target hw.ras to hw.prg
Next test is to pass the hw.prg using the #JTAG link to the #M65 and watch it run. This also means I can stay on the CLI to build something else. 📺😊
Retro Computing Nostalgia meet Open Source Software and Hardware with AgonLight and Neo6502, the incredible evolution of modern Retro computer projects https://olimex.wordpress.com/2025/07/23/retro-computing-nostalgia-meet-open-source-software-and-hardware/ #z80 #w65c02 #retrocomputing #retrogaming #pascal #cpm #forth #basic #cc65
A little while ago I worked on making the Apple II cc65 runtime less dependant on the target. That work is now in cc65's git and it is possible to use 80 columns, lowercase characters and MouseText characters while building for `apple2` in addition to `apple2enh`.
This allows me to ship a single floppy image for most of my projects, with binaries running on anything from the ][+ to the IIgs, and still benefit from the extended features at runtime.
As of today, the #cc65 runtime now contains LZSA (1 and 2) and ZX02 decompressors: https://github.com/cc65/cc65/commit/333ac4b38317d9264f370178b44bc71cc8156272
Visualizing Commander X16 User Port Signals with LEDs
#CommanderX16 #RetroComputing #UserPort #HardwareHacks #LEDprojects #cc65 #ModernRetro #LED #UserPort
https://theoasisbbs.com/visualizing-commander-x16-user-port-signals-with-leds/?feed_id=2853&_unique_id=6800fe2f2cac8
Разработка трёхмерного движка для Dendy/NES. Часть 1
В этой статье мы поговорим о разработке простого трёхмерного движка для консоли Dendy ( NES/Famicom ), который позволит выводить полигональные трёхмерные модели и проводить над ними базовые манипуляции (вращение, перемещение, трансформация, заливка полигонов и т. д.). В первом части мы обсудим реализацию вывода двумерных примитивов и организацию памяти в условиях ограничений NES.
https://habr.com/ru/companies/sberbank/articles/881056/
#c #python #разработка_игр #nes #dendy #gamedev #ретроконсоли #3dграфика #движок_игры #cc65
I always had the idea in mind to one day code something in #C for the #C64. There's #cc65 offering a decent compiler. I always ended up with using #assembler again. That's because on that platform, it is the only way to have "full control": The OS only offers a machine code ABI (jump to routines, pass stuff in registers) and misses lots of things, so you need to program the hardware directly. Of course, I still use an assembler instead of hacking the bytes of the machine code directly.
Any Unix and similar OS comes with a C compiler, and even other systems offer a C API, so for a "modern" environment, that's the natural language to use for that "full control". And remember, C is your "portable assembler". 😏
In a nutshell, if you take "from scratch" literally, it would mean to somehow hack bytes into the machine's memory. That doesn't make much sense. I understand it as "use a simple programming language and avoid these huge frameworks and similar doing deep magical stuff for you".
CC: @modev@snac.bsd.cafe
Any Unix and similar OS comes with a C compiler, and even other systems offer a C API, so for a "modern" environment, that's the natural language to use for that "full control". And remember, C is your "portable assembler". 😏
In a nutshell, if you take "from scratch" literally, it would mean to somehow hack bytes into the machine's memory. That doesn't make much sense. I understand it as "use a simple programming language and avoid these huge frameworks and similar doing deep magical stuff for you".
CC: @modev@snac.bsd.cafe
Forked the repo and commited my changes to get it to build with #cc65 in case anyone else is interested.
https://github.com/FozzTexx/reedsolomon/tree/cc65-compatible
I’m so hooked to this, that I feel I waste my time on project, instead of doing something to earn money. At least I’m learning C as I go along. I wrote the interface part of a simple wifi manager for my serial card for #apple2 in #cc65. It is suppose to talk to zimodem firmware on the esp8266 in a way that seems native to the apple2. #retrocomputing
I managed to rewrite my custom serial card firmware in #cc65 It’s way easier to work with strings in C compared to assembly. I had a minor hiccup with the pointers but I think finally got the grasp of them. Since I dont have any serial buffer but just one byte register, I found that using printf() with screen scroll actually cant catch up the serial speed. Using cputc() is doing well but no screen scroll. I ended up delaying the speed a bit on the esp8266 side and using printf(). #apple2
@jos1264 Or you could just use any text editor you like (#vim works pretty fine with assembly code), one of the many cross-assemblers available (e.g. ca65 from #cc65 comes with an object-code format and a linker for that, which is awseome for organizing larger projects) and control your build with good old #make.
But hey, if using monsters based on #chromium and #javascript (vs-code) and a #java vm (kickassembler) feels "right" for you targeting this tiny old machine writing lean and efficient code ... 🤷♂️😏
@RogerBidon @root42 That makes sense to me. TBH, I didn't even know #GCC *could* target the #mos6502 until reading your toot.
Low-level optimization will always be hard, I mean, it's hard to map C to this architecture at all (e.g. because of the very small and "global" hardware stack and a complete lack of any sp-relative addressing).
I was tempted ever so often to use C for the #C64, but always ended up writing *everything* in assembly (just using #cc65's assembler and linker, having linkable object files is super nice!).
Will take this on my ideas list to try creating a "gcc-mos6502" port for #FreeBSD 😎
@RogerBidon serious question, assuming you have to write mostly "targeted" code anyways (because a #mos6502 just won't reasonably run 98% of today's existing C code), what's the edge of a #GCC targeting this platform over e.g. #cc65?
If there's a real advantage, I might be tempted to bring this to #FreeBSD...
Another learning breakthrough :ablobcatrave: I’ve managed to write a small ca65 assembly program which prints text on the screen. I burnt it onto an EEPROM and started it from the #apple2 slot 5 with ‘pr#5’. It took me some time to wrap my head around how to make the memory map of the ROM but it worked and I’m so happy #retrocomputing #cc65
Just fixed my #cc65 boilerplate for #apple2 Now after compiling, the makefile inserts the new #ProDos image into Virtual][ emulator (MacOS) and “brun”s the project file. This speeds up the dev process quite a lot. #retrocomputing In case anyone needs it: https://github.com/varna9000/cc65-template-project
@governa With the #CC65 compiler (#C only) already along for a long time, did anyone compare the results?
https://cc65.github.io/doc/cc65.html
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst