Lallafa's XUM1541 Prototype

Now with the beta of XUM1541 online, I have another present for you: The OpenCBM on Mac page on my site. This page describes how to compile and set up the OpenCBM software yourself and how to get your device running on your Mac. Have fun!

So follow me on macvice @ twitter to get the latest updates on freshly build MacVICE versions…

dtv2ser 0.4 now supports all new features of dtvtrans 1.0 including init after reset, BASIC loading, saving and RUN. Furthermore, full flash support was added!

If you are impatient then just head over to the dtv2ser homepage and download your copy.

What’s new in this version? Let me explain it with a short walk through:

Basics

After flashing the new 0.4 firmware, you launch the dtv2sertrans client as usual. On Macs you can see some kind of auto-detection of the serial port:

> dtv2sertrans
dtv2sertrans version 0.4, dtv2ser device version 0.4
dtvtrans server NOT responding!!

Ah… no dtvtrans server is running on my DTV. So let’s reset the DTV (and enter dtvtrans via dtvboot):

> dtv2sertrans reset
dtv2sertrans version 0.4, dtv2ser device version 0.4
  resetting dtv... enter dtvtrans
  initializing full BASIC

That’s new: BASIC and KERNAL is fully initialized after a reset, so BASIC commands like load, save, run will work. Querying dtv2sertrans again:

> dtv2sertrans
dtv2sertrans version 0.4, dtv2ser device version 0.4
dtvtrans server version 1.0 (DTVBOOT 1.2 via joy2 in ROM)

Now the server is detected and reports the version, the port and if it resides in RAM or ROM.
You can query more info with:

> dtv2sertrans server info
  dtvtrans revision: 1.0
    implementation:  DTVBOOT 1.2
    port:            joy2
    mode:            ROM
    range:           0x1f8000-0x1fb3db

dtvtrans 1.0 Features

Let’s check out the new dtvtrans 1.0 features that support BASIC commands and simplify loading, running programs:

> dtv2sertrans reset + load mygame.prg + run

Reset + init BASIC, load a program via dtv2ser and run it… That’s easy!

> dtv2sertrans save myprog.prg

This call saves the current program like the BASIC SAVE does only via dtv2ser…

Whats quite handy is a fill commando to simple write a value (e.g. 0) to a range of memory:

> dtv2sertrans fill 0x18000-0x20000 0

Flash Commands

And now flashing! But first a Warning: Flashing operation can destroy your DTV. So you have to be sure what you are doing. In this guide I’ll warn you, if something dangerous will happen. So you can decide if you dare it

First let’s see if your dtv2ser device can handle sys calls:

> dtv2sertrans diag sys
dtv2sertrans version 0.4, dtv2ser device version 0.4
  loading servlet '/Users/chris/Projects/svn/dtv2ser/servlet/diag_srv.prg'
  testing 25 sys calls with wait and return value fetch
  * 0/25: testing sys call with 84 frames duration
  duration: 00:01.823
...
  * 24/25: testing sys call with 51 frames duration
  duration: 00:01.219
  * 25/25: all calls passed OK!

Ok, sys call test passed without errors… So the flash commands that are called via sys should work.
Now let’s ensure that the dtvtrans server program is runnning from RAM and not from ROM!

> dtv2sertrans server ram
dtv2sertrans version 0.4, dtv2ser device version 0.4
  resetting...
  is alive?
  initializing BASIC
  query dtvtrans server
  dtvtrans running in ROM. loading RAM version
  loading prg file '/Users/chris/Projects/svn/dtv2ser/contrib/dtvtrans_joy2.prg': 2548/0x0009f4 bytes, start: 0x0801
  sending program to DTV
    speed:  client=16.48 server=16.59 (kbyte/s)
    time:   00:00.191 for 2548/0x0009f4 bytes
  run program
  query dtvtrans server
  dtvtrans is now in RAM. Good!
    implementation: DTVTRANS 1.0

