Error: SOC_POWER_GOOD signal has de-asserted

Tony Armitstead

Hi,

I am trying to get an XTCIEVMK2X EVM board up and running. I have been through the process of updating it to the latest f/w and am having problems booting Linux.

There are two issues - which I think are the same issue:

1. Sometimes when I boot the BCM screen shows:

BMC VERSION 1.0.2.5
BUILT May 14 2013 11:46:18
---------------------

[00:00:00] BMC Init Begin
[00:00:00] BMC Version 1.0.2.5
[00:00:00] XTCIEVMK2X
[00:00:00] 1.0.0.2
[00:00:00] S/N: 79861
[00:00:00] BMC Init Complete
[00:00:00] Main PWR Start Begin
[00:00:00] Main PWR Start Complete
[00:00:00] SOC PWR Start Begin
[00:00:00] EVM setup has encountered the following error: The signal SOC_POWER_GOOD has failed to assert
[00:00:00] SOC PWR Stop Begin
[00:00:00] SOC PWR Stop Complete
[00:00:01] HWDBG is set to ON, evm setup will now halt.
[00:00:01] To alter this behavior, please use the hwdbg command.
BMC>

2. When the system boots up past BCM and loads up uboot and Linux, the SOC_POWER_GOOD signal disappears. The BCM serial port shows:

BMC VERSION 1.0.2.5
BUILT May 14 2013 11:46:18
---------------------

[00:00:00] BMC Init Begin
[00:00:00] BMC Version 1.0.2.5
[00:00:00] XTCIEVMK2X
[00:00:00] 1.0.0.2
[00:00:00] S/N: 79861
[00:00:00] BMC Init Complete
[00:00:00] Main PWR Start Begin
[00:00:00] Main PWR Start Complete
[00:00:00] SOC PWR Start Begin
[00:00:00] Clock 1
[00:00:00] Passed
[00:00:00] Clock 2
[00:00:01] Passed
[00:00:01] Clock 3
[00:00:01] Passed
[00:00:01] SOC PWR Start Complete
[00:00:01] SOC RST Begin
[00:00:01] Current BootMode is set to ARM SPI
[00:00:01] SOC RST Complete
[00:00:02] BOOT COMPLETE

[00:00:23] Error: SOC_POWER_GOOD signal has de-asserted. Shutting down soc power.

[00:00:23] Full Reset Begin
[00:00:23] Full Reset Complete
[00:00:23] POR Begin
[00:00:24] POR Complete
[00:00:24] SOC PWR Stop Begin
[00:00:24] SOC PWR Stop Complete
BMC>

and the uboot/Linux serial port shows:

U-Boot SPL 2013.01 (Nov 24 2013 - 16:43:18)
SF: Detected N25Q128A with page size 64 KiB, total 16 MiB

U-Boot 2013.01 (Nov 24 2013 - 16:43:18)

