CPCWiki forum

Here a new work with SyX about the CPC Firmware "v3".

FW 3.12

Quote
Fix the RSX use for ROM located from 16 to 31 (thanks redbox)

This Firmware was designed to get a better support of RAM and ROM expansions. Looking the future, not the past.
It don't work with BASIC 1.0 and no more support Tape by default. (need a ROM to manage it, that allow to improve it as new storages too)

So, the actual target is all CPC with BASIC 1.1 and floppy or HxC drives.

FEATURES

Quote- Display RAM (up to 576K)
- Display CRTC version
- Initialize up to 32 ROM*
- Boot with [ESC] initialize only ROM 0 & 7
- Mouse support under BASIC (see the previous FW test (http://www.cpcwiki.eu/forum/amstrad-cpc-hardware/firmware-mouse-support-!!!/))
- Fix the FR chars table, so all keys are properly displayed.
- CTRL+keys give usefull chars

CTRL KEYS

Quotectrl+2 = ½ (half)
ctrl+3 = ¾ (three quarters)
ctrl+4 = ¼ (quarter)

ctrl+a = α (alpha)
ctrl+b = β (beta)
ctrl+c = © (copyright)
ctrl+e = € (euro)
ctrl+m = µ (micro)
ctrl+n = ~ (tilde)
ctrl+o = Ω (omega)
ctrl+p = π (pi)
ctrl+s = Σ (sigma)
ctrl+v = √ (tick)
ctrl+x = ✗ (cross)

ctrl+? = ¿ (inverted question mark)
ctrl+! = ¡ (inverted exclamation mark)

Enjoy and thank you for your feedbacks ! :) 

* The 32 ROM init actually only work on a real hardware with the Megaflash and FlashGordon boards.
Most emulators are not supported.

- Support MegaFlash 32 ROMs under BASIC : does that mean it initialize the 32 rom ? or that you can program the megaflash rom with it ?

Any plan for sharing source ?

@gryzor / markus, any plan for svn server on cpcwiki ?

Fixed.
Init 32 ROM at boot or only 0 and 7 if ESC is pressed.

Sorry, but no source sharing for now, because it's WIP.
But, the SVN server for CPCWiki dev is a nice idea. :)

And the most important thing, TotO had all these nice ideas ;)

PD: I'm using exclusively this rom since the last two weeks and only use the original rom for checking compatibility :)

does it need any rombox or you must replace the original physical rom on the motherboard ?

You can make that or use one the lovely LowerROM boards (http://www.cpcwiki.eu/index.php/LowerROM) of Bryce :) (a few weeks ago he asked here (http://www.cpcwiki.eu/forum/amstrad-cpc-hardware/lowerrom-batch/) for people interested in one for making a new batch)

Useful !!! that's great job...and there are so many things to implement ...I think many of us will have ideas in the next few days :)

The modifications are frozen for now as far as I know. No further mods planned. At least for this batch of LowerROMs. The people who have ordered one should PM me and let me know what they want on their EPROM (2 versions of Firmware/BASIC fits on the device, selectable with a jumper). I have just finished building the first devices, I should have all finished by next week.
I also think they have ran out of space in the ROM?

Bryce.

It's freezen for now, but we hope to get feedback to improve the project. 

With respect to the rom space, the old versions were where we ran out of it, and the reason why we decided to remove the firmware tape routines; now, we have 1.465 bytes free, more than enough for new features, but they need to be great for justify the bytes used :)

Very cool guys, very cool  8)   :)

Nice work SyX & TotO  ;)

Cheers,
Shane

Check out the ROMs I uploaded, they take away ,p protection and such stuff. They may be of interrest for your project. Sorry can't write more here, still working...

Quote from: Bryce on 20:34, 18 October 12The modifications are frozen for now as far as I know. No further mods planned. At least for this batch of LowerROMs.

Yes, it's the first release and we use it since 2 weeks w/o problem.
We don't plane to release v3.2 w/o new significative features.
No other update will be done before the end of the world year.

A "tip" for french users.
If you order the Bryce's LowerROM and ask to program it with:
- Firmware EN
- Firmware FR

Then, the jumper will act as a QWERTY/AZERTY switch! ;)
(for the same computer with compatibility, or if you got both type)

Two screens, booting with and without the [ESC] key.
(AMSDOS ROM 7 & PARADOS ROM 6)

Did you try to use ParaDOS on ROM select 7?

Sure, why?
I just put Parados at ROM 6 to be able to disable it with ESC, w/o loosing a DOS at boot...

Ah, see you point.

Hi TotO & SyX, not sure if there is any documentation regarding all the differences between FW3.1 & the original Amstrad FW.

I Just went through the CTRL+<key> combinations and noted them down for anyone that is interested...

