Combined VGA / Tube interface board for Atom

[dreamerxb]

And the AtomTube is also running now

[dreamerxb]

Solved the problem with the AtomSid combined with the VGA/TUBE interface board. The problem lies in that I use a swinsid which causes the problem. When using an original, or in my case a ArmSid, the problem is gone.
Why the swinsid is not working well as other SID replacements I don't know.

[hoglet]

Why the swinsid is not working well as other SID replacements I don't know.

Did the SwinSID work well without the Combined VGA / Tube board / bypassed 8304?

Or has it always worked badly in your Atom?

What type of 6502 do you have fitted?

Dave

[KenLowe]

Solved the problem with the AtomSid combined with the VGA/TUBE interface board. The problem lies in that I use a swinsid which causes the problem. When using an original, or in my case a ArmSid, the problem is gone.
Why the swinsid is not working well as other SID replacements I don't know.

This, of course, has got me investigating how to integrate SID onto my combo board

This looks like a good starting point: viewtopic.php?t=17572

Hopefully the existing GAL on my board already has all the necessary signals, and a spare output, do the address decoding.

[dreamerxb]

Why the swinsid is not working well as other SID replacements I don't know.

Did the SwinSID work well without the Combined VGA / Tube board / bypassed 8304?

Or has it always worked badly in your Atom?

What type of 6502 do you have fitted?

Dave

No the SwinSid without the Combined VGA/Tube board produces only noise but with the ArmSID it has no problem in this configuration.
The SwinSid with Combined VGA/Tube board produces the music but plays it slow and the pitch is not correct and the music sounds false.
Only when not using PL6/7 for other things, the SwinSid behaves normally using a active speakerset. But I found also when using an external speaker ( not an active speaker) it plays the songs but with a very high tone through the music. The ArmSid has this problem not also the KickSid and the original SID not.
The processor I use in my atom is the Rockwell R6502AP

Erik

[KenLowe]

No the SwinSid without the Combined VGA/Tube board produces only noise.

Only when not using PL6/7 for other things, the SwinSid behaves normally using a active speakerset.

This sounds like a bit of a contradiction?

[dreamerxb]

No the SwinSid without the Combined VGA/Tube board produces only noise.

Only when not using PL6/7 for other things, the SwinSid behaves normally using a active speakerset.

This sounds like a bit of a contradiction?

Your are absolutely right, what I forgot to tell was that IC4 is in it place when not using PL6/7

Erik

[dreamerxb]

Solved the problem with the AtomSid combined with the VGA/TUBE interface board. The problem lies in that I use a swinsid which causes the problem. When using an original, or in my case a ArmSid, the problem is gone.
Why the swinsid is not working well as other SID replacements I don't know.

This, of course, has got me investigating how to integrate SID onto my combo board

This looks like a good starting point: viewtopic.php?t=17572

Hopefully the existing GAL on my board already has all the necessary signals, and a spare output, do the address decoding.

If you want to integrate SID on the VGA board maybe this https://github.com/frntc/SIDKick-pico is an idea ?

Erik

[dreamerxb]

Hey guys,

I found another ( small ) problem. with the combined VGA/Tube interface board in the atom the ramrom loader is not working anymore. I use the Yarrb2 board from Roland. When I start the ramrom loader I get the error 94 line 50
Any suggestion ?

Erik,

[hoglet]

I found another ( small ) problem. with the combined VGA/Tube interface board in the atom the ramrom loader is not working anymore. I use the Yarrb2 board from Roland. When I start the ramrom loader I get the error 94 line 50

I'm not 100% clear what you mean by the "ramrom loader"

Do you mean pressing R within the Atom Software Archive to load a set of ROMs into RAM? Please explain exactly what you are doing so we can try to replicate it.

If you type LIST 50 after the error, what does it show?

Dave

[dreamerxb]

I found another ( small ) problem. with the combined VGA/Tube interface board in the atom the ramrom loader is not working anymore. I use the Yarrb2 board from Roland. When I start the ramrom loader I get the error 94 line 50

I'm not 100% clear what you mean by the "ramrom loader"

Do you mean pressing R within the Atom Software Archive to load a set of ROMs into RAM? Please explain exactly what you are doing so we can try to replicate it.

If you type LIST 50 after the error, what does it show?

Dave

Sorry for not being accurate but yes that's what I mean, pressing R in the Atom Archive to load a set of RoM's into Ram

Erik

[dreamerxb]

I found another ( small ) problem. with the combined VGA/Tube interface board in the atom the ramrom loader is not working anymore. I use the Yarrb2 board from Roland. When I start the ramrom loader I get the error 94 line 50

If you type LIST 50 after the error, what does it show?

50 *RUN TEST

[dreamerxb]

Maybe this is helpful. It looks like that when running the ramrom loader from the archive, it lo losses the Atomcc connection there for it can't load ( *run ) the TEST file.

