You can always order new IEEE to IEEE from china (â,¬12,87, no delivery costs): click

You can take the sources to my XS-1541 where code for fast serial (burst mode) is included. It is code for the same controller as SD2IEC (MMC2IEC) and not far away from the controller in the µIEC. So it should be very easy to add burstmode into SD2IEC.

The problem is, most of the SD2IEC devices doesn't support SRQ line in hardware. Has this µIEC hardware support for SRQ?

I'm wondering about this.

1571 burst mode is planned. But in current source files is nothing about. I will ask Nate about this.

I'm sure you have seen a parallel 1571. My parallel 1571 is very very fast. Also my parallel 1541, especially in MNIB mode.

The new ZoomFloppy is the successor of XUM-1541 and all X-cables (X-1541, XA-1541, XM-1541, XAP-1541, XU-1541, XS-1541). With ZoomFloppy you can connect all your Commodore drives to your PC using USB connection.


ZoomFloppy can be ordered from Jim Brain in his shop: klick


ZoomFloppy supports of course OpenCBM software. But new is, it also supports nibblecopy (MNIB) to create better disk images (exact images). For this a parallel cable (Speed-DOS) is nessecary, same type used by XAP-1541 cable.

It will also support old CBM drives with IEEE-488 bus in future.

Quote from: marquisor on July 07, 2010, 03:46 AM
Or does it just work with a hardware mod, as C128DCR already got the right KERNAL?! Even resp. esp. for C64 mode...

First I was thinking it works without a hardware mod only by replacing C64 kernel.

But now I got another C128-D from a friend and my modified kernel doesn't work for him (only slow speed).

So it seems to be sure, an additional hardware mod must be done like on a normal C64. C128 in C64 mode seems to have problems to use burst hardware.

Quote from: marquisor on July 07, 2010, 03:46 AM
Next possible configuration comes in my mind is that the C64 mode has its own KERNAL and the C128 mode its own KERNAL, so TWO ROM chips sit on the C128DCR mainboard?

Yes of course! C128 has 2 kernels, one for C128 mode and one for C64 mode.

Quote from: marquisor on July 07, 2010, 03:46 AM
PS: Is there a software solution for getting burst transfer speeds in C64 mode? For doublesided disks I use "U0>M1", but no burst speedup then...

With this special kernel +  hardware mod (wire to SRQ) you don't need this command. Burstmode automatically is used if a burst able drive is connected. It works same as in C128 mode.

I'm searching for documentation to a special hardware, the fastest floppy speeder ever build for a 1541 drive: TurboTrans+ (successor of  Turbo Access).


Has anyone done something with the hardware of this speeder? Or has anyone made a analysis of the firmware? Or could anybody sell me one or borrow one?


I have build this hardware into one of my 1541 drive using a FE3 (1541 with 512KB RAM), but my hardware doesn't have same banking system cause I don't know how does it work:

• How does the banking work?
  
• How is the memory model exactly?
  
• Is there something special on this hardware?
  
• The parallel cable, how does it work from sight of the firmware (IO address, IO description)?
  

If someone could borrow me such a TurboTrans board, I would need it some weeks and I will pay for it.

If someone would sell me one, please send me an offer.

Congratulation! 


It is a wonderful device. I have two, a 8296 and a 8296-D.

It is not so rare to get here, but most of the 8296 I have seen are damaged. And most of this only have a PLA problem (UE5 and/or UE6). Good to know this PLA is simply to replace now!

I have found an article about burst mode for C64. Only two wires are nessecary from CIA to IEC port. Since I have some 1571 and one 1581 I tried this solution and it works perfectly.

Now I have found a burst kernel for C64 (cassette routines are lost). So my C64 works very fast with my burst drives, but 1541 is also working same time (slowly).

Now I got a C128-D with internal 1571 drive. C64 mode of this wonderful device is very slowly, so I tried to update kernel to this burst kernel.

It works very fine and it is very compatible (if 1571 run slowly, it will run also fast in burst mode). So it is a very good solution for me.

You will need a special adapter cause original kernel has a 23128 PIN layout. Replacement eproms like the 27128 have a different PIN layout: see here

A fastloader working with µIEC is already finished: SJLOAD

This is a very good idea with this long IEC cable! I also had problems to connect an additional drive to test demos on a real drive.

The documentation for Final Expansion is partly translated now from german to english: FE3 WIKI


Improvents are welcome, my english is really bad ...

Quote from: polishedball on April 08, 2010, 02:32 PM
I was able to get this working tonight had some difficulty flashing the device.  I had and outdated avrprog.exe upgraded and it flashed fine;

very fine, gratulation!

I first saw your PM and was wondering about this problem and did not know the solution.