ctrl+1 = ¡ (inverted exclamation mark)
ctrl+2 = ½ (half)
ctrl+3 = ¾ (three quarters)
ctrl+4 = ¼ (quarter)
ctrl+e = € (euro)
ctrl+o = Ω (omega)
ctrl+p = π (pi)
ctrl+[ = Ɵ (theta)
ctrl+a = α (alpha)
ctrl+s = Σ (sigma)
ctrl+x = ✗ (cross)
ctrl+c = © (copyright)
ctrl+v = √ (tick)
ctrl+b = β (beta)
ctrl+n = " (quotation)
ctrl+m = µ (micro)
ctrl+/ = ¿ (inverted question mark)

Please correct me if I am wrong or have missed any.
This is with the EN firmware.

Cheers,
Shane

Oooh I'm getting this on mine.
Nice choice of colours, btw! (though I probably like QCMD's more).

The extra characters are nice (oh, euro! Just in time to see it collapsing, but our humble CPCs will have its symbol :D ), though couldn't you make the F key (or other combos) perform actions, like the most frequent commands one uses?

Thanks for the hard work guys!!

Quote from: 00WReX on 13:24, 22 October 12Hi TotO & SyX, not sure if there is any documentation regarding all the differences between FW3.1 & the original Amstrad FW.

Thanks 00WReX!  :)

It's the only thing undocumented yet, aside from the info that TotO put in the first post.

Quote from: 00WReX on 13:24, 22 October 12Please correct me if I am wrong or have missed any.
This is with the EN firmware.

You are not missed any in the english firmware :) A few one of these were already in the original spanish rom, and we like them. The french and the spanish version include a few extras, mainly the french to be more logical, as TotO always said me :)

And as everything is open to your suggestions :)

IMPORTANT: This firmware is compatible with any 6128/6128+ basic rom. The 464/664 basic rom crash, but the same happen with the original 6128 firmware. Of course, it's possible to make a 464/664 version and give support to other languages, if enough people ask.

Quote from: 00WReX on 13:24, 22 October 12
Hi TotO & SyX, not sure if there is any documentation regarding all the differences between FW3.1 & the original Amstrad FW.

I Just went through the CTRL+<key> combinations and noted them down for anyone that is interested...
Please correct me if I am wrong or have missed any.
This is with the EN firmware.

I just speak about that in the afternoon. I don't take the time to add it, and though to do it this evening...
Thank you for doing it ! :)

- CTRL+N is not " but ~
- CTRL+/ because ? symbol is on the same key on EN keyboard.
- CTRL+1 because ! symbol is on the same key on EN keyboard.
- CTRL+[ because... It's a Buuuuuuuuuuuuug. :-\

All those shortcuts are common to all versions and are now updated to the first post of the topic! :)

Thank You!!! another time, TotO & Syx for your CPC dedication. You are great.

Quote from: Gryzor on 13:55, 22 October 12
The extra characters are nice (oh, euro! Just in time to see it collapsing, but our humble CPCs will have its symbol :D

Ha, Ha!!! (Spanish banks need Euros, me too  :P )

No, but seriously, why not have predefined commands?

May be, because I'm not enough lazy to though it was a priority?  ;D
Or because, that need more reflections to add that on the first version.

It would be nice to have commands like CAT, LIST |A, |B or |CPM as function keys. Not sure about BASIC commands, but OS type commands definitely :)

Bryce. 

Of course, it's perfectly possible to add those predefined commands to the function keys, although i think that we should add in the last line of the screen the commands associated to the function keys, as happens in msx computers... and we need to reach an agreement about useful commands ;)

It would be nice to use "non volatile ram" for saving for system and program configurations, for example a rom in the MegaFlash or an RTC with a few KBs of ram.

Quote from: SyX on 21:21, 23 October 12
It would be nice to use "non volatile ram" for saving for system and program configurations, for example a rom in the MegaFlash or an RTC with a few KBs of ram.

Some years ago I defined a data structure for the usage of the nvRAM of the SF2 and the CPC Booseter. Details are in the FutureView and I guess also in the Wiki.

Please keep up with that standarts. Needes sources are provided.

Quote from: Bryce on 20:41, 23 October 12
It would be nice to have commands like CAT, LIST |A, |B or |CPM as function keys. Not sure about BASIC commands, but OS type commands definitely :)

Bryce. 

Yes, that would be nice.

Basically for this reason alone I have the Microstyle ROM on my ROM boards.

[attach=2] [attach=3]

Or maybe use some of the CTRL+<keys> that are not currently used.

Example...

ctrl+d = |dir
ctrl+l = list

etc

Cheers,
Shane

@Bryce: I agree, I guess OS commands are much more frequent than BASIC ones...

@Syx: erm, yes, but now you're talking about a new device :D But yes, a bottom line with the commands would be nice indeed!

@00WReX: Microstyle looks nice, I had forgotten about that! I should probably load it onto my board...

I only ever loaded Microstyle once to try out the games. I didn't realise it offered that. Really cool. It will be uploaded to my MegaFlash tonight :)

What exactly does f6 do?

Bryce.

Sorry, only included page 2 of the help screen...
Below is screen 1...PANIC is one of the RSX's that is added with this ROM.

Basically just used to reset screen colours back to default...

[attach=2]

Cheers,
Shane

"CRTL + Alpha/Digit Keys" don't have to be used as commands, because :
1- It's not in coherency with the original Locomotive spirit
2- It's not possible to add functions on them, only extra chars (see answer 1)

"CRTL + Function Keys" can be used for RSX, but :
1- To be usefull, the RSXs have to launch something w/o parameter.
2- To be usefull, the user have to be free to customize the keys. (not possible in FW but ROM allow that)

Thank you for your ideas. We keep them on the box.
Adding a |A |B, when you can type those shorts commands as faster as pressing a key, look so gadget.
Better than each people load a dedicated ROM for it's own shortcuts usages. :) (like I can see it on the previous page)

With this conversation i have remembered an old program for the spanish magazine "Amstrad Semanal" (i have attached), that it can be useful for testing the idea.

The instructions for loading are:MEMORY &9FFF:LOAD"WINKEY",&A000:CALL &A000