Erik

[hoglet]

This is a bit of a strange one...

I can't reproduce it - the ROM loading works fine for me.

I can't think why the presence of the VGA / Tube board would break just the ROM loading. Unless the machine is generally unstable.

What happens if you do the following:

Code: Select all

<Press BREAK>
*CWD SYS
*RUN TEST
P. ?#80

What version of the Archive are you using?

Does loading other programs from the Atom Software Archive work?

Maybe Ken could try this as well?

Dave

[hoglet]

Can you post a photo of the inside of your Atom?

[dreamerxb]

This is a bit of a strange one...

I can't reproduce it - the ROM loading works fine for me.

I can't think why the presence of the VGA / Tube board would break just the ROM loading. Unless the machine is generally unstable.

What happens if you do the following:

Code: Select all

<Press BREAK>
*CWD SYS
*RUN TEST
P. ?#80

What version of the Archive are you using?

Does loading other programs from the Atom Software Archive work?

Maybe Ken could try this as well?

Dave

What version of the Archive are you using?
V12.00
Does loading other programs from the Atom Software Archive work?
So far all programs are function, also the tube is function
As soon I do the command *RUN TEST it losses the ATOMMC
P. ?#80 gives a 3

[KenLowe]

What happens if you do the following:

Code: Select all

<Press BREAK>
*CWD SYS
*RUN TEST
P. ?#80

This is with version 12.04 of the ASA:

*RUN TEST

[dreamerxb]

Can you post a photo of the inside of your Atom?

[dreamerxb]

What happens if you do the following:

Code: Select all

<Press BREAK>
*CWD SYS
*RUN TEST
P. ?#80

This is with version 12.04 of the ASA:

capture6.png

Same results as KEN except I get a error 94 on *RUN TEST because of lossing ATOMMC

[dreamerxb]

I removed the Combined VGA/Tube interface board from the Atom and the problems stil exists. So it is not the problem with the Combined VGA/Tube interface board.

Is my Yarrb2 board eventuly defect ?

[Multiwizard]

Looks good Erik...

[hoglet]

Is my Yarrb2 board eventuly defect ?

I doubt it's defective.

The purpose of the TEST program is to try to identify what type of Ram/Rom board is fitted. It's possible there is an incompatibility with YARRBv2 and this program. But I would have thought that Roland would have discovered this. I don't have a YARRBv2, just a YARRBv1, so I can't easily debug this.

Do you thing you could try the following test:

Code: Select all

<Press BREAK>
*HELP
*CWD SYS
*LOAD TEST
PRINT &?#80,&?#BFFE'
LINK #2800
PRINT &?#80,&?#BFFE'

Then take a screen shot, which should look something like:

@Roland, are you following this thread?

Dave

[hoglet]

@Roland, are you following this thread?

I'm not sure what's going on here. I've compared the CPLDs from YARRBv1 and YARRBv2 and can't see any significant differences.

For reference, here's the source of TEST:

Code: Select all

   10 DIMLL10
   20 FOR I=0 TO 1
   30 P=#2800
   40[
   50 LDA @#00
   60 STA #80
   70 LDA #BFFE
   80 EOR @#80
   90 STA #BFFE
  100 CMP #BFFE
  110 PHP
  120 EOR @#80
  130 STA #BFFE
  140 PLP
  150 BEQ LL1
  155 AND @#F1
  160 CMP @#B1
  170 BEQ LL0
  190 LDA @#01
  200 STA #80
  210:LL0
  220 RTS
  230:LL1
  240 AND @#10
  250 BNE LL4
  260 LDA #BFFE
  270 LDX @#5A
  280 STX #4000
  290 EOR @#01
  300 STA #BFFE
  310 LDX @#A5
  320 STX #4000
  330 EOR @#01
  340 STA #BFFE
  350 LDX #4000
  360 CPX @#5A
  370 BEQ LL2
  380 CPX @#A5
  390 BEQ LL3
  400 LDA @#FF
  410 STA #80
  420 RTS
  430:LL2
  440 LDA @#02
  450 STA #80
  460 RTS
  470:LL3
  480 LDA @#03
  490 STA #80
  500 RTS
  510:LL4
  520 LDA #BFFE
  530 TAX
  540 AND @#FB
  550 STA #BFFE
  560 LDA #A00
  570 EOR @#FF
  580 STA #A00
  590 CMP #A00
  600 PHP
  610 EOR @#FF
  620 STA #A00
  630 STX #BFFE
  640 PLP
  650 BEQ LL2
  660 BNE LL3
  670]
  680 NEXT
  690 LINK #2800
  700 P.&?#80'
  710 END

The purpose of this is to identify the type of RomRam board fitted. The return values are:
- 00 = No RAM ROM board detected
- 01 = Unsupported RAM ROM board (e.g. Phill's which doesn't support soft-loading of ROMs)
- 02 = Atom2015
- 03 = YARRB
- FF = Something unexpected occurred

