VOGONS


4 Beeps No Post

Topic actions

First post, by Dolard

User metadata
Rank Newbie
Rank
Newbie

Hi, I'm new here (first post) so sorry if I do something wrong but I've been having a ton of trouble getting this small old SBC to work over the past few months and I've tried everything I can think of to no avail. Here is a picture of the thing:

The attachment 17640461222762243208748853520189.jpg is no longer available

And below a diagram of the board for easy reference:

The attachment hs4500-62c7de0ed3462647407061.gif is no longer available

Anyways the first thing I did when I received it of course was try and power it on where I initially tried drawing via CN9 (connected through a modern ATX PSU with separate load) but then moved onto using CN20 (I did this through use of an old AT PSU by chopping up and reassembling the P8 and P9 connectors into a custom 4 pin inline connector to acquire -5V) as well. Both of these however did not work and resulted in 1 beep upon power to the board, fan spinning up, and then when the power pins are shorted just 4 short beeps and no post.

After this post code my first reaction was either the RAM had gone or the RTC module had gone so I acquired a custom RTC replacement for the specific RTC module this board had come with (a Dallas DS12C887 RTC module, credit to Necroware for the replacement design). Anyways power on PSU and SBC... Doesn't work, 4 beeps no post.

I then try RAM. I got 2 replacement sticks of DIMM and 2 sticks of SIMM. Replaced the DIMM stick twice and power on PSU and SBC... Doesn't work, 4 beeps no post.
Remove DIMM, put in 2 sticks SIMM (one was not enough and caused indefinite slow beeps and I tried with both 2 sticks configurations), and power on PSU and SBC... Doesn't work, 4 beeps no post. Below are the sticks tested:

The attachment 17640484320362434797804186706909.jpg is no longer available

I should note after every iteration I tried with the original RTC module and the new one along with clearing CMOS for each power on to eliminate all possibilities. After all this I decided I should mess with the jumpers and eventually just landed on leaving them in their default position. I then decided maybe it was just busted so I told the guy I got it from and he gave me another one. It is identical. I did everything again and still 4 beeps no post.

I then determine based on no information whatsoever that it must be a BIOS corruption. I was mistaken. I read the BIOS chip. Perfectly fine. I then reflashed it and... 4 beeps no post. I did the same with the other BIOS chip... 4 beeps no post. Did the same on the other board with all previous configurations... 4 beeps no post. Photo below:

The attachment 17640492284742582354046936542269.jpg is no longer available

Both boards also came with Millennium Modules as onboard storage solutions. I didn't bother reading what was on the modules but I tried everything above with and without a Millennium Module to no avail... 4 beeps no post. Photo below:

The attachment 17640498157892343604353076855869.jpg is no longer available

At the end of it all and having exhausted all solutions I could muster, I find myself begging for help. I don't know what to do to stop the 4 beeps. Please help me.

Reply 1 of 11, by Greywolf1

User metadata
Rank Member
Rank
Member

There’s a manual available on the retro web site check the motherboards beep code list

Reply 2 of 11, by Dolard

User metadata
Rank Newbie
Rank
Newbie
Greywolf1 wrote on 2025-11-25, 06:34:

There’s a manual available on the retro web site check the motherboards beep code list

Tried this already. Conveniently the manual doesn't contain a post code directory.

Reply 3 of 11, by Greywolf1

User metadata
Rank Member
Rank
Member

I found 2 interesting bits of info could be worth looking into 1 is the watch dog timer and 2 the cmos battery (not a normal battery) cr 1225 won’t post with dead battery.

Reply 4 of 11, by Dolard

User metadata
Rank Newbie
Rank
Newbie
Greywolf1 wrote on 2025-11-25, 14:52:

I found 2 interesting bits of info could be worth looking into 1 is the watch dog timer and 2 the cmos battery (not a normal battery) cr 1225 won’t post with dead battery.

I've disabled the watch dog timer and I've metered the CMOS battery and it's still got over 3 volts. Still the 4 beeps remain D;

Reply 5 of 11, by Greywolf1

User metadata
Rank Member
Rank
Member

I’ve tried looking for different models of the same brand motherboard but haven’t found anything else that explains the beep codes.
The only beep code it mentions is the failed cmos battery. But it’s not 4 beeps

Reply 6 of 11, by Dolard

User metadata
Rank Newbie
Rank
Newbie
Greywolf1 wrote on 2025-11-27, 12:28:

I’ve tried looking for different models of the same brand motherboard but haven’t found anything else that explains the beep codes.
The only beep code it mentions is the failed cmos battery. But it’s not 4 beeps

I have realized this board probably came out of a military touchscreen unit produced by HMW Enterprises in the early 2000s and I believe it requires an LCD controller or some other peripheral component to function properly. A part of me also believes that maybe only LCD output functions for display during BIOS and setup and that CRT output might only work once configured. It's possible that the board works perfectly fine and I just can't see it working and that the weird 4 beeps code is for something completely separate of post.

Reply 7 of 11, by igully

User metadata
Rank Member
Rank
Member

I would suggest connecting the SBC's first serial port to a terminal (8N1 @ 9600).

Many SBC's have debugging facilities available from COM1 which is usually a standard RS-232 port. Beeps might indicate just an usually expected hardware condition not met (like LCD availability, lack of compatible keyboard, bad memory, etc.). Since it is a military SBC there is no way this feature would be left out for cost saving measures, as the military has deep pockets, and any manufacturer would like to keep them as a happy customer. I would give this serial connected terminal a try if you haven't already.

Reply 8 of 11, by Greywolf1

User metadata
Rank Member
Rank
Member

That Is something I have noticed during my searches is this range of boards were for industrial use there are websites in Italian and polish that have information but could not tell you if it’s the information you’re looking for.

Reply 9 of 11, by Dolard

User metadata
Rank Newbie
Rank
Newbie
igully wrote on 2025-11-27, 22:38:

I would suggest connecting the SBC's first serial port to a terminal (8N1 @ 9600).

Many SBC's have debugging facilities available from COM1 which is usually a standard RS-232 port. Beeps might indicate just an usually expected hardware condition not met (like LCD availability, lack of compatible keyboard, bad memory, etc.). Since it is a military SBC there is no way this feature would be left out for cost saving measures, as the military has deep pockets, and any manufacturer would like to keep them as a happy customer. I would give this serial connected terminal a try if you haven't already.

Turns out I'm an absolute dolt and it was working the whole time. I still don't know what the 4 beeps is and it still does it but video just isn't getting properly output from the CRT connector. The 50pin LCD connector worked just fine though I just didn't do that before hand because I needed to find a compatible LCD controller for the board but I've got one and it's displaying properly. I didn't even connect a keyboard.

Reply 10 of 11, by Dan386DX

User metadata
Rank Member
Rank
Member

I wonder if the four beeps is just a POST success noise, like with those cheap Chinese boards from AliExpress.

90s PC: IBM 6x86 120Mhz. 128MB/6GB. ATI Rage Pro 3D.
Boring modern PC: R9 3900X, RX 7800XT. 32GB/1TB.
Fixer upper project: NEC Powermate 486SX/25. 16MB/400MB.

Reply 11 of 11, by Dolard

User metadata
Rank Newbie
Rank
Newbie
Dan386DX wrote on 2025-12-07, 05:49:

I wonder if the four beeps is just a POST success noise, like with those cheap Chinese boards from AliExpress.

No, it seems the POST success is 1 beep once power is sent. The 4 beeps only seems then to happen once the power toggle is shorted after POST success. The device doesn't require that the power be toggled to turn on so maybe it has to do with it?