AEP Condiut cannot be accessed

Home Forums Conduit: AEP Model AEP Condiut cannot be accessed

Tagged: 

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #16182
    JJ Deng
    Participant

    Hi Forum,
    i start the new thred here to discuss my issue with the AEP Conduit.
    What i did to get that issue:

    1. power on the Gateway.
    2. Only Power LED is on always, there is no any signal of other LEDs. The issue i noticed before opening the Device is, the 3 LEDs were on. As soon as i put my hand on the blue shell of the APE Cnduit device, only PWR LED is on. As soon as i leave my hand away from the device’s shell, 3 LEDs are back.
    3. Connect the USB to the debug port behind the front panel.
    4. Setting the TerraTerm as required.(which did work well before.).
    5. See the USB Serial port available to be connected. Type in User name and pass, click Enter or any other keys. No response. Black screen only.
    5. Push and Hold the reset for(many times, 5s, 30s, 1mins).
    6. Power off the device, power on the device again, reset again and again
    7. nothing changed, only Power LED is on always, No any response from debug port.
    8. Uninstalled the Lora card inside of the device. Tried all the flows above. Same problem.

    In the Device, there are 2 Atane connecters not tied /fixed, I doubt, that they shorted the power or something related, which distroyed the U-Boot?
    Is there any other method to go into U-Boot mode? We got blcoked by that issue.

    Thanks for suggestion in advance.

    Best Regards
    JJ

    #16183
    JJ Deng
    Participant

    Hi *,
    after removal of the Battery and restart the device, i can get the following information via the TeraTerm. And it stacks there without further progressing
    **********************************
    .data : 0xc0518000 – 0xc05407a0 ( 162 kB)
    .bss : 0xc05407a0 – 0xc055f408 ( 124 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 0xc03a9b70 – 0xc03a9bc8
    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 general reset
    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

    #16194
    Jeff Hatch
    Keymaster

    JJ,

    Please open a support portal case at https://support.multitech.com for this. The odd behavior you are seeing with the LEDs when you just touch the device looks like there is something wrong with the board. If this is indeed a defective device, you can get it changed out for a new one.

    Jeff

    #16522
    JJ Deng
    Participant

    Hi Jeff, thanks for reply

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.