TDS5000B series no boot after CPU upgrade?

[Fractal]

Hi,

I have this TDS5034B that I'm refurbishing; thought I would give it a little boost with a Core 2 Duo as the factory Celeron D341 goes 100% in FastAcquisition and makes the whole interface quite sluggish.

The mainboard is an Advantech Model AIMB-562VG-00A1E

Depending on the source and date of the documentation, this MB can take up to 2.66 or 2.8Ghz @ 1066 FSB

And so I got a couple of pieces, a, E7300 (2.66G) and E7400 (2.8G, but actually listed in the attached user manual) but none of them seem to work and leave the machine with full fan/black screen

I have an intuition my bios might be too old with the MB datasheets being from 2007, but at the same time both these CPUs released in 2006, same year as the BIOS

I've sent an email to Advantech asking them about it but it seems it's gone straight to the bin lol


Any tips to get it working?

Cheers!

__Yves


Any tips to get it working

[pac1085]

Sorry, don't have a good answer for your specific question, but I would add a comment about a CPU upgrade I did on my TDS5054B.  Between the CPU(went from 2.0 to 2.8 or 3.06, i forget), and replacing the HDD with a fast CF card, it boots into windows too fast now, apparently before the vxworks daugterboard finishes starting the oscilloscope functions, so the tekscope application crashes on startup.  I had to make a little script that pings localhost like 5 times, to add a little delay before starting the tekscope application.

Also, the CPU upgrade didn't help much with the actual TekScope application, since I think that's basically running off that daugher board.

Either way, good luck and I hope you find an answer!

[Ice-Tea]

You mean you have external VGA output but not on the actual screen? You need to enable the internal screen in the bios...

[Fractal]

Sorry, don't have a good answer for your specific question, but I would add a comment about a CPU upgrade I did on my TDS5054B.  Between the CPU(went from 2.0 to 2.8 or 3.06, i forget), and replacing the HDD with a fast CF card, it boots into windows too fast now, apparently before the vxworks daugterboard finishes starting the oscilloscope functions, so the tekscope application crashes on startup.  I had to make a little script that pings localhost like 5 times, to add a little delay before starting the tekscope application.

Also, the CPU upgrade didn't help much with the actual TekScope application, since I think that's basically running off that daugher board.

Either way, good luck and I hope you find an answer!

Hah uncanny; how fast does it boot anyway with these upgrades? The sloww time makes it quite a drag to use and I tend to flick my analog tek most of the time for quick measurements

You mean you have external VGA output but not on the actual screen? You need to enable the internal screen in the bios...

And I don't recall this to be the issue; the bios is unchanged between CPU swaps. With the core 2 duo it gets no beeps, nothing, almost as if the cpu was unrecognized

[calibrationfixture]

Hi Fractal,

Your Power-on Self Test Screen resembles those of later DPO7000 Series. Both have the same MB. DPO7000's use Pentium 4 Processors.

Calibrationfixture

[Fractal]

Hi Mate,

I didn't know the 7000 series had that same mainboard, in that case that seems plausible as it is specified to accept P4 CPUs as well (see the first PDF attached in the first message)

Furthermore, Illya on his xdevs.com article actually seem to have managed a plug and play CPU upgrade with a little slower but identical in every other way  E6600

This MB totally appears capable to run Core 2 Duo CPU, just why won't it run mine within the MB specs :/

[tunk]

It could be that it (945G chipset?) only supports the first generation C2D (i.e. 65nm):
https://www.cpu-upgrade.com/mb-Intel_(chipsets)/945G_Express.html

[pac1085]

Sorry, don't have a good answer for your specific question, but I would add a comment about a CPU upgrade I did on my TDS5054B.  Between the CPU(went from 2.0 to 2.8 or 3.06, i forget), and replacing the HDD with a fast CF card, it boots into windows too fast now, apparently before the vxworks daugterboard finishes starting the oscilloscope functions, so the tekscope application crashes on startup.  I had to make a little script that pings localhost like 5 times, to add a little delay before starting the tekscope application.

Also, the CPU upgrade didn't help much with the actual TekScope application, since I think that's basically running off that daugher board.

Either way, good luck and I hope you find an answer!

Hah uncanny; how fast does it boot anyway with these upgrades? The sloww time makes it quite a drag to use and I tend to flick my analog tek most of the time for quick measurements

You mean you have external VGA output but not on the actual screen? You need to enable the internal screen in the bios...

And I don't recall this to be the issue; the bios is unchanged between CPU swaps. With the core 2 duo it gets no beeps, nothing, almost as if the cpu was unrecognized

It takes 56 seconds to fully boot into a usable state with the tekscope app running and traces displayed.

It looks like its a P4 2.66, 1GB of RAM, and I used a 32 GB CF card (highly recommend upgrading to a CF card, but make sure to get a "Transcend Industrial" grade one, consumer grade CF cards are recognized by the OS as removable media, which causes boot issues). Also, it's running Windows XP...which may make a difference.

[calibrationfixture]

Hi,

Maybe allready common knowledge, see attached File. Page 28 an overview of used MB's in TDS5000B Scopes. First 2 also used in CSA/TDS7000B's. Last 2 Types also used in DPO7000's.


Calibrationfixture

[Vovk_Z]

IDK anything about this board but I would try C2D 4400 or 4500. They are often supported if MB is capable of 1066 MHz bus. But not all 1066 MHz MB support 1066 MHz bus C2D.