Help! I am building a Cyboard II

[salvogendut]

I have started to assemble a Cyboard II (from https://github.com/salafek/cyboard-for-cpc) and I can see in the BOM  that there are two elements R12 and R13 that are marked as 'Jumpers'. Since the images on github have a WS5100 covering that part, does anybody know how should I jumper these? If at all? See my board under contruction with the area marked in red where these jumpers should be



The finished board as it appears in github

[robcfg]

As the value for R12 and R13 is 0 ohm, and they are labeled as "jumper", I thin it means just connect it with a piece of wire.

If you have some resistor legs cut, provided they are long enough, you can solder that piece of metal instead of a cable.

[salvogendut]

I see! Thanks for the heads up!

[Prodatron]

thanks and cool to see more and more of this great hardware!

[d_kef]

As the value for R12 and R13 is 0 ohm, and they are labeled as "jumper", I thin it means just connect it with a piece of wire.

If you have some resistor legs cut, provided they are long enough, you can solder that piece of metal instead of a cable.

That's the way to go indeed!
If you have any more questions just contact me.

Edit: By the way, it's Cyboard not Cyboard II. Unless you add something to the design and make it Cyboard II.😉

d_kef

[salvogendut]

As the value for R12 and R13 is 0 ohm, and they are labeled as "jumper", I thin it means just connect it with a piece of wire.

If you have some resistor legs cut, provided they are long enough, you can solder that piece of metal instead of a cable.

That's the way to go indeed!
If you have any more questions just contact me.

Edit: By the way, it's Cyboard not Cyboard II. Unless you add something to the design and make it Cyboard II.😉

d_kefHey

As the value for R12 and R13 is 0 ohm, and they are labeled as "jumper", I thin it means just connect it with a piece of wire.

If you have some resistor legs cut, provided they are long enough, you can solder that piece of metal instead of a cable.

That's the way to go indeed!
If you have any more questions just contact me.

Edit: By the way, it's Cyboard not Cyboard II. Unless you add something to the design and make it Cyboard II.😉

d_kef

Thank you!!! I will definitely contact you! Also my apologies, it is indeed just a Cyboard! Not sure where that II came from 

[joky]

And please note that the clock must be equipped for a mouse to work on the USB port. I spent a long time looking for a fault that didn't exist, just because the clock wasn't equipped.

[salvogendut]

And please note that the clock must be equipped for a mouse to work on the USB port. I spent a long time looking for a fault that didn't exist, just because the clock wasn't equipped.

Wow thanks for the warning! I could easily loose my marbles on something like that

[d_kef]

And please note that the clock must be equipped for a mouse to work on the USB port. I spent a long time looking for a fault that didn't exist, just because the clock wasn't equipped.

That's a SymbOS "feature". It's just how SymbOS detects the presence of a Symbiface II. 
Every single component of Cyboard works independently of the others.

d_kef

[joky]

Okay, thank you for the explanation.

[Prodatron]

And please note that the clock must be equipped for a mouse to work on the USB port. I spent a long time looking for a fault that didn't exist, just because the clock wasn't equipped.

That's a SymbOS "feature". It's just how SymbOS detects the presence of a Symbiface II.
Every single component of Cyboard works independently of the others.

d_kef

In fact it's a "PlayCity feature". The old auto-detection for the SF2 mouse was independant from the other SF2 components.
Unfortunately the PlayCity is mirroring its ports to a larger range, which also includes the SF2 mouse. Old SymbOS versions use the old detection, but it doesn't work anymore, if a PlayCity is connected as well.

Code Select Expand

if 0
;### OLD DETECTION ROUTINE -> DOESN'T WORK WITH PLAYCITY

;### Detects and initializes device
;### Output    CF=1 device present and initialized
;### Destroyed  AF,BC,DE,HL,IX,IY
ms2det  ld bc,ms2prt
        ld a,100
ms2det1 in d,(c)
        dec a
        jr nz,ms2det1
        in a,(c)
        scf
        ret z
        ccf
        ret
endif



If anyone knows a methode, how to detect the SF2 mouse, when then PlayCity is connected as well, please tell me!

[d_kef]

Unfortunately the PlayCity is mirroring its ports to a larger range, which also includes the SF2 mouse. Old SymbOS versions use the old detection, but it doesn't work anymore, if a PlayCity is connected as well.

But then if you detect the presence of the PlayCity you can completely skip SF2 mouse detection because otherwise you will get garbage as both interfaces are driving the data bus. You can call your (old) detection routine only if the PlayCity is not present.
I mean as I understand it, it's not possible to have them both working. Is it?

d_kef

[Prodatron]

Unfortunately the PlayCity is mirroring its ports to a larger range, which also includes the SF2 mouse. Old SymbOS versions use the old detection, but it doesn't work anymore, if a PlayCity is connected as well.

But then if you detect the presence of the PlayCity you can completely skip SF2 mouse detection because otherwise you will get garbage as both interfaces are driving the data bus. You can call your (old) detection routine only if the PlayCity is not present.
I mean as I understand it, it's not possible to have them both working. Is it?

Good question, that stuff is 10 years ago and I have to check it again, as I forgot it already again haha