After that use the RSXs "|ON" to show what print the function keys and "|OFF" to hide.  For redefine the functions keys use KEY FKEY_NUMBER (0-9),"string" + CHR$(13) (for adding an ENTER to the string). For example: KEY 0,"LIST"+CHR$(13)

Quote from: Gryzor on 07:11, 24 October 12@Syx: erm, yes, but now you're talking about a new device :D But yes, a bottom line with the commands would be nice indeed!

Well, i think that everybody would like to configure freely the commands for the function keys, but not everybody is able to rewrite the eprom with the firmware. And because that, this functionality is much better for a rom in the MegaFlash or for another non volatile ram device (an RTC + RAM powered for a battery, jejeje).

Great program!!!
Let me share my settings!  :-\

KEY 0,"0"
KEY 1,"1"
KEY 2,"2"
KEY 3,"3"
KEY 4,"4"
KEY 5,"5"
KEY 6,"6"
KEY 7,"7"
KEY 8,"8"
KEY 9,"9"

Quote from: TotOGreat program!!!
Let me share my settings! 

Code: [Select]KEY 0,"0"
KEY 1,"1"
KEY 2,"2"
KEY 3,"3"
KEY 4,"4"
KEY 5,"5"
KEY 6,"6"
KEY 7,"7"
KEY 8,"8"
KEY 9,"9" 

:D :D :D

...a question: The new Firmware only allows Control+Keys which were defined in ROM and the function of other Control+Keys were disabled?  Is that correct?
Just aksing because I wanted to work with Protext (ROM version) and tried to make settings for a Right-Justify (e.g. press Control+J), re-formatting (Ctrl+F), Help (Ctrl+H) etc. which weren't active any more.

Yes, I have the same problem. A major drawback. However no problem with a LowerROM, just switch it "hot".

Ooh, yeah, it's quite bad if it takes over key bindings even in other programs... Of course, yes, it's not a biggie, just reboot with the original FW!

We are looking that.
What I know is the Firmware change only the ASCII char for the CRTL+KEY.
So, it does not affect a program that properly test the keyboard.

Quote from: HAL 6128 on 22:27, 06 November 12
...a question: The new Firmware only allows Control+Keys which were defined in ROM and the function of other Control+Keys were disabled?  Is that correct?
Just aksing because I wanted to work with Protext (ROM version) and tried to make settings for a Right-Justify (e.g. press Control+J), re-formatting (Ctrl+F), Help (Ctrl+H) etc. which weren't active any more.

It's as TotO says, Protext is reading chars generated for keys, instead of key numbers for function keys, as we changed those for showing the chars that we thought they are more useful, at least for us :P

We both don't use Protext and because that we never saw this problem in our tests... and neither will see it :P

Now after i have checked it and read the manual during this morning, Protext use practically all the CTRL combinations, not nice for our new combinations in the firmware.

There is varios solutions, as TFM and Gryzor says, for the Lower ROM users is so easy as when you need Protext change to the original firmware. Another fast fix, it would be insert the original keytable in the FW3.1, but you are losing the new chars. A more elegant solution would be make a pair of RSXs for enabling/disabling the new original keytable, it would be easy to put in a rom in the MegaFlash  (i have tested this, using KEY DEF from basic, for redefining the new CTRL combos to the oldies and then Protext worked again).

Quote from: TotO on 14:30, 07 November 12
We are looking that.
What I know is the Firmware change only the ASCII char for the CRTL+KEY.
So, it does not affect a program that properly test the keyboard.

Well, that not the point. The point is in which way it does influence the programs which one usually uses. Your intention is to make life more easy right? Let's keep it that way :)

In life, peoples who want to change nothing are free to do nothing.
Others go ahead with ideas and convictions.
The past errors don't have to limit the future ways.
Else, the human stay a monkey. ;)

That's so true :)  And now give me my banana :laugh:

Quote from: TFM/FS on 03:24, 08 November 12
And now give me my banana :laugh:

Why, FutureOS change nothing in the CPC life ?  ;D 
The LowerROM is an opportunity for doing new things for peoples who buy it.

Quote from: TotO on 14:00, 08 November 12
Why, FutureOS change nothing in the CPC life ?  ;D 
The LowerROM is an opportunity for doing new things for peoples who buy it.

1. I agreed with you, and I made a funny joke - which may not have been French enough? :P :laugh:
2. I see no connection to FutureOS here, but you tend to mention it when I post something. Slowly I see a pattern (imagine scary sound effects right here...) :o
3. The only thing about FutureOS you know is it's name, right? :D
And - hey - you are a well appreciated member of the scene, like others too. It's not my intention to offend you. I know writing a post never tells one if a sentence is ment serious or not. So just assume the positive  :)

Quote from: TFM/FS on 17:27, 09 November 12
1. I agreed with you, and I made a funny joke - which may not have been French enough? :P :laugh:
2. I see no connection to FutureOS here, but you tend to mention it when I post something. Slowly I see a pattern (imagine scary sound effects right here...) :o
3. The only thing about FutureOS you know is it's name, right? :D
And - hey - you are a well appreciated member of the scene, like others too. It's not my intention to offend you. I know writing a post never tells one if a sentence is ment serious or not. So just assume the positive  :)

You said: "give me my banana" in answer to "else humain stay a monkey if he don't go ahead".
Because you make FutureOS and ask for a banana, I may suppose that FutureOS don't go ahead.
It's just a joke, nothing more... A you, because you don't understand (connexion) you though that is a personal attack.  May be your susceptibility. Sorry, but it was not the goal of my post to offense you.

