Question Modem ,''Hit any key to stop autoboot: 0 '' ,and just stoped.

[FireworksON]

How to figure out the holes below, Which one is Tx,and RX,and GND. There are no marks on the board, it's a Chinese modem board. I don't know how to figure them out, so I looked through many posts from many forums,and at last I connected them.However I got the logs below,It just stopped there, it should have continued. What's the problem here? The modem is brand new.

Boot SPI NAND
k3

U-Boot 2013.04 (May 14 2019 - 12:16:13)

CPU : ZX279127@A9,800MHZ
Board: ZTE zx279127evb
I2C: ready
DRAM: 256 MiB
com1
product_vid = 89
vid=89-F663NV3a
bootsel=3
10000000,50000000
NAND: manuid=2c,24

Manu ID: 0x2c, Chip ID: 0x24 (Micron SPI NAND MT29F2G01ABAGDWB 256MiB 3,3V)
256 MiB
<nand_read_skip_bad_,1237>!mtdpart=0x1,offset=0x0,mtdpartoffset=0x180000,mtdPartsize=0x80000,length=0x20000
In: serial
Out: serial
Err: serial
Net: addr 0x94000008 before value is f9ffffcf
addr 0x94000008 after value is ffffffcf
serdes init done
init phy first!
eth0
Hit any key to stop autoboot: 0
=>

It should have Printed more,but it stoped here,what's wrong？

 

[kanewolf]

You successfully got the console port connected. What help are you expecting from us ?

 

[Alabalcho]

Four pins - probably, GND/VDC/TxD/RxD
Ground and power will be easy to detect with a ohm- and volt-meter. The other two are (most probably) TTL signals, either 3.3 or 5V, so get a converter, and try.

 

[FireworksON]

You successfully got the console port connected. What help are you expecting from us ?

Sorry, if it had been connected, it should have printed much more,but in fact it didn't,and i couldn't type in anything, there must be sth wrong.

 

[FireworksON]

You successfully got the console port connected. What help are you expecting from us ?

It seems that it had been connected,but when i tapped "Space" Key, it just showed "INTERRUPT", what the problem? And when I tap the "ENTER" Key, the "⇒ "turned into " y>" . Please help!

 

[FireworksON]

Four pins - probably, GND/VDC/TxD/RxD
Ground and power will be easy to detect with a ohm- and volt-meter. The other two are (most probably) TTL signals, either 3.3 or 5V, so get a converter, and try.

The last one seems do not connect anything, why it's RxD? Sorry,i don't have a multimeter at hand, so I can't detect them.

 

[FireworksON]

You successfully got the console port connected. What help are you expecting from us ?

Here is the same steps from a forum.

 

[FireworksON]

The problems above have been solved, i think i had connected the wrong pins. But i got a new problem,it struck again, showing
" |-->setup versioninfo tag...

Starting kernel ...

Uncompressing Linux... done, booting the kernel."


Entire:


Boot SPI NAND
k3

U-Boot 2013.04 (May 14 2019 - 12:16:13)

CPU : ZX279127@A9,800MHZ
Board: ZTE zx279127evb
I2C: ready
DRAM: 256 MiB
com1
product_vid = 89
vid=89-F663NV3a
bootsel=3
10000000,50000000
NAND: manuid=2c,24

Manu ID: 0x2c, Chip ID: 0x24 (Micron SPI NAND MT29F2G01ABAGDWB 256MiB 3,3V)
256 MiB
<nand_read_skip_bad_,1237>!mtdpart=0x1,offset=0x0,mtdpartoffset=0x180000,mtdPartsize=0x80000,length=0x20000
In: serial
Out: serial
Err: serial
Net: addr 0x94000008 before value is f9ffffcf
addr 0x94000008 after value is ffffffcf
serdes init done
init phy first!
eth0
Hit any key to stop autoboot: 0
addr=1a00000
addr=3a00000
select=0x0
search=0x2
<nand_read_skip_bad_,1237>!mtdpart=0x6,offset=0x0,mtdpartoffset=0x200000,mtdPartsize=0x400000,length=0x1000
tmp=0x00000000, value=0
select=0x0
search=0x2
search->result[0].entry=1a00140
<nand_read_skip_bad_,1237>!mtdpart=0x2,offset=0x0,mtdpartoffset=0x1a00000,mtdPartsize=0x2000000,length=0x1660000

---mtdparts_init--current_mtd_partnum=0-
dev id: type = 2, num = 0, size = 0xffffffff, mtd_id = single part
part : name = rootfs0, size = 0x01640000, offset = 0x01a20000
part : name = rootfs1, size = 0x01640000, offset = 0x03a20000

--- jffs2_part_info: partition number 0 for device nand0 (single part)
jffs2_part_info:rootfs0,1a20000
### JFFS2 loading '0uImage' to 0x44000000
Scanning JFFS2 FS: ............... done.
### JFFS2 load complete: 4013538 bytes loaded to 0x44000000
<nand_read_skip_bad_,1237>!mtdpart=0x0,offset=0x0,mtdpartoffset=0x0,mtdPartsize=0x180000,length=0x80000
lseek=0x42048000
cmdline=U-Boot V1.1.1 20190214092645
## Booting kernel from Legacy Image at 44000000 ...
Image Name: Linux Kernel Image
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4013474 Bytes = 3.8 MiB
Load Address: 40008000
Entry Point: 40008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
----------------------
|-->setup versioninfo tag...

Starting kernel ...

Uncompressing Linux... done, booting the kernel.