Boot from CD with a BuddhaIDE and why does my CF card not work in BuddhaIDE?

Caution: Non registered users only see threads and messages in the currently selected language, which is determined by their browser. Please create an account and log in to see all content by default. This is a limitation of the forum software.


Please understand that you need to create an account to be able to post, guest posting was disabled as an anti spam measure.

  • So, I have a A4000 with a Buddha IDE (20-year anniversary edition).


    I want to boot CD's like the bootable AmigaOS 3.2.


    I have not used the machine for several years and just installed KS47.111 roms and AmigaOS 3.2.2.1.

    I did also flash the Buddha IDE with latest FW and update the DOM.

    Now my problems:


    I want to boot from CD's, and I remember doing that before and have a CD32 emulator.

    But it's not working anymore. And the new installer in the DOM is not the same...


    So trying a clean install on a "new" old CF..


    If I boot the DOM in the right/second slot and have my CF32GB card in the left/first slot I can not see the CF card.

    If I exchange it with my old CF64GB card it shows. It shows, but I cant delet that because it's the only card booting on the BuddhaIDE.


    I have 1x64GB and 2x32GB, all of them Sandisk Extreme Pro. Works in my A1200, both on the IDE and the CF PCMCIA adapter.

    If I move the CF32GB to the IDE (I have a IDE to CF adapter on my internal controller for data transfer) then I can partition it with HDTOOLBOX.

    But the Buddha DOM does still not see it if I move it to the Buddha controller afterwards...

    Questions:

    How do I make the CD-ROM drive bootable when connected to the BuddhaIDE (oh and it's connected with a Zip100 IDE drive that does boot).
    What am I doing wrong with my CF card?

  • I want to boot CD's like the bootable AmigaOS 3.2.

    This is not possible, as we don't have enough room for a CD file system in the boot ROM of the Buddha.


    I want to boot from CD's, and I remember doing that before and have a CD32 emulator.

    You clearly did not boot. The CD32 emulator was part of the old package that we included with the previous versions of the Buddha, made by Elaborate Bytes. You probably installed that, and used CD32 titles from a booted WB.


    Your CF card problems may be explained by the origina (=old!)l Elaborate Bytes software that you have flashed, as that's the only one that boots from ZIP100 media. The new software that we've developed for the 20-year anniversary edition does not boot from ZIP drives, and it will confuse most F cards with ZIP or LS120 drives and talk ATAPI instead of ATA-X3T9 to them (that's the techy term for "not seen by HDToolbox").


    So please do use the latest ROM for your 20-year anniversary controller, not the Elaborate Bytes ROM, and what has worked before will also work now.


    Jens

  • I flashed my Buddha card with this one:


    Is there a newer one for my card?


    I did have to update the DOM, and the old CD installer with CD32 emulator did not work, wrong SCSI device.


    I had to change the CD dosdriver to buddhascsi.device to mount it in Workbench.


    But I do remember booting CD's but it might have been with a resident driver that needed a boot from HD or Floppy.
    If that was not with the Buddha CD software, i could have used something else. And it could have been with the internal IDE.

    If it is as you say impossible :)


    ZIP disks boot fine both before and after flashing the Buddha card.
    But if not booted from them I have to mount them the same way I do with CD.
    Had to change for buddhaatapi something to buddhascsi.device


    In Hdtoolbox I also change to buddascsi.device to scan the CF, but that only works on the CF64GB and Zip100 disks but not the CD32GB cards.

    I use the Internal IDE for external CF cards. For quick transfer and testing stuff.
    So I would like to use the Buddha with Zip&CD + Main CF

  • I flashed my Buddha card with this one:

    You even quoted the answer: Only for versions before the 20y-edition.


    I had to change the CD dosdriver to buddhascsi.device to mount it in Workbench.

    This doesn't compute. The old flash that you've programmed into your unit does not use buddhascsi.device, but "scsi.device" and "buddhaatapi.device". Things don't really add up here. Please make sure to use the software that is intended for your controller, and don't expect it to do things that it was never advertised to do.


    Jens

  • I think I did copy that image from the wrong place when asking the question:


    This is the file I used:


    And the CD drive is on buddhascsi.device


    "scsi.device" and "buddhaatapi.device" was used on the original firmware before flashing.
    But I was seeing multiple zip's and CD's.


    So if I flashed the wrong .bin file, help me find the one I need :)

  • I really like how you make the pictures small so we really only see the important stuff.


    Rom 52.101 is correct for your version of the Buddha controller.


    However, depending on the age of your controller, it may have been shipped with the Elaborate Bytes driver, and that's why you may remember booting from ZIP.


    It may even have the old CPLD in it. Where and when did you buy it? What's the output of the flash tool, what does it say about the CPLD version?


    Jens

  • If I run only the flashtoo with no bin:


    Booting from ZIP works fine:


    It was bougt from Amigastore.eu in January 2018.

  • ...and Amigastore never sent you the JTAG adapter for upgrading the CPLD? We've sent these cables and floppies to all resellers for free back then. Seems like they "forgot" to forward these parts to you.


    In any case, compatibility with CF cards will be higher after you do the CPLD upgrade. You can also build your own cable according to these instructions. However, you should claim your free JTAG cable from Amigastore - they shouldn't have kept this from you when they got it for free from us.


    Boot support from ZIP is indeed surprising for me; I didn't know that this works.


    Jens

  • USB Blaster is an Altera (now Intel) thing. The CPLD is a Xilinx part. The the small USB dongles look like UART adapters, and the large thing is an EPROMmer - nothing of that will help you. However, since you seem to be a bit into electronics, you should be able to make that cable according to the instructions in our Wiki. It's only six wires!


    Never received a JTAG adapter. Probaby because I'm in Norway.

    I've shipped these cables and floppies worldwide. And there should be no excuse - the parts were shipped to Amigastore for free on the condition that they will ship them to all customers. If they deliberately left you out because you're in Norway, you may have to look for a more trustworthy partner to buy from next time. We really should not jump to conclusions - they should still have your stuff, and if you contact them about the cable, they should at least be able to tell you why you were not informed that a free upgrade package is available.


    Jens

  • I agree with you, but way back then I gave them up...

    It started with the KS 3.x with a floppy bug (if I remember correctly).
    Months of mailing, and no reply even if when they had a new revision with the bug fixed.
    And calling them did not help.


    A year later we had a epic roadtrip, and drove by them... After first denying everything, they eventually agreed to flash a new set for me.
    I ordered a lot of new stuff after that, including the Buddha:

    But when the budda did not work there where no help. I probably messed up something, and in the end I figured out to replace the little resistor on the board and got it up and running.

    So, I really have no hope in trying to get a cable from them. I'll be better off making the cable.
    Unless I drive past them again :)

  • Definitely a lot quicker to make my own cable and boot from floppy :)


    Now boot from the 32B CF cards work, and even MicroSD->SD->CF->IDE adapter...
    ZIP drive still boots fine like it always has:


    But the device is still buddhascsi.device not buddhatapi.device or scsi.device (just info, not complaining).


    CD still works mounted with buddhascsi.device.

    Now to figure out if there is third party software to make a CD boot floppy or put a resident driver after first boot.

  • Now boot from the 32B CF cards work, and even MicroSD->SD->CF->IDE adapter...

    Great - the CPLD upgrade does relax the IOR/IOW timing a lot. Both old and new within spec, but the new timing has a lot more slack.


    But the device is still buddhascsi.device not buddhatapi.device or scsi.device

    That's expected. Only the old Elaborate Bytes drivers use different names. You can still use them if you absolutely have to use an old LS120 drive, but you'll loose a lot of CF compatibility. My personal recommendation is to stay with the new drivers.


    Now to figure out if there is third party software to make a CD boot floppy or put a resident driver after first boot.

    First and most simple solution that comes to mind (well, at least my mind) is to make a small script and put that on RAD:, along with the required file system. Mount the CD drive, assign SYS, C, DEVS and all that to the CD and you should have a CD with your WB stuff on. This is technically not booting from CD, but loading everything from there that didn't fit on RAD:.


    Jens

  • IDEFIX97 was probably what I used to boot the CD drive, but I guess it was on the internal IDE controller...

    Got it running with CD32 emulator now :)

  • IDEFIX97 was probably what I used to boot the CD drive, but I guess it was on the internal IDE controller...

    The old Buddha drivers were actually built on the same source code as IDE-fix 97. However, no system that I'm aware of (other than CD32 and CDTV) has ever cold-booted from a CD.


    Jens

  • The A4000D internal IDE can boot with this:

    Aminet - disk/cdrom/mountcd.lha
    Needs a reboot after and then run, I had a CD boot floppy somewhere...


    That way you can boot AmigaOS3.2 CD and install.


    Most of the fun is getting everything working :) Then I can rest and put everything away again until the next time I want to play.

  • The last reply was more than 365 days ago, this thread is most likely obsolete. It is recommended to create a new thread instead.