Mine either! :) Well, I had a hard time during the last days, few sleep, and Engish is second language for both of us. That doesn't make it more easy either. ;D  But back to topic now... I used 3.1 quite a while and I can say it runs very stable and realible. Well done!

Have just started using this firmware on my Lower ROM board...on a real CPC  :D  (previously only tried it on an emulator).
I must say I do like it, and the mouse functionality is nice.

The "ESC" feature to bypass the ROMs is also very handy also.

Thanks again guys  :)

Cheers,
Shane

Just Last night I made a Plus cart with this Lower Rom, The Plus Default basic rom and Parados 1.1 in slot 7.


As the 6128+ has no tape interface then the tape commands were pretty useless anyway. This however is an excellent update. Good work all round.


One question tho. Is anything special needed for the 32 rom initialisation to work, or have I missed something? I have various foreground roms in slots above 15 (DosCopy & Crime, Stylerom etc) on my Symbiface 2 and they appear not to be initialised automatically at boot.


With the 32 rom booster in slot 15 all is well however this is a rather 'untidy' solution  ;)


I will upload the CPR and BIN files tonight if anyone else in interested in using this on a Plus, or i can burn roms for anyone who wants them as I have over 50 blank 27c2001s left ;)

Strange, that setup should work, but maybe TotO or SyX can answer that. I'm not sure if Firmware one needs to have the Classic 6128 Basic or whether the Plus Basic will work too.

Bryce.

Quote from: CraigsBar on 18:19, 30 January 13
With the 32 rom booster in slot 15 all is well however this is a rather 'untidy' solution  ;) 

Why do you call it an untidy solution? Do you have any reason? I think this software is well done.

Quote from: TFM/FS on 18:46, 30 January 13
Why do you call it an untidy solution? Do you have any reason? I think this software is well done.

Only untidy because, If I understand correctly, the Lower rom should do it without the need of the booster rom. No biggy I mean 30 rom slots is plenty for anyone isn't it? it's just that using the booster should not be necessary, right, thus releasing slot 15.


The booster rom is excellent and has been in use in my symbiface since the day it arrived, but if the firmware initialises 32 roms by default it should not be neede any more.


Regards


Craig

In a SF2, MegaFlash, any EPROM card you can NOT change the firmware. So you DO need the Booster ROM. And you can fill up the Booster ROM with another 15 KB of software using Softbrenner. So nothing is wasted.


Well, at least it seems you don't intend to smite the Inicron software, maybe I got you wrong there.

Quote from: TFM/FS on 18:55, 30 January 13
In a SF2, MegaFlash, any EPROM card you can NOT change the firmware.

Indeed, But in the 6128+ cartridge I created WITH firmware 3.1, basic and Parados 1.1 as detailled above you can ;)


So my 6128+ now boots with firmware 3.1, and a Symbiface attached, should this not work with all 32 roms without the booster ;)


Regards


Craig

Well, obviously it's not the Booster which can be called 'untidy'. Sorry couldn't resist :-*  Can you make a Cartridge with AMSDOS (0.50 from CPC6128) to check it with that?


Can you check a regular cart on you Plus? I don't see a reason why it shouldn't work honestly.

Quote from: CraigsBar on 18:19, 30 January 13One question tho. Is anything special needed for the 32 rom initialisation to work, or have I missed something? I have various foreground roms in slots above 15 (DosCopy & Crime, Stylerom etc) on my Symbiface 2 and they appear not to be initialised automatically at boot.

No, you haven't to do anything special, KL_ROM_WALK is fixed to start the initialization in the rom 31 (the address $0327 in the firmware rom has the starting rom number, 31).

Did you still have booster ROM installed? That might confuse things?

Bryce.

Quote from: Bryce on 22:19, 30 January 13
Did you still have booster ROM installed? That might confuse things?

Bryce.

No I removed it. I have now burned a 2nd cart using CPC 6128 Basic 1.1 and AmsDos 0.5


Again roms above 15 are not initialised in the Symbiface2


If I drop in the booster in 15 it works just fine.


Regards


Craig

A double installation of a ROM only uses up additional RAM. You can simulate this by putting the same ROM a couple of times into a ROM-Box.

The problem here is that the initialisation is missing!

Quote from: TFM/FS on 22:28, 30 January 13
A double installation of a ROM only uses up additional RAM. You can simulate this by putting the same ROM a couple of times into a ROM-Box.

The problem here is that the initialisation is missing!

Pardon?


I think I miss something

Me pardon too, missed some posts at time of my post. :laugh:

Well, it looks that i forget to fix the last check in the rom and only the first 16 roms were initialized.

Thanks to CraigsBar for discovering this bug and for testing the fix in the real machine. I have attached the fixed versions to this message.

PD: These roms reset continuously a few emulators, but work in the real machine.

Attached are the following ZIP files


Patched_Plus_EN_FW31.zip - The Menu patched Plus cart with FW3.1 inserted (English qwerty)
Patched_Plus_FR_FW31.zip - The Menu patched Plus cart with FW3.1 inserted (French azerty)
Classic_FR_Parados_FW31.zip - Classic CPC 6128 Cart (v3) with FW 3.1 & ParaDOS 1.1 inserted (French azerty)
Classic_EN_FW31.zip - Classic CPC 6128 Cart (v3) with FW 3.1 inserted (English qwerty)
Plus_EN_parados_FW31.zip - Plus cart with ParaDOS 1.1 and FW3.1 inserted (English qwerty)


