USIfAC II, technical problems & support [MERGED with Plus-related posts from original thread]

[Cribbyrhymes]

@ikonsgr thank you for the response. I'm happy to persevere, it's a fantastic bit of hardware you have designed and I want to get it up and running. I think it is something to do with my power supply/Mainboard it's just trying to narrow down the fault which can be tricky as you have highlighted. I'll give the things you mentioned a go and let the chat know how I get on

[Cribbyrhymes]

@ikonsgr it's working! 
I extracted the files onto the usb and it is working perfectly! No keyboard freezes at all, I've spent the last hour test loading games from the usb and they are all running perfectly. I'm a happy man. Thank you for all your help and patience. Must have been an issue with my ROM chip then.

[darthnuno]

Hi,
I'm using the latest USIfAC II on a Schneider CPC464
I have obsiously an issue to switch to the 6128 mode.

Here the status, right after a power on of the computer ->




and the printscreen, right after a |6128 command ->




As you can see, some changes on the screen, but it still written "464 mode" :-(
In addition I'm trying some games (I suspect being 6128 versions), and got the not "enough memory" error message :-(
So, how to be sure to be in a "6128" mode? Thx in advance for support. 

[ikonsgr]

@darthnuno the "464 Mode" message means that board works for CPC 464, regardless of being in the 512k ram mode or the dual ram/rom mode.
In dual mode you can run almost all software for cpc, as your 464 practically is converted to a CPC 6128 with 256k ram.
About the "not enough memory" error message, can you be more specific? What game you tried? Was it a dsk image or files? Did you use t he file manager or commands from basic?

[darthnuno]

@darthnuno the "464 Mode" message means that board works for CPC 464, regardless of being in the 512k ram mode or the dual ram/rom mode.
In dual mode you can run almost all software for cpc, as your 464 practically is converted to a CPC 6128 with 256k ram.
About the "not enough memory" error message, can you be more specific? What game you tried? Was it a dsk image or files? Did you use t he file manager or commands from basic?

Thanks for you reply.
Well, I found how to change the display "464 mode" <> "6128 mode" on screen : by using the command ¦sm,1 y<> ¦sm,2
But If I correctly understand you, it's better to stay in "464" if I'm on a 464 hardware? Well, now I'm not sure about the purpose of the command ¦sm? Expect changing the display 464<>6128 and the basic mode version 1.0 <> 1.1 ?
I'm trying to run the game "Skyfox" (.dsk)

Of course, it's maybe the .dsk image itself that has an issue? Whatever the 'mode', it ends up by the memory full message...
A good test for me would be to try an exclusive 6128 game on my 464? Do you have the name of a game or program for me to test ?

[ikonsgr]

Well, I found how to change the display "464 mode" <> "6128 mode" on screen : by using the command ¦sm,1 y<> ¦sm,2
But If I correctly understand you, it's better to stay in "464" if I'm on a 464 hardware? Well, now I'm not sure about the purpose of the command ¦sm? Expect changing the display 464<>6128 and the basic mode version 1.0 <> 1.1 ?
I'm trying to run the game "Skyfox" (.dsk)

Of course, it's maybe the .dsk image itself that has an issue? Whatever the 'mode', it ends up by the memory full message...
A good test for me would be to try an exclusive 6128 game on my 464? Do you have the name of a game or program for me to test ?

when you have 464 you use 464 mode, otherwise ram expansion will not work (you will have only the internal 64k ram). I'll see this game tomorrow, but most probable the line 50 with memory 42619 is designed for specific CPC, probably cpc 464, so if you use the dual mode which converts 464 to 6128 will give this error. Try to replace line 50 with: 50 MEMORY HIMEM and see if that works. here you can find a collection of good and classic games: https://www.dropbox.com/scl/fo/51ramuvw843qigsuhbvrl/AFG-ENzMtNg_0hT_HoxdYt0?rlkey=cc5t9nhmkf1qla7ou5h4o3geo&dl=0

[ikonsgr]

@darthnuno ok, try the version i attached. It's in files form, not dsk image, for ultra fast loading, and works on both 512K Ram mode and dual RAM/ROM mode too.
The BAS loader has some differences with the one you tried, most notably the "memory 42619" line doesn't exist.

[darthnuno]

@darthnuno ok, try the version i attached. It's in files form, not dsk image, for ultra fast loading, and works on both 512K Ram mode and dual RAM/ROM mode too.
The BAS loader has some differences with the one you tried, most notably the "memory 42619" line doesn't exist.

I tried your version and ... it works, thanks :-)

