Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
61 user(s) are online (48 user(s) are browsing Forums)

Members: 2
Guests: 59

khayoz, Raziel, more...

Support us!

Headlines






x5000: Scary story & MCU Debug interface
Home away from home
Joined:
2007/9/11 12:31
From Russia
Posts: 7018
@All
I wrote about it in the beta groups, but I think some of you may found it funny/interesting to read, so put it here as well with just a bit better design and information. All images are clickable for full-size.

So, yesterday my x5000 stop power-on just for no reason. I.e. you press the power button, led is working, but then nothing else. You even can't power-off it back.

First, I unplug everything one by one: no luck
Then I just put off the motherboard from the case on the table and attach just a PSU + CPU/FAN + Ram Module: no luck
With or without SD Card: no luck
Module in all different slots: no luck
Different PSUs (3 of them): no luck.

All that motherboard show me just 2 working LEDs on it: one green is LED1 one, "Stand by power indicator", and the second one, are LED16 one, indicated red "Standby state indicator (CPLD Controlled):

Resized Image

Once I press power-on, nothing changes in the LEDs. The same 2 LEDs only, and slow speed of fans moving. And I also can't power off by holding the power button. It's like the power going to the motherboard, but nothing else happens next.

Then attached the serial cable to see that there is absolutely nothing in output, so it was time for not casual serial cable, but going deeper and attach to the MCU debug interface (called DEBUG SERIAL TERMINAL, i.e. simple "serial" is what we have from rs232 and this one is another, debug one for motherboards needs)

Resized Image


Resized Image


For that, I use a special cable called "FTDI cable" which is doing the same as we do with RS232 for pure serial cable: Serial To USB. But while in the case with serial it does convert in one format, for FDTI in convert in another one (often called TTL, UART, etc) format (the format used to program/control microcontrollers, etc). So special cable needs it.

My one based on the PL2303TA built-in in the USB-connector itself:

Resized Image Resized Image

Resized Image

Now, once you connect it to your terminal (i use Putty on win32), be sure you have a 38400 baud rate, or you will see nothing or garbage, and be sure you have disabled flow control, or you will be not able to type anything.

Then even if you do not power on the machine, but just hook up power cable, you already can operate with x5000:

Quote:

Cyrus Plus
MCU Firmware Version 2.1
Hardware Version 2.1
CPLD Version 2.0
CPLD build time: 10:10:10
CPLD build date: 2014-05-27
MCU build time: 10:34:25
MCU build date: May 30 2014
SYS CLK frequency 133MHz
Dual Ethernet devices fitted.
P5020 processor fitted

>> help

command description
======= ======================================================
help Print this help list
id Identify (report h/w and f/w revisions)
id date Identify (report h/w and f/w revisions build date)
p Power up all supplies
s Shut down all supplies
q Toggle printing
v Print voltages and temperatures
OK
>> id

Cyrus Plus
MCU Firmware Version 2.1
Hardware Version 2.1
CPLD Version 2.0
Dual Ethernet devices fitted.
Release Build
OK
>> id date

Cyrus Plus
CPLD build time: 10:10:10
CPLD build date: 2014-05-27
MCU build time: 10:34:25
MCU build date: May 30 2014
OK
>>



>> p
Powering up...
Enabled PS_ON



So, once I type there "p" (to power on the machine), it just shows me POWER_ON, and then nothing happens after. It even didn't come to the level of checking anything. It's like everything stops too early, on the power level, I.e. electricity coming to the motherboard, but not enough. But, from the same electrical Outlets, notebooks, TV, other devices like monitor - works just fine.

I start then to check all sorts of things, swap everything, etc, etc, with no luck. Then after some hours, wife saying that something happens with the electric stove, it starts to behave strangely. So I come to see: it also just like x5000 power on, LEDs working, but start to produce all sort of errors. Then next I heard "noise" from an electric water heater, saying something wrong, next it was Dishwasher behave strangely: can power on, but can't power off and LEDs blinks.

So my first fear was that everything just died at once, because of some electricity issue happens (despite me being paranoic and have all sorts of protective automatic fuse/circuit breakers). Ok, bad, but then Pegasos2 should be still alive, as it wasn't powered on, and wasn't connected at all, but surprise: I tried to boot up my pegasos2: NO BOOT! So, if things that were enabled died at once, how it can be that pegasos2 died too if it was fully disabled from all the cables? I take pegasos2 to another house of neighbors, and there it boots! So issue cleary in my house then.