All Archives contain a BIN eprom image for burning and use in a real cartridge, and a CPR for use in Emulation. I have tested all 5 in Mac Arnold and they work just fine.


The first two (Based on the Menu patched Plus cart) have still retained burning Rubber, |game or |jeux work to launch it.


regards


Craig

Quote from: SyX on 22:36, 04 February 13
Well, it looks that i forget to fix the last check in the rom and only the first 16 roms were initialized.

Thanks to CraigsBar for discovering this bug and for testing the fix in the real machine. I have attached the fixed versions to this message.

PD: These roms reset continuously a few emulators, but work in the real machine.

I have so far been unable to get the Spanish rom image to insert correctly into either a Classic or Plus Cart image. I will revisit that if requested, However as I have no need for it for now the attached English and French images should give a good selection of choices.


Regards
Craig

Very great job ! Thanks for these new .CPR files.

Quote from: SyX on 22:36, 04 February 13
Well, it looks that i forget to fix the last check in the rom and only the first 16 roms were initialized.
Thanks to CraigsBar for discovering this bug and for testing the fix in the real machine. I have attached the fixed versions to this message.

Thank you!
The first page was updated with the new files.
16 ROM inits = Standard ROM boards and lazy emulators.
32 ROM inits = Extended ROM boards like the Megaflash.

One last CPR file attached.


Spanish time


Classic_ES_FW31_Parados


Classic Spanish Basic, Firmware 3.1 Spanish, Parados 1.1


Regards


Craig

Hello,

I just burn a real eprom with the parados FR version and it works pefectly, except the ù which become | and it is not useful for french guys with AZERTY layout :)

For the rest, it is a very good tool into a cartridge:)

Quote from: Kris on 16:26, 09 February 13it works pefectly, except the ù which become | and it is not useful for french guys with AZERTY layout :)

Hello,

I suggest you to check again...
The FR layout is fixed to match with the AZERTY keyboard.
The original mapping is wrong and the FW 3.1 fix it.

So,
- The | key print the | char and no more the ù char.
- The ù key print the ù char.
- The ç key print the ç char and no more the \ char.
- The \ key print the \ char.
- The à key print the à char and no more the @ char.
- The @ key print the @ char.
...

;)

Right ! I use an old version to burn the eprom; now all is working fine !
THanks for your post ;)

Quote from: CraigsBar on 21:37, 05 February 13
One last CPR file attached.
...
Classic_ES_FW31_Parados

Hi! Ok, now you will say "Do it Yourself" and you will be right.... I'm just not aquainted to CPR format. However for a real CPC (WinApe wont work with it) it may be good to have a cartridge file with X-DDOS instead of Amsdos. Just my thoughts. Or VaraDOS (that Parados with the patch for Vortex Format).

Quote from: TFM/FS on 21:53, 09 February 13
Hi! Ok, now you will say "Do it Yourself" and you will be right.... I'm just not aquainted to CPR format. However for a real CPC (WinApe wont work with it) it may be good to have a cartridge file with X-DDOS instead of Amsdos. Just my thoughts. Or VaraDOS (that Parados with the patch for Vortex Format).

Sure no worries, Just let me know what languages you would like ;)

Regards

Craig

English :)

+ Fr please :)

Ask and you will be rewarded.


Unfortunately I could not get X-DDOS to work once the carts were tested. So the attached have been built with VaraDOS (Taken from the Executioner posting in the ParaDOS and Vortex thread)


Both the CPR and raw BIN files are attached below.

Thanks!!!! That's lightspeed!!!!

Quote from: SyX on 22:16, 30 January 13
No, you haven't to do anything special, KL_ROM_WALK is fixed to start the initialization in the rom 31 (the address $0327 in the firmware rom has the starting rom number, 31).

Is this all you did?

I spent hours trying to do this with the lower ROM (for use in a plus cart) and it never worked and I always got a resetting boot loop. 

However, I only ever tried it in an emulator (WinApe) and I never tried it on a real machine...  ???

Quote from: redbox on 12:46, 11 February 13
Is this all you did?

I spent hours trying to do this with the lower ROM (for use in a plus cart) and it never worked and I always got a resetting boot loop. 

However, I only ever tried it in an emulator (WinApe) and I never tried it on a real machine...  ???

Yes and an extra check there is a few bytes later (take a look in the upgraded rom). The reset boot loop only happened in winape for me. In caprice or cpcjava worked perfectly, and in the real machine too, as CraigsBar tested the last week :)

Welcome back!!! ;)

Quote from: SyX on 15:18, 11 February 13
The reset boot loop only happened in winape for me.

That's a lesson for me.  Spent literally ages trying to get that to work but was only using WinApe  >:(