However, I think I have a good candidate to check the 6128 'emulation' on a 464. It's an homebrew called Baba's Palace.

Whatever the mode/setup/config chosen on my USIfAC, it always end up by this message when trying to launch the game :



Here's the rom :

Baba's Palace.dsk

I don't know how that game detects if it runs on a real 6128 ? Could you run this on a real 464?

[ikonsgr]

I tried your version and ... it works, thanks :-)

However, I think I have a good candidate to check the 6128 'emulation' on a 464. It's an homebrew called Baba's Palace.

Whatever the mode/setup/config chosen on my USIfAC, it always end up by this message when trying to launch the game :



Here's the rom :

Baba's Palace.dsk

I don't know how that game detects if it runs on a real 6128 ? Could you run this on a real 464?

First, you should set basic operation mode to 464 by givning |SM,2. Then you give |6128 to swap in dual ram/rom mode, that converts CPC 464 to CPC 6128.
Btw, this game is in the collection i mentioned, in direct files form and works on boot 512k ram mode too.

[pollito]

Hi all.

My ULIfAC v2 board has stopped working, and I'm not sure what has happened, or how to get it up and running again.

The issue started suddenly when I mounted a DSK image, and tried to run DISC.BAS. I can't remember the exact error, but after seeing it, I entered the CAT command, and it showed corrupted characters.

I powered off the CPC and, believing it was a faulty USB stick, formatted another one. I then copied the files onto it from a recent backup.

Unfortunately, now when I power on the CPC, it just shows the standard boot screen, with no ULIfAC ROM message.


Things I have tried:

1. Checked the new USB stick, and it is formatted to FAT32.

2. Tried again with the original USB stick.

3. Tried a third USB stick (formatted FAT32).

4. Tried on another CPC 464.

5. Checked the switch on the ULIfAC was set to 464 (not 6128).

6. Tried on a CPC 6128 (with the switch set to 6128).

7. Tried three different known-good edge connector to M4 cables.

8. Tried the ULIfAC connected in both backplanes, and directly connected to the CPCs.

9. Re-formatted one of my USB sticks (to FAT32), and only copied the following files onto the root of directory (from CPC464_TO_6128.zip):

Code Select Expand

AMSDOS.ROM
BASIC11.ROM
CONFIG.TXT
OS_6128.ROM

Possible useful information:

• When the CPC is first powered on, the USB light flashes once.
• The Pause button still works.
• Pressing the DskSwap, RAM/ROM or Reset button causes the CPC to reset.
• The CPC is being powered from a 5V 4A power supply.
• The ULIfAC is being powered internally, and the jumper InternalPower is shorted.

Any help would be appreciated. I have only had the ULIfAC for just over a year.

[eto]

I finally used a ULIFAC (3b) with a 464 that I have here for repair.

Seems I don't have any luck with 464s and any of the UxIFAC devices.

The 464 is stuck during boot and I have to reset the computer. At least a Reset always solves it. But then I can't run the direct load games. I start |FM and navigate into the folders and if I try to run a game I usually get a blank screen. Sometimes an "external command" error message. Sometimes also a BASIC error message (different reasons). In the last case I sometimes can start the game from BASIC by typing RUN"gamename - which (again) works. Overall the direct load feature is completely unusable.

Is that a known behaviour? Or something that can be resolved?



Also: what's the current firmware for the old board? The "3b final" or is 3c recommended? How can I upgrade it with a PICKIT programmer - I could only find the new way in the manual but I don't have that adapter and I could not find the documentation how to use the PICKIT with the ULIFAC 2 - I guess that works differently than the ULIFAC as it has 2 PICs?

[pollito]

Hi all.

My ULIfAC v2 board has stopped working, and I'm not sure what has happened, or how to get it up and running again.

The issue started suddenly when I mounted a DSK image, and tried to run DISC.BAS. I can't remember the exact error, but after seeing it, I entered the CAT command, and it showed corrupted characters.

I powered off the CPC and, believing it was a faulty USB stick, formatted another one. I then copied the files onto it from a recent backup.

