GP32 Gpdrive In Bios

[jlebrech]

Would it be possible to have a new firmware with an integrated gpDrive on it, like when u push the start button when u start.

 

[aquafish_]

make it yourself, use Zed (www.egloo.fr.st)...

 

[lizard808uk]

Zed is great, I use it for my digital camera (I have a file browser [Comi] and JpegView wrapped in a firmware). So sticking gpDrive in your own firmware won't be too difficult.

 

[phoda]

I have done it - Zed worked great. I made my firmware and incorporated Windups V1.0 as well as GP Drive 0.5 - windups boots fine. GP Drive also starts when selected, but gives the message "SMC Unknown - message halted".

 

[slubman]

Just a question: what is zed ?
Stupid post :unsure:

 

[ColinR]

Zed's dead, baby. Zed's dead.

Going from the context of this thread, I'd guess it would be a bios constuction tool.

 

[Squidge]

I have done it - Zed worked great. I made my firmware and incorporated Windups V1.0 as well as GP Drive 0.5 - windups boots fine. GP Drive also starts when selected, but gives the message "SMC Unknown - message halted".

Yup, the bios failed to initialise the smc hardware (couple of registers) before running the app. This is of course, assuming you have an SMC in there...

 

[phoda]

@ Squidge: yeah - I definitely had the SMC there The test I did was:
1- Bootup starting Windups 1.0; 2- Run GPDrive : worked
1- Bootup starting GPDrive: did not work

@ Aquafish: I used mr. spiv's BIOS when I compiled it. Haven't tried with different BIOSes though, so I do not know if this might be this BIOS "fault"...

@ ColinR: zed is a firmware construction tool made by Aquafish. Basically you select two different applications on GXB format (eg Windups and COMI) - zed will create a firmware using those applications as well as a BIOS of your choosing. The firmware will also have a menu, just a multifirmware. Very nice.

What seems weird to me is that GPDrive is working with this BIOS - however, only after another app (Windups) has started. Could this be bug in zed?

 

[lizard808uk]

Have you checked the readme with Zed? Theres a matrix showing which pc link programs work with which bios firmwares... You'll probably find that it'll work without the Bios monitor

 

[Squidge]

Once Windups (or any other file has been read from the SMC), then the hardware is initialised and GpDrive will work as normal. Before the hardware is initialised, GpDrive will not find any SMCs to use.

 

[phoda]

Squidge: can't GPDrive read the SMC to force a hardware initialization? I am actually insisting on this because it seems GPDrive, as it stands, can't be used on any multifirmware - and being such a useful program I believe a lot of users hope this could be implemented on a future multifw.

 

[Squidge]

It could yes, and if someone made there own multi-firmware (not using Zed), then they could easily initialise it before executing any of the bios programs. I believe that the hardware initialisation is simply a fact of hardware port setup (DDR).

 

[aquafish_]

@ Squidge: yeah - I definitely had the SMC there  The test I did was:
1- Bootup starting Windups 1.0; 2- Run GPDrive : worked
1- Bootup starting GPDrive: did not work

question : for convert gpdrive into a gxb, have you use mr.spiv's unfxe ??? it's possible that the problem come from it (it already made some problems with darkfader's pclink) , try to do that with gp_unfxe (avaiable on my website) it has more chances to work...

 

[phoda]

@ Aquafish - I actually used the GP unfxe since the very beginning, as per you "readme" recommendation.

@ Squidge - can you make a new version of GPDrive with the hardware initialization? Please? B)