Although it does modify BFFE, it's careful to always restore the original value. What I suspect is happening is a read of BFFE is getiing corrupted, and the value written back then has bit 2 cleared when it should be set, which switches the ROM set to one that doesn't include AtoMMC.

Erik, do run the tests suggested in the previous post, as they may help narrow down the issue.

Dave

[dreamerxb]

@Roland, are you following this thread?

I'm not sure what's going on here. I've compared the CPLDs from YARRBv1 and YARRBv2 and can't see any significant differences.

For reference, here's the source of TEST:

Code: Select all

   10 DIMLL10
   20 FOR I=0 TO 1
   30 P=#2800
   40[
   50 LDA @#00
   60 STA #80
   70 LDA #BFFE
   80 EOR @#80
   90 STA #BFFE
  100 CMP #BFFE
  110 PHP
  120 EOR @#80
  130 STA #BFFE
  140 PLP
  150 BEQ LL1
  155 AND @#F1
  160 CMP @#B1
  170 BEQ LL0
  190 LDA @#01
  200 STA #80
  210:LL0
  220 RTS
  230:LL1
  240 AND @#10
  250 BNE LL4
  260 LDA #BFFE
  270 LDX @#5A
  280 STX #4000
  290 EOR @#01
  300 STA #BFFE
  310 LDX @#A5
  320 STX #4000
  330 EOR @#01
  340 STA #BFFE
  350 LDX #4000
  360 CPX @#5A
  370 BEQ LL2
  380 CPX @#A5
  390 BEQ LL3
  400 LDA @#FF
  410 STA #80
  420 RTS
  430:LL2
  440 LDA @#02
  450 STA #80
  460 RTS
  470:LL3
  480 LDA @#03
  490 STA #80
  500 RTS
  510:LL4
  520 LDA #BFFE
  530 TAX
  540 AND @#FB
  550 STA #BFFE
  560 LDA #A00
  570 EOR @#FF
  580 STA #A00
  590 CMP #A00
  600 PHP
  610 EOR @#FF
  620 STA #A00
  630 STX #BFFE
  640 PLP
  650 BEQ LL2
  660 BNE LL3
  670]
  680 NEXT
  690 LINK #2800
  700 P.&?#80'
  710 END

The purpose of this is to identify the type of RomRam board fitted. The return values are:
- 00 = No RAM ROM board detected
- 01 = Unsupported RAM ROM board (e.g. Phill's which doesn't support soft-loading of ROMs)
- 02 = Atom2015
- 03 = YARRB
- FF = Something unexpected occurred

Although it does modify BFFE, it's careful to always restore the original value. What I suspect is happening is a read of BFFE is getiing corrupted, and the value written back then has bit 2 cleared when it should be set, which switches the ROM set to one that doesn't include AtoMMC.

Erik, do run the tests suggested in the previous post, as they may help narrow down the issue.

Dave

Hello Dave, here is the result of the previous post:

[hoglet]

Hello Dave, here is the result of the previous post:

That actually seems to be working as expected:
- no crash/error
- BFFE not corrupted in any way
- returns 03 to indicate YARRB detected

It would be useful to know after doing that test whether AtoMMC is broken in some way.

I'm somewhat at a loss as to what's going on, unless the failure is rather intermittent, or it only occurs with *RUN and not *LOAD/LINK.

Dave

[hoglet]

This is with version 12.04 of the ASA:

Do you also have a YARRBv2 fitted? (the one with the XC95288)

Dave

[KenLowe]

My test was actually with a YARBB that has a 44 pin XC9572. I'm not sure if that's a YARRB1??? I've just dug out my other Atom that does have the XC95288 based YARRB2 and done the same test on that one, and I get exactly the same result.

Also, if I press 'R' when on the ASA Menu page I see a bunch of ROMS loading, and then the machine reboots. I don't get any errors. This happens on both of my Atoms.

[dreamerxb]

Hello Dave, here is the result of the previous post:

That actually seems to be working as expected:
- no crash/error
- BFFE not corrupted in any way
- returns 03 to indicate YARRB detected

It would be useful to know after doing that test whether AtoMMC is broken in some way.

I'm somewhat at a loss as to what's going on, unless the failure is rather intermittent, or it only occurs with *RUN and not *LOAD/LINK.

Dave

Hello Dave, the AtoMMC is also broken when using *LOAD/LINK in the previous post.

Erik

[dreamerxb]

This is with version 12.04 of the ASA:

Do you also have a YARRBv2 fitted? (the one with the XC95288)

Dave

Yes I have that one

Erik

[hoglet]

Hello Dave, the AtoMMC is also broken when using *LOAD/LINK in the previous post.

It least it's consistent...

What errors do you then get if you do:
- *HELP
- *CAT
- *LOAD TEST

Does ejecting / re-inserting the SD Card fix it?

Dave