Quote from: polishedball on April 08, 2010, 02:32 PM
  however if I put anymore that 25 files on the SD card it errors out and locks up the uiec if I try to load them.  It gives a file not found for anything in the list after the 25th.  Is this a limitation of the interface? 

Maybe a limitation of the µIEC, not of the IEEE bridge.

Never heard about such a limitation. I'm using sub directorys so maybe I never got this limit.

Quote from: polishedball on April 08, 2010, 02:32 PM
Is there a way to setup directories or use some sort of image file?

Yes, µIEC supports sub directorys and of course D64 and D81 image files.

You can change into it with

@CD:SUBDIR
@CD:IMAGE.D64

Quote from: polishedball on April 08, 2010, 02:32 PM
I use jiffydos on the C64 side so I don't know many of the long string commands. Thanks for your software it is a huge improvement over tape, and having to repair my drives.

first: IEEE2IEC is deeply beta. I made it and nobody was interested first. So I didn't give it much time ...


second: I only tested it with real drives like a 1541, never tested it with µIEC.


The bridge should be improved with Jiffy support and maybe better timeout handling.

But I'm hoping someone make a real SD2IEEE hardware and I can change µIEC firmware to support it. This would be a better solution than this bridge with µIEC.

No one sent problems with release candidate so I release r020 today:


As usual please download r020 from FE3 download page.


Many thanks to Vic20-Ian for translating FE3 Loader file docu: click



Changes: 

   
• Bugfix: BLKD command fixed

   
• Diskloader is improved. It works now with programs starting at cassette buffer address. But this file must be loaded at last (if more than one file)!

   
• SAVE has a shorty in FE3 wedge. With "arrow left" you will do a SAVE.

If file already exists on the disk you can choose between "update" und "replace".

Replace simply send a @S: command to delete the file first.

Update will hold 2 versions of the file. It always does a "delete old file", "rename file" and "save file" sequence.


Caution: "update" will work only within D64 image files, not in normal file system of the SD card. This is cause SD2IEC (µIEC) doesn't process the @R: command outside of image files.



Replace:



Update:

Quote from: RobertB on February 04, 2010, 02:26 AM
I have one of those.  Unfortunately, I never got it to work.    Though it recognizes that an IEC drive is there, when it is given a command like LOAD, there is no drive activity.

Which configuration do you use? CBM-8032 with IEEE2IEC bridge on a 1541?


Please try to disable IEEE-488 timeout by entering POKE 1020, 255


This solution is from this location: click


Maybe the problem is, Atmel is too slow after a request from your BASIC-4 Host.

A real IEEE-488 floppy has a hardware (Exclusive OR) to flag NRFD immediatly after PET set ATN line. Your PET expects NRFD low nearly immedeatly after setting ATN, otherwise it reports a timeout.

This doesn't occur if you have IEEE2IEC and also a 8050 Floppy on the bus. The floppy does the "trick" for the IEEE2IEC bridge.

I will see to get it work with an PIN interrupt. A 14,7MHz AVR should fast enough for this ...



Same problem exists with some Commodore IEE-488 hard disks I heard a short time ago ...

CPLD designs for PET /CBM and floppy drives (1541/1571) are finished.

it is possible to flash CPLD design by a connected Bumble-B directly in David-65. So updates and changes are possible without a JTAG programmer.


David-65 also gets a highspeed connection port. Together with a Bumble-B it is possible to connect a PC by USB and transfer Data directly between 6502 and PC.


I'm in contact with a member of VICE team. It seems VICE will emulate David-65 in future!

The Final Expansion 3 already is emulated in VICE, thanks to VICE Team!!

Quote from: dr.v on March 06, 2010, 12:55 AM
Many years ago (about 20) when I was a teenager I was extremely involved with the c64/128.  I ran a BBS, was active in my local users group, did a ton of 8 bit assembly coding, helped repair C= equipment, etc.  Then I graduated from high school, went off to college, and gave up my time consuming hobby.  Even sold off my equipment.  14 years of college, 4 degrees, and 1 tenure track university position later I decided that it was time for me to return to my passion for C=.  You can imagine how excited I was to find all of the people here (people like you, Diddl) who helped keep the faith over the many years.   

Yes! Same here.

As a teenager I did many programming on 4032 and 8032 computers. Later I got a C-64 and was happy with it. Many years I forgot commodore while working on PC's and mainframes.


In 2008 I found my old floppy disks and wanted to get their contents on my PC. I was very amazed cause this big community! For 4040 and 1541 it would be simple with a XA-1541. But none of my PC has a LPT port (only USB) and my 8050 disks wouldn't be readable cause IEEE-488.

So I took an Atmega32 and made the XS-1541 to connect my drives to my USB port.


After this the Commodore fever was burning hard. At eBay I got a VIC-20 and I was inspired to make Final Expansion 3.


Now I'm working on a 1541 floppy speeder (200 times) - David-65.

