This is the classic Marilyn Monroe resized to 128x128 pixels and saved as a .bmp file. it is then converted to Intel Hex and uploaded to CRC65 which format it to display on the OLED grey level display. 16 grey levels can produce fairly decent pictures.
Bill

This is short 20 seconds video clip of animated GIF running on CRC65.
https://youtu.be/mDH89I5S3LY

I started out with a random animated GIF from the Web, resize it to 128x128, extracted into individual files and stored them as collection of 4-bit .bmp files. Each .bmp file contains 8K of graphic data. The BMP animation program in CRC65 receives each file, reformat, displays, and stores it in memory up to six 8K files. It then display these files continuously in a loop. The frame rate is around 6 frames/sec.

The display loop is limited by the size of CRC65 RAM memory; a better program is storing the data in the CF for playback.
Bill

Since everyone is doing 65816 I might as well join the party and show rev2 of CRC65 which is dual W65C02/W65C816 design. Selection of 6502 or 65816 is via few jumper changes and a different CPLD firmware. The 128K (CY7C109) RAM provides 58K of RAM when configured to W65C02 or 116K of RAM while configured to W65C816. The nominal CPU clock for both 6502 and 65816 is 14.7MHz. Pictures show CRC65 with W65C02 and with W65C816. Documentation is work-in-progress at here:
https://www.retrobrewcomputers.org/doku ... rc65r2home
Bill

This is 25 second of BadApple!! on CRC65's I2C interface driving a 128x64 OLED. The original full length video is 155 seconds animated GIF at resolution of 360x270 playing.at 20 frames/sec. The original video is down sampled to 85x64 GIF then splited into 3100 frames of images and converted into format suitable for displaying on 128x64 OLED display. The resulting data file is 3.1meg and stored as a contiguous binary file on CRC65's CF disk. A BadApple player written in 6502 assembly retrieves data from CF disk and writes it to the 128x64 OLED display via I2C. It can write a frame in 31mS so 19mS software delay is inserted to produce 20 frames/sec video.
Bill

Porting DOS/65 to CRC65 is high on the list of my winter projects. I have made some progress and post it here, but to stay on topic I want to post further progress here.

I designed the DOS/65 disk format to be compatible with my CP/M disk format on Z80 so I can exchange files and debug problems. That particular disk format has 1 track (128KB) set aside for system files. So that is where I stored DOS/65 system files (CCM,PEM,SIM) along with CRC65 monitor. The auto-start code located in CF's master boot record is modified to copy 27 sectors of CF data on the system track to RAM from $b200 to $e7ff and then jump to start DOS/65, this way DOS/65 will boot directly after a power cycle. I still can access CRC65's hardware monitor by execute a "go $b400" in DOS/65 prompt. Since CCM and PEM are stored in system track of the CF, DOS/65's warm boot routine can simply copy CCM and PEM from CF's system track to memory.

I want to assemble DOS/65 programs natively on CRC65 but it is a chicken-egg situation where I need 6502 executable assembler installed first. Executable ASM.COM is not available since all the files on DOS/65 ver2 distribution are in assembly source text. So I assembled ASM212.ASM using CA65 assembler then transfer the executable over to DOS/65 and save as ASM.COM. It seems to assemble other source files correctly but it only generates KIM-1 compatible binary. The provided KIM-to-COM conversion program (MKCOM) does not seem to work at the moment. This is where I am stuck right now.

The attached screen capture shows CRC65 auto boot into DOS/65 after reset. Drive D are DOS/65 ver 2 distribution files and drive A are files assembled used ASM.COM. I'm making progress.
Bill

Hi Bill,

Congrats on getting DOS/65 running! Great progress and very quick

I have makecom running. I ended up using WDC Tools and making some basic changes to the source. I use a TEA of $0800 however. In any case, I've attached my files here.



Let me know if this works for you.

Also, I managed to get the assembler working, basic compiler, basic runtime, alloc, Xmodem, compare, etc. working as well.

_________________
Regards, KM
https://github.com/floobydust

Thanks for the makecom file. I think I made mistakes last night getting assembled mkcom.hex transferred to CRC65 and save as DOS/65 executable. Once I have the assembler and mkcom working on CRC65, I am able to assemble and run the remaining utility files (except xmodem) natively. xmodem interfaces directly with the specific serial device, so I need to work out the interface to CRC65's serial I/O which is rather unusual, to say the least.
Bill