Glad you had success though!  Must include your ROM in my Plus System Cartridge (http://www.cpcwiki.eu/index.php/Plus_System_Cartridge)  :)

CraigsBar has made a wonderful job making cartridge images with it, now they are in this thread, but when i can, i will prepare a page in the wiki with everything related to this revision of the firmware.

PS: And always test in the real machine, i have made this fault a lot :P

That happended exactly once to me! Not a second time! I had the perfect pixelwise scrolling, on an emulator, but it didn't work on the CPC. I learnt from that!

Quote from: SyX on 15:29, 11 February 13
PS: And always test in the real machine, i have made this fault a lot :P

Was wondering about this so had a look at your Firmware with a Hex editor.

I see you've patched KL ROM WALK and KL INIT BACK, replacing &0F with &1F and &10 with &20 respectively.  However, I noticed that you haven't patched KL FIND COMMAND which also has a CP &10 in the original ROM at &02ec.

Does this mean that even though the extra ROMs initialise that the firmware won't be able to find the RSXs in them when they're called?  Has anyone actually tried this on real hardware...?

ROM 3.12 are available at the first page.

Just noticed that, apparently, FW3.1 ruins CATart? Or is it my idea? I was trying to play Subhunter (Sunday morning FTW! Coffee, cigarette, CPC! That's a different 3C from the one our French friends know ;) ) and with it enabled it comes up all fouled up...

MODE 2 may ruin CAT Art using "CAT" command, but not the FW as I know.

Yeah, I thought about it, but the CATart screen is switched to mode 1 anyway... lemme try.


Huh. Yes, indeed it's in mode 1. However, if I switch to mode 1 manually before CATing, it appears fine. Strange?

I think it's because the CAT command not init properly the catalogue column display, when the mode is changed.
If you use |DIR instead, that may work fine again.

Yup, |Dir did the trick. What's the difference?

Sorry for the double post, but thought I'd post here for anyone watching this thread.


My 464 displays RAM as 560KB with FW3.12 and a Symbiface, does anyone know why?


See my other thread for full details: SYMBiFACE edge connector issues (http://www.cpcwiki.eu/forum/amstrad-cpc-hardware/symbiface-edge-connector-issues/15/)

Look Like 64+512-16K ...
May be the Symbiface eat a 16K bank for it's personal use?

Quote from: TotO on 17:02, 13 May 13
Look Like 64+512-16K ...
May be the Symbiface eat a 16K bank for it's personal use?

Or maybe FW3.x does not properly detect RAM  ;D
On a 464, if the memory extension does not force the mreqn signal, the internal ram will be written as well as the extension one.
Some background in this thread 464 and ram extension .... (http://www.cpcwiki.eu/forum/amstrad-cpc-hardware/464-and-ram-extension/) with a memory test that you can run.

Anyone knows how the FW 3.x does the memory detection ? The detection algorithm may not count the 0x4000-0x8000 internal ram as it get corrupted by  the external ram testing.

Tests was done, and it display up to 576K by 16K steps. :)
As I know (but SyX can explain better) some "read/write" was done on each pages from 16K to 576K.

This is the code for the ram check, feel free of taking a look to find the elusive bug:    ; Inicializamos la lista de páginas de ram extendida
    LD   H,D
    LD   L,E
    DEC  L
    LD   C,32 - 1
    LDIR
   
    ; Detectamos cuantas páginas de 16KBs de RAM extendida tenemos disponibles
detect_expansion_ram
    LD   B,>GATE_ARRAY

    ; Marcamos la página 1 de RAM principal
    LD   A,$C0
    OUT  (C),A
    LD   A,$FF
    LD   (RAM_P1),A
   
    ; Marcamos todas las páginas de ram extendida
    LD   HL,RAM_P1          ; HL --> Dirección donde se pagina la RAM extendida
    LD   A,$C4              ; Primera página de RAM extendida
    LD   DE,$FF * 256 + 32  ; Contador para las páginas
.loop_mark_expansion_ram
    OUT  (C),A              ; Hacemos visible la página
    LD   (HL),D             ; Y la marcamos

    ; Pasamos al siguiente banco, asegurándonos que el bit 2 está activo
    INC  A         
    AND  %11111011
    OR   %00000100         

    DEC  E
    JR   NZ,.loop_mark_expansion_ram

    ; Analizamos todas las páginas de ram extendida
    LD   HL,RAM_P1          ; HL --> Dirección donde se pagina la RAM extendida
    LD   A,$FF              ; Marcador que acabamos de escribir
    LD   BC,GATE_ARRAY + $C4 ; Primera página de RAM extendida
    LD   DE,1 * 256 + 32    ; Contador para las páginas
    LD   IX,EXPANSION_PAGES ; Puntero a la lista de páginas de ram
.loop_detect_expansion_pages
    OUT  (C),C
    CP   (HL)
    JR   NZ,.page_used
.page_no_used
    ; Escribimos el contador en la lista y en la página; y los incrementamos
    LD   (HL),D
    LD   (IX + 0),D
    INC  D
    JR   .goto_next_page

.page_used
    ; La marcamos en la lista como página inexistente
    LD   (IX + 0),$00
   
.goto_next_page
    INC  IX
    ; Actualizamos a la siguiente página de RAM extendida
    INC  C
    RES  2,A
    AND  C
    SET  2,A                ; Nos aseguramos que el bit 2 esté activo
    LD   C,A
    LD   A,$FF
    DEC  E
    JR   NZ,.loop_detect_expansion_pages

    ; Calculamos el número de páginas de ram extendida encontradas
    ; Volvemos a situar en $4000 la primera página de RAM principal
    LD   C,$C0
    OUT  (C),C

    ; RAM Pages -> D - 1 / RAM Total -> 64 + (D - 1) * 16
    DEC  D

    CP   (HL)
    JR   Z,.end_fix_expansion_pages
    ; Arreglamos la lista de páginas detectadas (D = 2 y $4000 $01,"SyX")
    ; Ya que en una de las paginaciones se puso la ram principal
    LD   B,32               ; Contador para las páginas
    LD   HL,EXPANSION_PAGES ; Puntero a la lista de páginas de ram
    XOR  A
.loop_fixing_list
    CP   (HL)
    JR   Z,.continue_fixing
    DEC  (HL)
.continue_fixing
    INC  HL
    DJNZ .loop_fixing_list
    DEC  D
.end_fix_expansion_pages
    ; Actualizamos el número de páginas (+ 64 KBs de base RAM)
    LD   A,D
    ADD  4
    LD   L,A
   
    ; Y el número de KBs
    XOR  A
    REPT 4
        SLA  L
        RLA
    ENDR

    LD   H,A

Remember that i don't have a symbiface or a ram expansion (neither the LowerRom board or HxC...), because that, at least somebody sends this kind of hardware for testing, i can only use the emulators for checking and i get always 576 KBs in them when use a 512 KBs expansion.

Got it  ;D


    ; Calculamos el número de páginas de ram extendida encontradas
    ; Volvemos a situar en $4000 la primera página de RAM principal
    LD   C,$C0
    OUT  (C),C

    ; RAM Pages -> D - 1 / RAM Total -> 64 + (D - 1) * 16
    DEC  D

==> CP   (HL)
    JR   Z,.end_fix_expansion_pages
    ; Arreglamos la lista de páginas detectadas (D = 2 y $4000 $01,"SyX")
    ; Ya que en una de las paginaciones se puso la ram principal
    LD   B,32               ; Contador para las páginas
    LD   HL,EXPANSION_PAGES ; Puntero a la lista de páginas de ram
    XOR  A
.loop_fixing_list
    CP   (HL)
    JR   Z,.continue_fixing
    DEC  (HL)
.continue_fixing
    INC  HL
    DJNZ .loop_fixing_list
    DEC  D
.end_fix_expansion_pages
    ; Actualizamos el número de páginas (+ 64 KBs de base RAM)
    LD   A,D
    ADD  4
    LD   L,A
   
    ; Y el número de KBs
    XOR  A
    REPT 4
        SLA  L
        RLA
    ENDR

    LD   H,A

The CP (HL) will always follow the  NZ  branch on a 464 with a extension that does not drive mreq.  The content of the base ram will match the content of the last extension block writen, not the FF marker.
You end up by decrementing D once more. D=31 instead of 32 => (31+4)*16= 560k
You can check that behaviour on emulator by changing the base ram marker for something different than 0xff.

If you want to properly fix the memory check, you should verify that the base ram is not corrupted when you write to the extension. If ram is corrupted, do not count the block as valid.

If you want to detect a 464 with  a non compatible extension, you may check that write to extension block corrupt the base ram, but write to base ram does not corrupt the extension ram.

Anyway, just have the confirmation that the symbiface ram extension does not work on 464.

Quote from: gerald on 09:58, 14 May 13
The CP (HL) will always follow the  NZ  branch on a 464 with a extension that does not drive mreq.  The content of the base ram will match the content of the last extension block writen, not the FF marker.
You end up by decrementing D once more. D=31 instead of 32 => (31+4)*16= 560k
You can check that behaviour on emulator by changing the base ram marker for something different than 0xff.

Good work, that is impressive  :)

Great analysis :)

Hello All,

I am still using a 'Bryce' LowerROM board with MegaFlash and have been running 'Custom' Firmware 3.1 on it .
I recently thought it was about time to upgrade to the latest 'Custom' firmware as I knew that there had been updates.

I did a lot of searching and only found minimal bits of information regarding the 'Custom' firmware and nothing really
that gave a good indication of the latest version.

I finally found a post that mentioned FW 3.15 and then eventually found my way to the 'CentPourCent [dot net]' website
and downloaded the DSK image from the X-Mem page, then extracted the FW 3.15 ROMs etc, etc.

Is there a thread or website or anything relating to the 'Custom' firmware as it sort of seems a bit hidden (unless
you are using an X-mem).

From my quick testing, FW 3.15 is working perfectly with the Lower Rom & MegaFlash...Due to the fact I could only find
it on the X-mem page I was unsure if it was being specifically adapted for that.

Cheers,
Shane

You are right, the FW3.15 (LOWER) and its expansion (ROM 1) are not listed out of the X-MEM floppy disc.
Yes, they should work with the LowerROM and the Megaflash too.

The main FW315EXP.ROM features are:
- |FLASH allow to flash the ROM from the BASIC
- |HELP list the ROM content
- |HELP,<nb> display the ROM <nb> RSXs
- |C RAM Drive (0K, 256K, 448K)
- Remove CTRL+key new shortcuts for a better compatibility

Here the last files.  8)