Fine, server now running from RAM… We are ready for flashing!
Let’s check the type of the flash ROM found in the DTV:

> dtv2sertrans flash id
dtv2sertrans version 0.4, dtv2ser device version 0.4
  flash type: SST39VF1681

Now let’s have a look a the flash usage:

> dtv2sertrans flash map
dtv2sertrans version 0.4, dtv2ser device version 0.4
  generating flash map on DTV
  duration: 00:04.731
          flash ROM map ('.'=empty '*'=filled)
          0xxx 1xxx 2xxx 3xxx 4xxx 5xxx 6xxx 7xxx 8xxx 9xxx Axxx Bxxx Cxxx Dxxx Exxx Fxxx
  000000: .... **** .... .... .... .... .... .... .... **** **** **** .... **** **** ****
  010000: **** ***. .... .... **** **** **** **** **** **** **** **** **** **** **** ****
  020000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  030000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  040000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  050000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  060000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  070000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  080000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  090000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  0a0000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  0b0000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  0c0000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  0d0000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  0e0000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  0f0000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  100000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  110000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  120000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  130000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  140000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  150000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  160000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  170000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  180000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  190000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  1a0000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  1b0000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  1c0000: **** **** **** **** **** **** **** **** **** **** **** **** **** **.. .... ....
  1d0000: .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ....
  1e0000: .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ....
  1f0000: .... .... .... .... .... .... .... .... **** **** **** **** **** **** **** ****

The first step in flashing is to store the current contents of the flash ROM in a file:

> dtv2sertrans flash dump orig_rom.bin
dtv2sertrans version 0.4, dtv2ser device version 0.4
  dumping flash ROM to file 'orig_rom.bin'
    speed:  client=17.95 server=17.96 (kbyte/s)
    time:   01:54.116 for 2097152/0x200000 bytes
  saving raw file 'orig_rom.bin': 2097152/0x200000 bytes

Now, create or alter the ROM file (e.g. use tools like DTVFSEdit).
If the new ROM is ready, you can flash it back to your DTV with (first in dummy mode w/o flashing):

> dtv2sertrans flash sync new_rom.bin
dtv2sertrans version 0.4, dtv2ser device version 0.4
  loading raw file 'new_rom.bin': 2097152/0x200000 bytes
  syncing flash ROM
          flash ROM map ('*'=flash '#'=erase+flash)
          0xxx 1xxx 2xxx 3xxx 4xxx 5xxx 6xxx 7xxx 8xxx 9xxx Axxx Bxxx Cxxx Dxxx Exxx Fxxx
  010000: #... ..#. .... .... .... .... .... .... .... .... .... .... .... .... .... ....
  020000: .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ....
...

If you add the -f switch then a real flash operation is performed. This will alter your DTV! So make sure the image is correct:

> dtv2sertrans flash sync -f new_rom.img
...

Ok, that’s it! This was a short walk through for all the new dtv2ser 0.4 features. But there are many more things to discover. Just run dtv2sertrans -h to see more options…

Have Fun,
-chris

Puh, finally my 1541U cartridge has a decent case!
I created one myself starting with a generic case at the price of about one EUR…

Have a look at my Lallafa’s 1541U DIY Cartridge Case Page for more details!

I just built my sd2iec device board from Shadowolf. Its really small and compact so I thought why not integrate it into my modded DTV with the original joystick case. I don’t wanted to sacrificy the battery case so I knew there is not much place left…

With a lot of cramming and fiddling around I finally managed to insert the sd2iec inside my DTV Mod. Phew! Now the case is filled up to the limit – but its cool to have a sd2iec right inside the joystick;)

Have a look here at my gallery for more pictures!

I have lying around hundreds of D64 disk images on my hard disk and thought it would be really nice to have a quick look at the directories…

So I wrote D64QLPlugin that allows to display the contents of a D64/D71/D81 disk image file in a small retro-style directory view…