DOS/65 is now running on 29.5MHz CRC65. It uses exactly the same files as 14.7MHz CRC65, except the serial port is running at 230400 baud. Other than checking overclocked CRC65 has no unexpected software issues, the real motivation was to run Dan Werner's screen editor, sedit, which uses serial port to update the screen that can be somewhat slow even at 115200. sedit does work better with 230400 baud, but has the same bugs as 115200 baud. I did encountered a strangeness at 29.5MHz; that XMODEM receives file perfectly at 230400 baud at 12KByte/s, but with 14.7MHz and 115200 baud XMODEM is struggling with numerous retries.

Attached is CF image of DOS/65 rev0.2. Unzip and copy to a new CF disk (32MB or bigger) using disk imaging tool such as Win32DiskImager. It should autoboot into DOS65 and you should see the same files as the screen capture below. Works are in progress for the 3 programs below:
DBASIC.COM is EhBASIC ported to DOS65 but LOAD and SAVE do not work
SEDIT.COM is Dan Werner's screen editor
XMODEM.COM is flaky at 14.7MHz as noted above.
Bill

Hi Bill
That's great I'll give it a workout and report anything I encounter.
Larry

Larry,
I'm very interested in your feedback.

Another strangeness with XMODEM: I can transfer 481K file to DOS/65 OK, but when I try to transfer 1meg file, it stuck at 524288 bytes which is exactly 1/2 meg. When I use the file status program (flst215s.bas) to read the directory info, I see the directory has 32 Extends and 4096 Records. Either DOS/65 has a 32 extends limit or XMODEM can only transfer 512KB of data.
Bill

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!

BDD,
A S-record or Intel hex loader is pretty standard feature in a hardware monitor. CRC65's monitor has an Intel hex loader which can receive ASCII data at 115200 (or 230400 in case of 29.5MHz CRC65) as fast as my workstation can send it without handshake--it's nothing special, pretty much every monitor can do that. Sending Intel hex file serially is how DOS/65 binary is loaded into a new CF initially and how XMODEM is loaded and saved as the very first executable in the new DOS/65 environment in order to bring in rest of files. Like you've said, it is fast and error free over a few feet of wires.

In my Z80 CP/M world, using XMODEM to transfer mega-byte size file and verify it is a part of the test suite, so I have no doubt CP/M and XMODEM can handle mega-byte size file. The overall XMODEM transfer rate is not just moving bytes across wire, but also how fast data can be stored to disk. The XMODEM file transfer rate for 22MHz Z80 is around 9KB/s at 115200. Clock for clock, Z80 is half the performance of 6502, so 29.5MHz 6502 should run circles around 22MHz Z80. This "strangeness" of XMODEM as implemented for DOS/65 on a 29.5MHz 65C02 is an indication of inefficiency and possible bugs in DOS/65 XMODEM program and/or DOS/65 file handling. It is my hope that 6502.org community can help me understand why this particular DOS/65 XMODEM is not performing up to par.

BTW, you are right about kps is the correct unit of measurement. There is no physical modem present in the XMODEM data path.

Bill

Well, a couple things:

1- The Xmodem utility that is packaged as part of DOS/65 is very inefficient, i.e., very very slow. It's the code itself, not the connection speed. It also uses the older single byte checksum. I have my own Xmodem CRC-16 code that I use with my C02Monitor and it's very quick, runs at full speed and the CPU has enough time to generate the CRC-16 checksum for each packet on the fly (no lookup table). I've considered writing a Xmodem utility for DOS/65 but have yet to really think about it, much less get started.

2- It would appear that DOS/65 has a limit of 512KB for a single file... I found the same thing, albeit with the same Xmodem utility. I'll probably write a small utility to create a disk file and just throw 128-byte records into it until it forces an error. I also want to try creating a larger disk than the 8MB, which I just stuck with when Rich sent me his ROM version.

Just a sideline on Xmodem... yea, it's old, not very efficient for transfers... BUT... so many existing and even newer terminal programs still support it. For myself, this is reason enough to have the implementation inside my Monitor code. I don't need a second serial port and it works flawlessly via the console port in both directions. I also added Motorola S19 support for downloads... as I have WDC Tools outputting S19 records, the download function automagically detects and processes the S19 records with or without a user entered address offset.

Once I have two serial ports working (I sorta do now, but the second port has no wiring to the chip), I'll likely look at doing the same thing the BDD is doing for transfers, but that's a back-burner for now.

_________________
Regards, KM
https://github.com/floobydust

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!

Interested to see your quad serial code for 65816. CRC65 can be reconfigured for 65816 with 2 banks of RAM and I have a quad serial board based on OX16C954 that's compatible with CRC65's bus, so CRC65816 with video/keyboard and quad serial board should make a nice standalone computers.