Unfortunately, now when I power on the CPC, it just shows the standard boot screen, with no ULIfAC ROM message.


Things I have tried:

1. Checked the new USB stick, and it is formatted to FAT32.

2. Tried again with the original USB stick.

3. Tried a third USB stick (formatted FAT32).

4. Tried on another CPC 464.

5. Checked the switch on the ULIfAC was set to 464 (not 6128).

6. Tried on a CPC 6128 (with the switch set to 6128).

7. Tried three different known-good edge connector to M4 cables.

8. Tried the ULIfAC connected in both backplanes, and directly connected to the CPCs.

9. Re-formatted one of my USB sticks (to FAT32), and only copied the following files onto the root of directory (from CPC464_TO_6128.zip):

Code Select Expand

AMSDOS.ROM
BASIC11.ROM
CONFIG.TXT
OS_6128.ROM

Possible useful information:

• When the CPC is first powered on, the USB light flashes once.
• The Pause button still works.
• Pressing the DskSwap, RAM/ROM or Reset button causes the CPC to reset.
• The CPC is being powered from a 5V 4A power supply.
• The ULIfAC is being powered internally, and the jumper InternalPower is shorted.

Any help would be appreciated. I have only had the ULIfAC for just over a year.

@ikonsgr any thoughts on this? I only used it for 6 months last year on my 464 before my M4 card arrived. Then I started using the ULIfAC again around two months ago when I got my 6128. I don't believe that the ULIfAC should fail after 8 months of use. Maybe it hasn't, but I would appreciate some advice troubleshooting it please. Let me know if it's easier to do this via email.

[ikonsgr]

@ikonsgr any thoughts on this? I only used it for 6 months last year on my 464 before my M4 card arrived. Then I started using the ULIfAC again around two months ago when I got my 6128. I don't believe that the ULIfAC should fail after 8 months of use. Maybe it hasn't, but I would appreciate some advice troubleshooting it please. Let me know if it's easier to do this via email.

Did you try giving OUT &FBD2,5 to reset board's rom number? In such cases (as error/hung up upon dsk image access) this resolve the problem

@eto, the latest firmware for older ULIfAC boards is 3c, if you have a pickit programmer you should use this hex file: https://www.dropbox.com/scl/fi/s8a1pk0jvbdvby8y9gxbp/ULIFAC_v3C_BOOTLOADER.zip?rlkey=q49dg5t10o67079u2k7p1oahk&dl=0

[pollito]

@ikonsgr any thoughts on this? I only used it for 6 months last year on my 464 before my M4 card arrived. Then I started using the ULIfAC again around two months ago when I got my 6128. I don't believe that the ULIfAC should fail after 8 months of use. Maybe it hasn't, but I would appreciate some advice troubleshooting it please. Let me know if it's easier to do this via email.

Did you try giving OUT &FBD2,5 to reset board's rom number? In such cases (as error/hung up upon dsk image access) this resolve the problem

@eto, the latest firmware for older ULIfAC boards is 3c, if you have a pickit programmer you should use this hex file: https://www.dropbox.com/scl/fi/s8a1pk0jvbdvby8y9gxbp/ULIFAC_v3C_BOOTLOADER.zip?rlkey=q49dg5t10o67079u2k7p1oahk&dl=0

Thank you sooooo much! It worked like a charm! My ULIfAC lives again! I will have a lot of fun this evening playing games on my living room TV tonight, many thanks to you!

Should I also upgrade the firmware for my board? If so, is 3c the latest version for the rev 2 ULIfAC?

[ikonsgr]

Thank you sooooo much! It worked like a charm! My ULIfAC lives again! I will have a lot of fun this evening playing games on my living room TV tonight, many thanks to you!

Glad to be helpful! Next time you could give me a note on email and get a much faster responce ;-)
Btw, the resetting of board's rom number is mentioned in the 1st "troubleshooting advise" post, on this thread too 

Should I also upgrade the firmware for my board? If so, is 3c the latest version for the rev 2 ULIfAC?

Nope, this is the latest firmware for ULIFAC v2/v3 boards.

[pollito]

Glad to be helpful! Next time you could give me a note on email and get a much faster responce ;-)

