Problem When Trying to configure GD3

[mohamed-eid]

Hello All,

could any one help me, as I am facing a problem when I try to configure the GD-3 board via serial connection.
I added role ip address to the cpu using (netadmin -m) to be used for configuration for main and I left the IP address of the CPU (CS) as it is and rebooted it, after rebooting both GD and CS could not get in service, so I want to connect to the GD-3 board and configure its IP, so when I connect to the board, it gives me login name and password, I use "root or admin/pass:admin" then once I write (mgconfig) the board restart it self.

with (netadmin -m) I added the same role IP address to the twin CS but configuration didn't stored, I don't know why?, so GD is working on the twin CS and is not working on the Main CS.
could the problem in the cable?!!!, also when I wanted to return configuration back on the main CS using serial cable, I can not connect to as it seems like power down.

[patmul39]

As far as I am aware, admin account is not available anymore on GD3. To configure the GD3 you need to connect as root.

[mohamed-eid]

hello patmul39,
I try root, and I succeeded to login, but once I write (mgconfig) the board restart it self, and I don't see (mgconfig) menu

[mohamed-eid]

here is a prt.text from hyper terminal of the GD-3 board

U-Boot 1.3.0-rc3 (Mar 5 2010 - 11:50:23) 3EH30350AAAM bootl100/000.012

Reset Status:

CPU: e300c4, MPC8377, Rev: 21 at 666.666 MHz, CSB: 333 MHz
I2C: ready
DRAM:
DDR DIMM: data bus width is 64 bit without ECC
DDRC ECC mode: OFF
DDR RAM: 256 MB
FLASH: 2 MB
PCI: Bus Dev VenId DevId Class Int
00 17 1064 2102 0000 00
In: serial
Out: serial
Err: serial
Net: TSEC0, TSEC1
eSDHC: 4bit-buswidth mode
SATA: SATA0 [Link: no RDY]
SATA1 [Link: no RDY]
## Booting image at ff836de0 ...
Image Name: aleboot.bin
Image Type: PowerPC U-Boot Standalone Program (uncompressed)
Data Size: 8840 By

U-Boot 1.3.0-rc3 (Mar 5 2010 - 11:50:23) 3EH30350AAAM bootl100/000.012

Reset Status:

CPU: e300c4, MPC8377, Rev: 21 at 666.666 MHz, CSB: 333 MHz
I2C: ready
DRAM:
DDR DIMM: data bus width is 64 bit without ECC
DDRC ECC mode: OFF
DDR RAM: 256 MB
FLASH: 2 MB
PCI: Bus Dev VenId DevId Class Int
00 17 1064 2102 0000 00
In: serial
Out: serial
Err: serial
Net: TSEC0, TSEC1
eSDHC: 4bit-buswidth mode
SATA: SATA0 [Link: no RDY]
SATA1 [Link: no RDY]
## Booting image at ff836de0 ...
Image Name: aleboot.bin
Image Type: PowerPC U-Boot Standalone Program (uncompressed)
Data Size: 8840 Byt

U-Boot 1.3.0-rc3 (Mar 5 2010 - 11:50:23) 3EH30350AAAM bootl100/000.012

Reset Status:

CPU: e300c4, MPC8377, Rev: 21 at 666.666 MHz, CSB: 333 MHz
I2C: ready
DRAM:
DDR DIMM: data bus width is 64 bit without ECC
DDRC ECC mode: OFF
DDR RAM: 256 MB
FLASH: 2 MB
PCI: Bus Dev VenId DevId Class Int
00 17 1064 2102 0000 00

[enio.eltz]

Hi mohamed-eid

You have posted:

after rebooting both GD and CS could not get in service

If you could get CS in service, you won't have GD in service. First of all check if CS is in service.

[mohamed-eid]

should I configure the Gd-3 board to see the role CPU address to enable communication between CS and GD?!! I think this is right.
so I configured the CS to have a role IP address, then the GD couldn't communicate with the CS.
So I must configure the role CPU address in the GD board.
when I try to make this after login successfully using admin or root, I can't configure by mgconfig, as the GD restarts after I write mgconfig