Check it out at the D64QLPlugin Homepage!

Grab your copy here: dtv2ser Homepage

The new version introduces a fully automatic bootstrap command that brings an unmodified DTV (with only a DB9 joystick connector attached) into dtvtrans mode in a few minutes without manual intervention. A normal mode types in TLR’s boot.txt basic booter on the virtual keyboard and fetches mlboot.prg and dtvtrans.prg afterwards. A new improved fast bootstrap method does some pre POKEs to speed up typing and boots in half the time. Additionally, a screen code compiler allows to type in mlboot.prg directly to screen space and run it there without the need to execute boot.txt first.

Additionally, the JoyStream is introduced to describe and execute sequences of joystick input via a special string language syntax. AutoType allows to type in arbitrary files or strings via the virtual keyboard of DTV’s basic prompt. A Screen Code compiler encodes an assembler program and directly types in the corresponding character codes on the screen to run it there.

Have fun!

Sounds awesome? It is! Mine arrived during this week and today I had the time to check it out. I just finished drilling out the holes for all connectors and now the board fits nicely in its case:

After using the RR+RRnet and MMC64 with the two cases interconnected and the network cable pointing upwards its a real relief to have everything in a single case.

The BIOS of the MMCReplay is really nice and full featured. You can flash ROM images directly from files stored on a SD card. You have 7 slots available that can hold different ROM images.

RRNet was tested with DiskImages64 on my Mac, of course. All works as expected
and since the MMCReplay is fully compatible to the RR+RRNet and MMC64 it is no surprise.

Now I have something new to play with… And I really feel like updating DI64 with some new features…

After thinkcommodore.com finally shut down its business, it was a sad time for Mac + Commodore fans without having a forum to discuss. Now the wait is over: a new site hit the ground: doremac.com. The site has a forum with strong focus on Commodore computing done by Mac users. Starting from data transfer connection issues to CBM emulators on the Mac you can find everything there. Head over and check it out!

Grasstust, the site maintainer, was kind enough to add a MacVICE Forum Thread. So all MacVICE related stuff including bug fixes and user support can be discussed there.

What’s this all about?

Bootstrapping means to initially load some software or tools on a system.

Unfortunately, a fresh and unmodified DTV joystick device has no easy way of adding software. Only by wiggling the joystick left and right during boot you can enter the basic command prompt. There the C64 blue screen is available and allows to enter basic code. There is no keyboard available so a virtual keyboard is used by pressing the joystick and moving around until the desired key is highlighted.

The idea of DTV bootstrapping is now to enter a short boot basic program that then receives more tools transmitted via the joystick port. For this to work, you will need a mini-joy-mod. This mod of the DTV only adds a DB9 connector for the joystick port 2 and requires to solder 6 lines…
With this mod you can bootstrap with a dtv2ser device and run dtvtrans on the device! With dtvtrans you can upload any tool to the memory of the DTV and run it. With TLR’s flash tool you can then alter the flash file system and add new programs or games…

Automatic in the title now means to take the burden of manual typing in the initial basic boot code. This is done by simulating the input via the virtual keyboard with the dtv2ser device connected to the new DB9 joystick connector. This technique is called AutoType and was invented by Spaceman Spiff and is already implemented in dtvtrans+.

Here is the first version that uses dtv2ser 0.3 and a DTV with the umodified virtual keyboard and its slow timing to enter the boot code (My first capture attempt with a web cam positioned directly in front of the monitor :

Boot Time is 480 seconds

This one is a more advanced version that uses some pre-pokes (thanks to TLR!) to speed up the virtual keyboard first. Entering the boot code is then much faster (Second capture with frame grabber):

FAST Boot time now is 270 seconds…

There is still room for improvement there, as the basic code is not in minimal syntax yet.

Now I am busy finishing dtv2ser 0.3 and preparing it for release. Stay tuned and be ready for your own DTV bootstrapping experience… and maybe some new and more optimized fast boot code