Thanks TotO for the very quick reply and attached file.

I have just updated the ROM List on the Wiki with the file you provided as it only had the 3.12 file previously.

ROM List - CPCWiki (http://www.cpcwiki.eu/index.php/ROM_List)


Cheers,
Shane

Thank you for the wiki update. I will not forget for the next time!  8)
(for information, I got two lower boards that I no more use... Need an EPROM flasher to update them)

Quote from: TotO on 23:21, 23 December 14
Thank you for the wiki update. I will not forget for the next time!  8)
(for information, I got two lower boards that I no more use... Need an EPROM flasher to update them)

Really, How big are they, and woudl you mind selling one to me? I was hoping a small board lower rom flash card would be made to bring the Symbiface up to the same level as the x-mem, but as I have a programmer and about 200 x 27c128 and a similar number of 27c256 chips here having to programm a few is no biggy LOL.




Let me know what you want for one, and wwe may be able to do some business ;)

Quote from: TotO on 23:21, 23 December 14
Thank you for the wiki update. I will not forget for the next time!  8)
(for information, I got two lower boards that I no more use... Need an EPROM flasher to update them)

When I designed the LowerROM, there wasn't as much activity in ROM Firmware "hacking" as there is now. I didn't envisage so many OSs, so making it writable wasn't a priority. Maybe it was the hardware that motivated the firmware hacking?

