exxos's Atari, Amiga & retro forum

We are sorry that your order is incomplete... This is due to a stock discrepancy in our Distribution Centre.

The missing items... ​​​​​​have been placed on back order and will be despatched to you as soon as they become available. Estimated date of delivery, approx 8 weeks.

:|

BW

Ah man that sux. Always feking something with JLC :cussing: its all why I gave up with getting the birdseed motherboards done as just had enough in the end :roll:

exxos wrote: 23 Aug 2021 23:42 Ah man that sux. Always feking something with JLC :cussing: its all why I gave up with getting the birdseed motherboards done as just had enough in the end :roll:

Ah, I forgot to say: that was Farnell. My 2x 32MB memory.

So I ordered the more expensive one up (from Micon as I've seen that works with the TF boards). Now it's...

We regret to inform you that your consignment may be subject to a delay due to a Customs issue beyond our control and which we are working hard with the appropriate parties to resolve.

!!

BW

First signs in the wild of the DFB1r4 in bring-up configuration (no RAM, flash or bus transceivers).

Wish me luck! :?

BW

Looking good so far... fingers crossed for some positive progress with this!
:thumbup: :goodpost: :coolpics:

Hmm. Failing at (almost) first hurdle.

Bus Arb seems to be working, the processor starts trying to read 0x000000 from the motherboard, but never gets a DTACK. Instead BERR fires around 100 cycles later.

What could cause that?

If the cycle were not being seen by COMBEL, we'd not get a BERR, would we? I suppose a stuck address line that just happened to fall in a region without peripherals (is that possible) could do it? Scoping all the address lines does suggest they're correctly set to all zeros.

As the processor gets BERR on this first read, nothing else happens afterwards.

I've gone through the firmware and really cut it down (making sure I'm not driving XDTACK high or something). The onboard processor boots happily in DISABLE mode.

A chin-scratcher.

BW

Where are you testing the address zero at , on the booster board ? I'd assume you have a bad connection and combel is seeking some other ( wrong ) address and does not issue dtack, I'd assume one of the higher address lines is broken between the booster and motherboard.

exxos wrote: 11 Sep 2021 23:27 Where are you testing the address zero at , on the booster board ? I'd assume you have a bad connection and combel is seeking some other ( wrong ) address and does not issue dtack, I'd assume one of the higher address lines is broken between the booster and motherboard.

I tested A1-A15 on the cartridge port, but, yeah, I could only probe A16-23 on the pin on my board.

You're probably right, though. Must be one of those top lines. My mobo has had connection problems on the expansion port before & have had to reseat cards a few times often. No joy with reseating this one, though, so I might get some fine sandpaper on the terminals.

I should probably invest in some deoxit as my WD40 contact cleaner doesn't do much, it seems.

BW

Maybe try resoldering the port ? I've had 100s of ram boards in and out of my falcon , had to resolder it a while back. No problems since.

exxos wrote: 12 Sep 2021 14:12 Maybe try resoldering the port ? I've had 100s of ram boards in and out of my falcon , had to resolder it a while back. No problems since.

Yes. Good idea. It's overdue, to be honest.

I have to have the board out of the case to fit the spanky new fan the Exxos store fairy delivered to me anyway. :D

BW