I didn't want to bother you by email, and thought it would be quicker to get you here anyway. Now I know! 

Btw, the resetting of board's rom number is mentioned in the 1st "troubleshooting advise" post, on this thread too 

Instead, I went into a panic, tried everything I could think of, gathered as much information as I could, loaded up the ULIfAC wiki page, clicked the link to this thread, went to the last page and posted!

Thanks again for the help!

[ikonsgr]

Important update about the "freezing upon booting" issue on some CPC 464:

Finally, after a lot of speculation about the cause of the problem (since i don't have a CPC 464 with a booting issue to investigate it myself),a couple of good retro community members from Croatia (one of which is a proffesional electronics engineer), and with the "help" of a couple of "sticky" CPC 464, found out that the problem can be fixed very easily, by simply soldering an A09-103 9pin 10k network resistor, which acts as pull up resistor on Amstrad's CPC data bus:

You cannot view this attachment.

Of course i've already started to make ULIfAC boards with the added pullup resistors, but you can apply this very easy fix, on any existing ULIfAC board too!
 As for the cause of the issue, it seems that upon cold booting of Amstrad CPC, a specific combination of Z80 CPU and/or 6845 CRT chips that happen to have somewhat weaker sourcing current capabilities, couldn't supply the required 5v for any data bit at high/5v state, resulting in the freezing of Amstrad CPC! Although this issue is rather rare, concerning only a few Amstrad CPC 464, i wanted to share this information, for anyone having this issue, and how to easily fix it! ;-)

[Brocky]

im guessing this fixes the USIfAC II as well? 
.....im going to keep my mouth shut on my thoughts.....

other than im glad its resolved...

[ikonsgr]

im guessing this fixes the USIfAC II as well?
.....im going to keep my mouth shut on my thoughts.....

other than im glad its resolved...

Indeed, although in the case of USIfAC II it would be a bit more difficult to apply the fix, as the pins of PIC mcu port used for connecting to Amstrad's Data Bus,  are not in a row like with ULIfAC, so it might need some discrete 10k resistors (or maybe use two 5pin 10k network resistors), to do it:

You cannot view this attachment.

All pins in red rectangles should be connected to a common 5v pin (Vdd) through 10k resistors.

[GUNHED]

Would you suggest to add that to USIfAC II for the CPC6128 / 6128plus too?
Maybe for reducing noise on the bus? Any other reasons?

Thanks for the update! 

[Brocky]

im guessing this fixes the USIfAC II as well?
.....im going to keep my mouth shut on my thoughts.....

other than im glad its resolved...

Indeed, although in the case of USIfAC II it would be a bit more difficult to apply the fix, as the pins of PIC mcu port used for connecting to Amstrad's Data Bus,  are not in a row like with ULIfAC, so it might need some discrete 10k resistors (or maybe use two 5pin 10k network resistors), to do it:

You cannot view this attachment.

All pins in red rectangles should be connected to a common 5v pin (Vdd) through 10k resistors.

great...thanks

[Brocky]

Would you suggest to add that to USIfAC II for the CPC6128 / 6128plus too?
Maybe for reducing noise on the bus? Any other reasons?

Thanks for the update! 

it really wouldnt hurt.. i cant get it to detect on my 6128 at all (even after giving the out to init) ..hopefully this will fix it..
the data and address lines should really be pulled up to 5v by default..

[ikonsgr]

the data and address lines should really be pulled up to 5v by default..

 I've made more than 700 USifAC II/ULIfAC boards so far, and only a handful of people reported this strange booting problem.
So, obviously this was a rather rare issue, something that is also confirmed by the fact that,  i couldn't investigate and try to fix the problem myself,  simply because, i couldn't reproduce it! Apart from the 5 Amstrad CPC 464/6128 i own, i had the chance to test both boards on numerous CPC 464 and CPC 6128 of others, and "unfortunately" i never encountered such problem! 
 In 2 words: Only a very small percentage of Amstrad cpc really need pullup resistors on data bus, and there was no way to know about it, EXACTLY because it was such rare issue, that i couldn't reproduce it myself no matter what!

[poulette73]

Agree with John 

[zboskovi]

im guessing this fixes the USIfAC II as well?
.....im going to keep my mouth shut on my thoughts.....

other than im glad its resolved...

Yes, I've tested it too and it works...