Conduit no longer responding serial login on device port
Home › Forums › Conduit: mLinux Model › Conduit no longer responding serial login on device port
- This topic has 5 replies, 3 voices, and was last updated 9 years, 4 months ago by
Jeff Hatch.
-
AuthorPosts
-
November 9, 2015 at 10:16 pm #9874
Jonathan Pickett
ParticipantOn power up the PWR, STATUS and LS lights come on and stays on. Spew from the debug port looks like:
OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Booting Linux on physical CPU 0x0 Linux version 3.12.27 (jenkins@frylock) (gcc version 4.8.2 (GCC) ) #1 Wed May 27 01:49:19 CDT 2015 Machine: Atmel AT91SAM (Device Tree), model: Multi-Tech Systems MTCDT AT91: Detected soc type: at91sam9x5 AT91: Detected soc subtype: at91sam9g25 AT91: sram at 0x300000 of 0x8000 mapped at 0xfef70000 Kernel command line: mem=256M console=ttyS0,115200 root=/dev/mtdblock8 ro rootfstype=jffs2 PID hash table entries: 1024 (order: 0, 4096 bytes) Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) vmalloc : 0xd0800000 - 0xff000000 ( 744 MB) lowmem : 0xc0000000 - 0xd0000000 ( 256 MB) modules : 0xbf000000 - 0xc0000000 ( 16 MB) .text : 0xc0008000 - 0xc04ee4a4 (5018 kB) .init : 0xc04ef000 - 0xc0516c14 ( 160 kB) .data : 0xc0518000 - 0xc05406a0 ( 162 kB) .bss : 0xc05406a0 - 0xc055ef08 ( 123 kB) NR_IRQS:16 nr_irqs:16 16 sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 4294967286ms Calibrating delay loop... 199.06 BogoMIPS (lpj=995328) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 Initializing cgroup subsys blkio CPU: Testing write buffer coherency: ok Setting up static identity map for 0xc03a8cd8 - 0xc03a8d30 devtmpfs: initialized pinctrl core: initialized pinctrl subsystem NET: Registered protocol family 16 DMA: preallocated 256 KiB pool for atomic coherent allocations AT91: Power Management (with slow clock mode) AT91: Starting after power-restored wakeup gpio-at91 fffff400.gpio: at address fefff400 gpio-at91 fffff600.gpio: at address fefff600 gpio-at91 fffff800.gpio: at address fefff800 gpio-at91 fffffa00.gpio: at address fefffa00 pinctrl-at91 pinctrl.2: initialized AT91 pinctrl driver bio: create slab <bio-0> at 0 at_hdmac ffffec00.dma-controller: Atmel AHB DMA Controller ( cpy slave ), 8 channels at_hdmac ffffee00.dma-controller: Atmel AHB DMA Controller ( cpy slave ), 8 channels SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb i2c-gpio i2c.3: using pins 30 (SDA) and 31 (SCL) i2c-gpio i2c.4: using pins 64 (SDA) and 65 (SCL) Switched to clocksource tcb_clksrc NET: Registered protocol family 2 TCP established hash table entries: 2048 (order: 2, 16384 bytes) TCP bind hash table entries: 2048 (order: 1, 8192 bytes) TCP: Hash tables configured (established 2048 bind 2048) TCP: reno registered UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. NFS: Registering the id_resolver key type Key type id_resolver registered Key type id_legacy registered jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. ROMFS MTD (C) 2007 Red Hat, Inc. msgmni has been set to 496 Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) io scheduler noop registered (default) io scheduler deadline registered io scheduler cfq registered fffff200.serial: ttyS0 at MMIO 0xfffff200 (irq = 16, base_baud = 8333333) is a ATMEL_SERIAL console [ttyS0] enabled f8040000.serial: ttyS1 at MMIO 0xf8040000 (irq = 26, base_baud = 8333333) is a ATMEL_SERIAL brd: module loaded loop: module loaded at24_get_setup: found a match for eeprom at 56 at24 0-0056: 512 byte 24c04 EEPROM, writable, 16 bytes/write sam9x5: read 512 bytes from id eeprom at24_get_setup: found a match for eeprom at 50 at24 1-0050: 512 byte 24c04 EEPROM, writable, 16 bytes/write sam9x5: ap1 eeprom read failed: -110 at24_get_setup: found a match for eeprom at 52 at24 1-0052: 512 byte 24c04 EEPROM, writable, 16 bytes/write sam9x5: read 512 bytes from ap2 eeprom atmel_nand 40000000.nand: Using dma0chan0 for DMA transfers. ONFI param page 0 valid ONFI flash detected NAND device: Manufacturer ID: 0x2c, Chip ID: 0xaa (Micron MT29F2G08ABBEAHC), 256MiB, page size: 2048, OOB size: 64 atmel_nand 40000000.nand: ONFI params, minimum required ECC: 4 bits in 512 bytes atmel_nand 40000000.nand: Initialize PMECC params, cap: 4, sector: 512 Scanning device for bad blocks 9 ofpart partitions found on MTD device atmel_nand Creating 9 MTD partitions on "atmel_nand": 0x000000000000-0x000010000000 : "NANDFlash" 0x000000000000-0x000000040000 : "at91bootstrap" 0x000000040000-0x0000000c0000 : "u-Boot" 0x0000000c0000-0x000000160000 : "u-Boot Config" 0x000000160000-0x000000200000 : "u-Boot Redundant Config" 0x000000200000-0x000000800000 : "uImage" 0x000000800000-0x000001000000 : "Config" 0x000001000000-0x000001800000 : "OEM Config" 0x000001800000-0x000010000000 : "Rootfs" libphy: MACB_mii_bus: probed macb f802c000.ethernet eth0: Cadence MACB at 0xf802c000 irq 23 (00:08:00:4a:01:6f) macb f802c000.ethernet eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=f802c000.etherne:00, irq=-1) PPP generic driver version 2.4.2 PPP BSD Compression module registered PPP Deflate Compression module registered ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver ehci-atmel: EHCI Atmel driver atmel-ehci 700000.ehci: EHCI Host Controller atmel-ehci 700000.ehci: new USB bus registered, assigned bus number 1 atmel-ehci 700000.ehci: irq 31, io mem 0x00700000 atmel-ehci 700000.ehci: USB 2.0 started, EHCI 1.00 usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: EHCI Host Controller usb usb1: Manufacturer: Linux 3.12.27 ehci_hcd usb usb1: SerialNumber: 700000.ehci hub 1-0:1.0: USB hub found hub 1-0:1.0: 3 ports detected ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver at91_ohci 600000.ohci: AT91 OHCI at91_ohci 600000.ohci: new USB bus registered, assigned bus number 2 at91_ohci 600000.ohci: irq 31, io mem 0x00600000 usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb2: Product: AT91 OHCI usb usb2: Manufacturer: Linux 3.12.27 ohci_hcd usb usb2: SerialNumber: at91 hub 2-0:1.0: USB hub found hub 2-0:1.0: 3 ports detected rtc (null): invalid alarm value: 1900-1-1 0:0:0 at91_rtc fffffeb0.rtc: rtc core: registered fffffeb0.rtc as rtc0 at91_rtc fffffeb0.rtc: AT91 Real Time Clock driver. i2c /dev entries driver at91sam9_wdt: enabled (heartbeat=15 sec, nowayout=0) Netfilter messages via NETLINK v0.30. nf_conntrack version 0.5.0 (3973 buckets, 15892 max) ipip: IPv4 over IPv4 tunneling driver gre: GRE over IPv4 demultiplexor driver ip_gre: GRE over IPv4 tunneling driver ip_tables: (C) 2000-2006 Netfilter Core Team TCP: cubic registered NET: Registered protocol family 17 l2tp_core: L2TP core driver, V2.0 Key type dns_resolver registered at91_rtc fffffeb0.rtc: setting system clock to 2015-10-09 21:00:46 UTC (1444424446) usb 1-2: new high-speed USB device number 2 using atmel-ehci usb 1-2: New USB device found, idVendor=0424, idProduct=2534 usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 hub 1-2:1.0: USB hub found hub 1-2:1.0: 4 ports detected usb 2-3: new full-speed USB device number 2 using at91_ohci usb 2-3: New USB device found, idVendor=04e2, idProduct=1412 usb 2-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 usb 1-2.2: new high-speed USB device number 3 using atmel-ehci usb 1-2.2: New USB device found, idVendor=0403, idProduct=6014 usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-2.2: Product: Single RS232-HS usb 1-2.2: Manufacturer: FTDI jffs2: notice: (1) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found. VFS: Mounted root (jffs2 filesystem) readonly on device 31:8. devtmpfs: mounted Freeing unused kernel memory: 156K (c04ef000 - c0516000) INIT: version 2.88 booting INIT: No inittab file found Enter runlevel:
It looks like it is running. Neither Windows or Linux recognize the device port when plugged in. It was working earlier today. Any ideas on what to try next?
November 10, 2015 at 8:35 am #9877Jeff Hatch
KeymasterJonathan,
Have you tried entering the runlevel at the prompt? Run level 5 is a common level for most things to run in normal configuration. If that does not work you may be required to re-flash the device from the boot loader. It appears that your inittab got corrupted or removed somehow.
Jeff Hatch
November 10, 2015 at 11:13 am #9882Jonathan Pickett
ParticipantEnter runlevel: 5 INIT: Entering runlevel: 5 INIT: no more processes left in this runlevel
The device port is still unresponsive.
Are there instructions for reflashing the device?
November 10, 2015 at 11:33 am #9883Brandon Bayer
BlockedJonathan,
Use the U-boot instructions on the second half of this page:
-Brandon
November 10, 2015 at 12:54 pm #9884Jonathan Pickett
ParticipantI am in U-Boot and my environment is showing that my U-Boot environment is not configured for flashing:
U-Boot> printenv baudrate=115200 bootargs=mem=256M console=ttyS0,115200 root=/dev/mtdblock8 ro rootfstype=jffs2 bootcmd=nboot.jffs2 ${loadaddr} 0 ${kernel_addr}; bootm ${loadaddr} bootdelay=0 ethact=macb0 ethaddr=00:08:00:4a:01:6f filesize=EE0 hostname=AT91SAM9G25 ipaddr=192.168.2.1 kernel_addr=0x200000 loadaddr=0x22000000 nand_erasesize=20000 nand_oobsize=40 nand_writesize=800 netmask=255.255.255.0 serverip=192.168.2.2 stderr=serial stdin=serial stdout=serial
I have downloaded the uboot-setenv-mtcdt script. How do I get the script to the device? The instructions are a little vague at that point.
November 10, 2015 at 2:01 pm #9886Jeff Hatch
KeymasterDepending on which terminal program you are using, you can import the script and run it through your terminal program. If you don’t have something like minicom that supports this, then you can revert to cut and pasting the setenv commands in the script.
For example, in minicom you can do a CTRL-A Z, G and point minicom to the script you want to run at the prompt in the menu.
Jeff
-
AuthorPosts
- You must be logged in to reply to this topic.