I2C:   ready
Detected SO-DIMM []
DRAM: 1 GiB
NAND: 512 MiB
Net:   TCI6638_EMAC, TCI6638_EMAC1
Hit any key to stop autoboot: 3 2 1 0
Creating 1 MTD partitions on "nand0":
0x000000180000-0x000020000000 : "mtd=2"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=2"
UBI: MTD device size:            510 MiB
UBI: number of good PEBs:        4080
UBI: number of bad PEBs:         4
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     3
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 4080
UBI: number of PEBs reserved for bad PEB handling: 40
UBI: max/mean erase counter: 1/0
UBIFS: mounted UBI device 0, volume 0, name "boot"
UBIFS: mounted read-only
UBIFS: file system size:   5713920 bytes (5580 KiB, 5 MiB, 45 LEBs)
UBIFS: journal size:       1142785 bytes (1116 KiB, 1 MiB, 9 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: LZO
UBIFS: reserved for root: 0 bytes (0 KiB)
Loading file 'uImage-k2hk-evm.dtb' to addr 0x87000000 with size 57857 (0x0000e201)...
Done
Loading file 'skern-keystone-evm.bin' to addr 0x0c5f0000 with size 45056 (0x0000b000)...
Done
Loading file 'uImage-keystone-evm.bin' to addr 0x88000000 with size 3990416 (0x003ce390)...
Done
## installed monitor, freq [204800000], status 0
## Booting kernel from Legacy Image at 88000000 ...
   Image Name:   Linux-3.10.10
   Created:      2013-11-24 21:26:00 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3990352 Bytes = 3.8 MiB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 87000000
   Booting using the fdt blob at 0x87000000
   Loading Kernel Image ... OK
OK
   Using Device Tree in place at 87000000, end 87011200

Starting kernel ...

Is it when the Linux boot shows 'Starting kernel ...' that the BCM port shows
'[00:00:23] Error: SOC_POWER_GOOD signal has de-asserted. Shutting down soc power'.

Have I got a h/w problem or is there some s/w fix that I am not aware of?

Thanks for your help, Tony.

over 10 years ago

0 Rex Chang over 10 years ago

TI__Guru 50170 points

Hi, Tony,

What's your UCD versions and have you updated the UCD accroding to the HW set up guide?

Rex

0 Tony Armitstead over 10 years ago in reply to Rex Chang

Prodigy 20 points

Hi Rex,

Many thanks for your post - it led me to the fix.

I basically followed the instructions at

http://processors.wiki.ti.com/index.php/EVMK2H_Hardware_Setup#UCD_Power_Management_Modules_In-Field_Update

to update the three UCD modules. It wasnt 100% per the instructions because the instructions claim you can have the DIP switch setting in any position. Not true for my situation. I had to have the switches in no boot mode (0001). If I didnt, it tried to boot and then powered down as per my original post. This caused the I2C commands being issued by the update tool to fail. When I set the switches to 0001 the re-programming went as planned. Now I can boot into Linux no problem.

Thanks again, Tony.

0 Rex Chang over 10 years ago in reply to Tony Armitstead

TI__Guru 50170 points

Hi, Tony,

Glad that you got it working. Let me discuss this internally and see if we need to update the document if the EVM stays at power failure state.

Thanks!

Rex

0 Dave McIntyre over 8 years ago in reply to Rex Chang

Prodigy 40 points

I also have an XTCIEVMK2X EVM that has the message "The signal SOC_POWER_GOOD has failed to assert".
My BMC version is 1.0.2.6, type is 0.0.0.1, EVM version is 4.0 and UCD version is A03.

My BMC output looks very similar to #1 and #2 in the original post. So is the correct answer then to update my UCD? Or do I have a HW problem?

Thanks

Dave

0 Stefan Rusu over 8 years ago in reply to Dave McIntyre

Prodigy 30 points

BMC VERSION 1.0.2.6
BUILT Nov 5 2013 13:06:10
---------------------

[00:00:00] BMC Init Begin
[00:00:00] BMC Version 1.0.2.6
[00:00:00] XTCIEVMK2X
[00:00:00] 4.0
[00:00:00] BMC Init Complete
[00:00:00] Main PWR Start Begin
[00:00:00] Main PWR Start Complete
[00:00:00] SOC PWR Start Begin
[00:00:00] EVM setup has encountered the following error: The signal SOC_POWER
GOOD has failed to assert
[00:00:00] SOC PWR Stop Begin
[00:00:01] SOC PWR Stop Complete
[00:00:01] HWDBG is set to ON, evm setup will now halt.
[00:00:01] To alter this behavior, please use the hwdbg command.

We hit the same issue as Dave, on one of our "~5 week old" boards, same BMC/EVM versions. Tried updating the UCD even though they were the latest version on the board, except the one that actually had a higher version than what's available here wfcache.advantech.com/.../UCD_Update_Tool_Rev1_1.zip

It didn't work... so maybe it's a hardware failure?

0 Dave McIntyre over 8 years ago in reply to Stefan Rusu

Prodigy 40 points

this link:

http://wfcache.advantech.com/www/support/TI-EVM/Rev4_0/UCD/UCD_Configuration_Standard_Release.zip

points to a set of updated ucd files (104_A03, 52_A04, and 78_A04)

I have not tried it yet.

0 Stefan Rusu over 8 years ago in reply to Dave McIntyre

Prodigy 30 points

I tried those too Dave but the update for one of them didn't work and the others didn't make any difference

0 Rex Chang over 8 years ago in reply to Stefan Rusu

TI__Guru 50170 points

Hi, Dave & Stefan,

Could you provide the versions for the UCD modules by following step 5 "Get Version" in the UCD Update Guide? Rev 4.0 EVM should have correct UCD version but just want to be sure that they are up to date. In case update is needed, you will need to update all 3 modules, 52, 78, and 104.

Rex

0 Dave McIntyre over 8 years ago in reply to Rex Chang

Prodigy 40 points

104_A03, 78_A03_02, 52_A03_03

BMC is at 1.0.2.6

0 Stefan Rusu over 8 years ago in reply to Dave McIntyre

Prodigy 30 points

Same for me:

104_A03
78_A03_02
52_A03_03

And now after updating the broken target (including non-ascii characters that appear):
104_A03
78_A04♂♂♂
52_A04...

Note that update of 104_A03 from wfcache.advantech.com/.../UCD_Configuration_Standard_Release.zip failed to work
so the 104_A03 shown is from this one wfcache.advantech.com/.../UCD_Update_Tool_Rev1_1.zip
... even though the files are different.. why would you keep the same version number....?

0 Rex Chang over 8 years ago in reply to Stefan Rusu

TI__Guru 50170 points

You may want to pursue this issue with Advantech. Rev 4.0 EVM should not have the power issue and the UCD versions are correct.
Rex

0 Dave McIntyre over 8 years ago in reply to Stefan Rusu

Prodigy 40 points

I've tried contacting tech support at Advantech but, so far, no reply.

0 Rex Chang over 8 years ago in reply to Dave McIntyre

TI__Guru 50170 points

Dave,

How did you get your EVM? Do you have a TI field contact?

Rex

0 xin li3 over 8 years ago in reply to Rex Chang

Intellectual 520 points

I have got the same message "Error: SOC_POWER_GOOD signal has de-asserted" almost every time when I power on my EVMK2H rev4.0. I have tried all the 4 versions of BMCs and UCDs including the latest version of BMC 1.0.2.6 and UCD downloaded from AdvanTech official website, and all the trials haven't worked so far.

Could you know how to work it out ?

Is there something wrong in hardware, or I did not get a correct version of BMC and UCD, or other else?

thanks for any response.

0 Rex Chang over 8 years ago in reply to xin li3

TI__Guru 50170 points

I am trying to get hold of one of the failed EVMs and see what could be the issue. I myself have several Rev 4.0 K2H EVMs, but none of them has any issues. I'll update this thread once I got the EVM and spend some time on it.

Rex

0 xin li3 over 8 years ago in reply to Rex Chang

Intellectual 520 points

Hi, Rex.

Here is what was happening to my EVMK2H Rev 4.0. I suggest you try the following steps on your EVMK2H, maybe it will produce the error "Error: SOC_POWER_GOOD signal has de-asserte".

(1)For the first time, the error occured sometimes but not always when I powered on the new EVMK2H.

(2)So I tried to update to the latest version of UCD downloaded from AdvanTech website, but it didn't work either.

(3)And then I tried all other versions of UCDs and BMCs 1.0.2.5/1.0.2.6. After that, the Error occurs almost every time when I power it on.

0 xin li3 over 8 years ago in reply to Rex Chang

Intellectual 520 points

Hi, Rex,

Could you let me know a little bit about your current situation regarding the error "SOC_POWER_GOOD signal has de-asserted"? Now I can not do angthing to my EVMK2H 4.0 because of the error.

0 Rex Chang over 8 years ago in reply to xin li3

TI__Guru 50170 points

Hi, Xin,

Please contact Advantech who manufactures the K2H for a replacement. The 3rd party EVMs failed in the field do not come back to TI and I won't be able to diagnose the issue.

Rex

0 Raja over 8 years ago in reply to Rex Chang

TI__Guru* 81335 points

Hi Xin,

We have updated UCD files to fix power issue. We recommend you to go through the known issue document and fix the power issue by updating the UCDs.

Please take a look at know issue document and download UCD files from below link.

http://www2.advantech.com/Support/TI-EVM/EVMK2HX_sd4.aspx

Thank you.

Processors

Processors forum

Error: SOC_POWER_GOOD signal has de-asserted