Would be a fun surprise if the 386 had its own Halt and Catch Fire mode.
https://www.rcollins.org/ddj/Jan97/Jan97.html
>On the standard Intel 80386 DX, asserting the undocumented pin at location B6 will cause the microprocessor to halt emulation and enter ICE mode.
[this is written from an ICE perspective - for "emulation", read "normal operation"]
This mode was introduced in the 80286, but I don't think the pins were exposed except in the special bond-out variant for ICE, and maybe early samples. You can trigger it in software (opcode 0F 04 on the 286, or by enabling a bit in DR7 on the 386), but then the processor disconnects from the bus and you have to reset it.
On the 286, you can get it to dump some otherwise hidden internal state, by using a prefix that no longer exists on 386s: https://rep-lodsb.mataroa.blog/blog/intel-286-secrets-ice-mo...
But the byte enable pins also implicitly communicate size, which would otherwise require another two pins. So this byte enable scheme breaks even (at least for chips with 16bit or 32bit buses).
The main goal is simplify the design of the motherboard.
<input name="layer" type="radio" onclick="show('https://static.righto.com/images/386-package/layer0.jpg')" id="layer1">
<label for="layer1">Pins</label>
then it would be possible to click the label name (i.e. Pins, I/O Vcc, etc.) instead of having to click the small radio circles.It's a small thing, but I think it's a lot more fun/easy/fast to click the different label names rather than the circles. It's truly a small nit - just in case it's an easy fix for you. Cheers!
(just to make sure: you need to add a unique "id" attribute for each "input", and then make a <label> tag for each label referencing that id in the "for")
Nesting the <input> inside the <label> is simpler. Then you don't need the id and for attributes. I think it avoids an unclickable space between them too.
For example, I know that thermal samples for the Pentium 5-era Xeon (Jayhawk) were produced, but I'd always wondered Intel went from the dummy to realizing "oh, shit, this is going to be way too hot in the long run."
8MB of DRAM, a 250MB spinning disk hard drive, 5.25 and 3.5 inch floppy bays, removable bios that I had to sort through a tupperware of chips to find the correct unit, some unnamed AGP video card that I had to slot removable chips into as well and a great big 16" CRT.
I think I had to install a special serial card in an ISA slot to use a mouse too.
Do you mean VGA rather than AGP? AGP came much later than the 386 and wouldn’t have been supported by its motherboard chipsets.
I can’t remember if those were available on 386s or started in the 486 era.
Full ISA connector (potentially missing the bit in the middle) and then a further piece? VLB
Shorter than ISA but higher density? AGP (it's even a bit shorter than PCI)
Was it at least a Pentium? Can't be AGP otherwise.
Going to ignore PCI-X, PCIE and obscure AGP variants
Anyways.. this is what I really like about kens work.. the accidental discovery of beautiful structures while trying to answer abstract questions. Thanks for doing all this!
and Cyrix 486DLC hijacks 7 of those :)
A20M# (F13) - when supported by motherboard you can L1 cache whole ram instead of leaving first 64KB uncached
FLUSH# (E13) - when supported by motherboard you dont have to use hacks and flush L1 on every DMA access. Hacks (BARB mode) seemed clever at the time until everyone had a Sound Blaster DMAing audio constantly invalidating cache while gaming.
RPLSET (C6) RPLVAl (C7)- L1 cache status debug outputs
SUSP# (A4) SUSPA# (B4)- suspend support, wakes on INT and NMI. Good for laptops.
>The surprising thing is that one of the No Connect pads does have the bond wire in place
Somehow Cyrix picked this particular pin (B12) for KEN# input (enable L1 cache) :O
>From the circuitry on the die, this pin appears to be an output
Meaning the _one_ NC pin Intel CPU actually wires, an output no less, Cyrix demands driven low to enable cache.
Pedantic note: I think "quadratically" makes more sense here: we're talking about two dimensions.
kens•21h ago
OptionOfT•21h ago
loa_in_•20h ago
kens•20h ago
wkat4242•12h ago
johnklos•20h ago
Since the bond wires are just hanging out in air, does this mean that a chip like this could be ruined by dropping it which might cause the bond wires to move enough to short something?
Thanks for all your hard work!
userbinator•15h ago
generuso•12h ago
This failure mode is quite low on the list among others, but it is something that people did investigate. For example: "Swing Touch Risk Assessment of Bonding Wires in High-Density Package Under Mechanical Shock Condition" https://asmedigitalcollection.asme.org/electronicpackaging/a...
besserwisser•1h ago
imoverclocked•20h ago
kens•19h ago
TZubiri•18h ago
kens•18h ago
bunabhucan•17h ago
rts_cts•16h ago
s1110•17h ago
userbinator•15h ago
danparsonson•14h ago
pyuser583•11h ago
mannycalavera42•2h ago
vodkadin•14h ago
tjwebbnorfolk•9h ago
mavamaarten•5h ago
kkaske•14h ago
s1110•14h ago
I mean I eventually read the article. Sorry for that. But we're at "Hacker News", sporting hackers ethics, aren't we?
inferiorhuman•12h ago
pyuser583•11h ago
wood_spirit•10h ago
drysine•8h ago
red75prime•11h ago
astrange•11h ago
That and financial businesses usually don't operate outside their host country anyway. Though you do want your customers to see their accounts when they're traveling.
pyuser583•11h ago
In all fairness, this isn’t a good use of that technique. But most websites are of no interest outside a handful of countries.
orbital-decay•12h ago
tgv•9h ago
rylando•14h ago
kens•14h ago