---

But bakc to ontopic ...

Maybe you can patch Maverick to run with your CMD drives? Are ROM listings of the DOS available for CMD drives?

bugfix release r019a :: many thanks to nbla000 from denial board!


download as usual at http://vc20final.t-winkler.net/zip/


Image for VICE included ...

I collect drives since nearly two years and I have now many drive types: 1541,1541-II,1570,1571,8050,SFD,8250 in my 8296-D.

For 1541 and 1571 I have nearly all popular parallel speeder except prologic DOS.

I'm very interested in this kind of hardware ... 

----

CMD drives are very good but very rare also, so I don't have a CMD drive. And I know nearly nothing about CMD drive hardware internals.


Maverick is the ultimate software for Commodore drives. it is very special to 1541/1571 hardware. Why do you believe it would work in a CMD drive?

Is a CMD drive so similar to a 1541 (same ROM, same IO (VIA) on same address)?

If CMD drives allow partitions the system ROM (DOS) cannot be the same. Maverick calls code from DOS ROM, if a drive has not the correct code in this address space it will fail (it must fail).

My english is not so good ...

"1541 emulation partition" is not really clear for me. I thought you speak about emulation in an emulator like VICE?

Maverick needs modified drives with 8K RAM expansion (RAMboard) at $6 or $8. Maybe you have to configure this RAM in emulator (VICE is able to emulate additionally RAM simply).


Some of the Maverick tools run since I got a special RAMboard (Supercard plus). I have analyzed this and found this card has 8K RAM and additionally a special ROM between $0800 and $17ff (4KB). This ROM hold some functions for reading whole tracks and other strange stuff.

With Supercard+ runs Maverick a little faster at beginning cause no upload of code is nessecary.

Yes, I had same problem cause I bought a 1581 without drive from canada.

I couldn't find any drive fit in my 1581.
Someone told me take a amiga drive. Amiga drive doesn't fit.
Someone told me no HD drive.
Someone told me you must change some things in the drive electronics (don't want to change this).


Finally someonetold me to make a "special/modified" ribbon cable ...

And this was it!! I have 7 drives here, HD and normal density, different companies (Teac, Sony, Amiga drive), all of my 7 drives work properly in my 1581!!

Solution:  click
Picture:  click

you simply could write a copy program to copy from 1581 to 1571.


normally CP/M itself can do this with CP command.

With XA-1541 and OpenCBM or with XS-1541 you can directly read 1571 diskettes into a D71 file on PC.

Nils from "For8Bits" is developing a new hardware for PET and CBM computers.

It is very similar to Final Expansion for VIC-20 but it is more universal useable. David-65 works on every 6502 board: PET, CBM, VIC-20, any Commodore Floppy ...

Simply do following to install David-65:

   
• remove 6502 CPU (hope it has a socket)
• insert David-65 into CPU socket
• insert CPU into David-65 board

David-65 offers nearly same features than a FE3:

   
• CPLD for programmable memory configuration
• additionally 512 Kb SRAM
• additionally 512 Kb Flash  (programmable)
• a RS-232, very slow only for debugging (software driven like in a C-64)
• a LED for diagnostic purposes

---

What are the benefits for using a David-65:

   
• extension of a PET / CBM
  
  Any PET or CBM with 8KB or 16KB will have 32KB also
  
  If RAM or ROM (or both) is damaged David-65 will replace it without soldering
  
  You can choose between any BASIC, any Kernal and any Software extension (ExBasic, Assembler, ...). You can switch between different editor ROM and different languages. And of course any RAM configuration, also for normally ROM address ranges.
  
  New Software can use whole 1MB of the Davuid-65 memory
  .
  
• Diagnostic
  
  David-65 can start with own Flash and own RAM, so nearly no "external" hardware is nessecary. Only power and clock for the CPU is nessecary to run diagnostic.
  
  A badly hard damaged 6502 system could be analysed from CPU's sight. Even if Kernel or Zeropage is damaged, David-65 will find it out.
  .
• Ultimative Speeder for a 1541 drive
  
  My personal favourite goal is the ultimate speeder for a floppy drive. Davied-65 can hold tw0 D64 Images or one D71 image. Installed in a 1541 floppy David-65 can read whole disk into memory and so access data in RAM disk like speed. Write access goes into RAM and will be written in idle time (lazy write back).
  .
• David-65 can act as a standalone 6502 board if a 5V power and a clock is available ...

Many other things are possible with David-65, cause CPLD design makes it possible to adapt it to any 6502 system.

---

IEC on a PET/CBM/CBM-II is possible simply since 1 year with my IEEE2IEC Interface.

It' like to drive a Ferrari with a beetle engine ...


IEC on a cassette port of a PET has 2 main disadvantages:- You will need a firmware or a changed kernel

- speed is horrible slowly