Next, I start to check via multimeter wtf happens with volts/ampers/etc in the outlets: surprise, half of them (those ones where devices behave bad and computers didn't boot), have 110VOLT instead of 220-230! And notebooks/monitors/etc works because they have no needs for 220, but seems ok even with 110. To my house comes 3 AC Phases per 5KV, and each of them I use for different needs: lights on one of them, "big" things on another one, and 3rd one for outlets. Checked my electric-fuse-circuit-breakers inside of the house: all fine. Went outside to see what happens on the concrete pillar with the electrical panel of the company giving me electricity: Once comes close, felt this delicious smell when something overheats. So call the company, and there is a gift they gave to me today:

Resized Image

Swapped it on the new one, a bit bigger-better, explaining why happens that after this thing fire up all drops from 220V to 110V, and wish my luck with my x5000 :) So come back to home, checked: x5000 boots, pegasos2 boots, all devices works!

Of course, it can be cool if x5000 says at the beginning not just "POWER_ON", but something "you have not enough power to power_on at full", but probably it's too much to ask from just a computer motherboard, and besides, in my case, it were surely some kind of strange situation anyway.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites
   Report Go to top

Re: x5000: Scary story & MCU Debug interface
Site Builder
Joined:
2006/12/2 23:57
From Athens/Dublin
Posts: 821
I am glad you sorted out the situation and your machine works fine. For sure it is a weird thing to happen.

   Report Go to top

Re: x5000: Scary story & MCU Debug interface
Home away from home
Joined:
2006/12/2 3:55
From Italy, Perugia
Posts: 3417
@kas1e

Wow what a story
Glad you resolve everything and your X5000 still alive along with all your other devices .. that's the most important thing

   Report Go to top

Re: x5000: Scary story & MCU Debug interface
Quite a regular
Joined:
2007/7/23 21:35
Posts: 712
@kas1e

You were not kidding, that is a scary story.
Thankfully you, your family and your equipment are all in good health.

Cheers

   Report Go to top

Re: x5000: Scary story & MCU Debug interface
Just can't stay away
Joined:
2007/7/14 21:30
From Lothric
Posts: 1325
@kas1e

Wow, nasty stuff. That might have escalated badly, like fire..

   Report Go to top

Re: x5000: Scary story & MCU Debug interface
Home away from home
Joined:
2007/9/11 12:31
From Russia
Posts: 7018
@Capehill
Quote:

Wow, nasty stuff. That might have escalated badly, like fire..


That died fuse was on their concrete pillar, so if it fires up then just on its own. Also, I have lots of fuses inside of the house (right where the input of electricity comes) (not just automatic only, but some more protective of different situations). Plus, all my cables poured into concrete floors and of good quality (so once and if they will fire, beton will not help to spread the fire further).

But yeah, with electricity everything possible, even 10 fuses can be bypasses by a combination of bad factors, and everything can output in one single outlet right over your hands, and exactly in time when you didn't expect it :)

Exactly that fuse should be disabled once hot arise, but in my situation is not (while it's "schneider electric", not the worse kind of fuses). It even didn't disabled, so electricity continues to come into the house, and maybe my own fuses "split" the voltage from 220 to 110 and didn't disable too, and that was the reason for my first thought that x5000 and other devices dead.

But at least this dead fuse took a hit and save other ones in the сhain

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites
   Report Go to top

Re: x5000: Scary story & MCU Debug interface
Just popping in
Joined:
2007/1/10 21:56
From Stockholm Sweden
Posts: 172
@kas1e

I have way too long thought about buying a really good fused backup UPS for my X5000, guess your scary story convinced me to REALLY fix it once and for all.

Happy to hear that your X5000 survived it all.

_________________
1989-> A500, A600, A3000, A4000, A1200, CD32, µA1, PegII, A1XE, CDTV, Amy/416D79, A1X5000, Vampire 500 V2+, Vampire 600 V2, Amy-ITX<-2021
   Report Go to top

Re: x5000: Scary story & MCU Debug interface
Just popping in
Joined:
2007/2/14 15:50
From Australia
Posts: 74
That would have scared the hell out of me.

In regards to the potential alert, it is definitely an edge case not many people would have thought of :)

   Report Go to top

Re: x5000: Scary story & MCU Debug interface
Home away from home
Joined:
2009/7/7 4:34
From Man Cave, Canada
Posts: 2491
@kas1e

just nuts but in the end happy to hear X5000 and all your equipment is safe but honestly nothing surprises me anymore when it comes to computers or anything electronic as I've seen/ heard all kinds over the years ...just like X-FILES..the truth is out there and strange shit happens sometimes that defies logic

_________________
_______________________________
c64-dual sids, A1000, A1200-060@50, A4000-CSMKIII
Indivision AGA & Catweasel MK4+= Amazing
! My Master Miggies-Amiga1000 & AmigaONE X1000 !
mancave-ramblings

   Report Go to top





[Advanced Search]



Powered by XOOPS 2.0 © 2001-2016 The XOOPS Project