Bryce.

Gesendet von meinem Motorola DynaTEC 8000X mit Tapatalk 2.

Hi TotO, I would also be interested in one of your Lower ROM boards.

I am planning to order an X-Mass & X-Mem, so maybe it could be included in the one payment (and also the one postage cost).

Also what I have done with my lower ROM board is replace the UV EPROM with a Winbond W27C512 EEPROM.
I have a cheap UV eraser, but it is so much easier/quicker simply reprogramming when required and not having to go through
a 10 minute erase.

cheers,
Shane

Thanks for updating the wiki entry, @00WReX (http://www.cpcwiki.eu/forum/index.php?action=profile;u=518) !


@Bryce (http://www.cpcwiki.eu/forum/index.php?action=profile;u=225) : time for v2? ;)

The x-mem do it.

Quote from: Gryzor on 19:19, 24 December 14
Thanks for updating the wiki entry, @00WReX (http://www.cpcwiki.eu/forum/index.php?action=profile;u=518) !


@Bryce (http://www.cpcwiki.eu/forum/index.php?action=profile;u=225) : time for v2? ;)

As TotO says. No point really, it's already covered.

Bryce.

Quote from: Bryce on 00:09, 24 December 14
When I designed the LowerROM, there wasn't as much activity in ROM Firmware "hacking" as there is now. I didn't envisage so many OSs, so making it writable wasn't a priority. Maybe it was the hardware that motivated the firmware hacking?

Absolutely!  :)  As soon as there is new hardware people will use it. But of course nobody writes software for non existing hardware.  :)  The LowerROM was the needed breakthrough to show new ways.  :)

Bringing up an old thread here


I've recently acquired a CPC6128 again but find some information on the Wiki/Forums lost or missing. Top of this thread attaches 3.12 and 3.15 in posts following?


Dukes M4 board talks about FW316 but no references to it
https://www.spinpoint.org/cpc/m4info.txt (https://www.spinpoint.org/cpc/m4info.txt)


Forum post here has the FW316 version for people (like me) who have been trying to find it
https://www.cpcwiki.eu/forum/applications/(m4board-xmem)-can-m4-rom-be-installed-on-the-xmem/msg198015/#msg198015 (https://www.cpcwiki.eu/forum/applications/(m4board-xmem)-can-m4-rom-be-installed-on-the-xmem/msg198015/#msg198015)

Edit: FW316UK32.ROM displays as FW3.16-EN in the top banner. Version ID at 0x25A7 needs to be updated from '16' to '32''

cheers
Matt

The FirmWare 3.1x was designed for the X-MEM and compatible boards.

- FW312.ROM is deprecated
- FW315.ROM is for X-MEM (optional RAM Drive if extra memory available)
- FW316.ROM if sor X-MEM + X-MASS (no RAM Drive)

About the filenames:
UK, FR, ES is the keyboard keymap.
16, 32 is the number of ROM initialised at boot.

In example, FW315UK32.ROM is Firmware 3.15 for UK QWERTY keyboards and init 32 ROM (512K) during the boot.
I have updated my Internet hosting last week and I have to upload again the files soon, but the address is: http://centpourcent.net (http://centpourcent.net)

By the way, all the files are available at www.cpc-power.com (http://www.cpc-power.com)

Thank you.

Thanks for the quick reply and explanation. I'm running what hardware I can get hold of at the moment

The FW316 software was mentioned on the M4 page, but google only came up with results on these forums
http://www.spinpoint.org/cpc/m4info.txt (http://www.spinpoint.org/cpc/m4info.txt)

So it works with initialising all the 32 ROM files on my machine using the M4. I had read on another thread here, it was better to run this firmware than use the booster ROM

I managed to get this one working on the M4 board with a revaldinhos 1024MB RAM module (detected as 512MB + 64MB in FW316, but full memory detected in other memory test software)

https://github.com/revaldinho/cpc_ram_expansion/wiki/'Old-School'-CPC6128-512KB-and-1MB-RAM-Expansion-Cards
(https://github.com/revaldinho/cpc_ram_expansion/wiki/'Old-School'-CPC6128-512KB-and-1MB-RAM-Expansion-Cards)
One interesting quirk I found was that Sweevos world would start in Mode 2. That game seems to reset and reinitialise the ROMs I think.

Apart from that all seems to work fine

In fact, using this Firmware version allow to not waste a slot with a "booster ROM".
Next the commodity to have the CRTC and Memory (up to 512K standard port) displayed in MODE 2.
On FW316 you can press the "1" KEY at boot to start in MODE 1 if required for your games.

Quote from: TotO on 11:23, 08 March 21
I have updated my Internet hosting last week and I have to upload again the files soon, but the address is: http://centpourcent.net (http://centpourcent.net)

X-MASS and X-MEM links seem to be broken.

Yes, I will have to upload again the files since I have changed the website hosting but you can found them at cpc-power for waiting. Thank you. :)