Announcement

Collapse
No announcement yet.

Looking for E10 new OS build Beta Testers

Collapse
This is a sticky topic.
X
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Looking for E10 new OS build Beta Testers

    Hello E10 Users,

    EDIT: Newest build at: http://www.jcwoltz.com/e10/e10-1202-20120417014733.zip

    First and Foremost: ***I am not a Synapse Wireless Employee, nor is this supported by Synapse Wireless. I accept no liability for lost data or other damage that may occur from using this***

    With that said, I have not had any damage to my E10 or other devices from running these upgraded builds. This has been tested from a few of my other clients and works for them. I want to open this up to anyone who wants to try out the builds and let me know of any issues they may have. The fixes that comes from any issues that might come up will be integrated back into the builds and released for all to use.

    Background:
    I originally started to customize the OS and software builds for the E10 due to a need for more packages (software) and more driver support for various USB WIFI and USB Cellular modems. I quickly moved to a linux 2.6.38 kernel, but due to needing even more USB Cellular modems I moved to a linux 3.0.4 kernel.

    Current Status:
    There are at least 3 people running this build right now, including me. Snap Connect is working fine for me. The major upgrades from the stock image include:
    • Linux 3.0.4 (stock is 2.6.33)
      • All USB Wifi devices enabled, for more WIFI adapters supported
      • All support (by Linux) for cell modems enabled

    • Buildroot 2011.11-git (stock is buildroot 2010.02)
      • busybox 1.19.2
      • built with gcc 4.6.x
      • All cpu optimizations turned on (arm926t instead of arm_generic)
      • Built as EABI instead of OABI
      • uClibc 0.9.32.x
      • binutils 2.21.1
      • Python 2.7.2 (instead of Python 2.6.6)
      • dbus and udev for dynamic device allocation and /dev creation
      • wireless tools including wpa_supplicant (I include an example /etc/wpa_supplicant.conf so you can easily modify for your wireless network)
      • usb_modeswitch (used to switch usb cell modems from fake cdroms into their modem mode)
      • Extra utils: bwm-ng, cups, iperf, iptables (for setting up firewall), ntp (for clock synchronization), rsync (for remote backups, or keeping multiple E10s in sync), opensshd (instead of dropbear, allows for scp of files), dialog, screen, and htop.

    • I have made some custom scripts to help with certain functions:
      • /etc/network/pre-wlan.sh (this will make sure wlan0 exists, make sure wpa_supplicant connects/associates, then start dhcp client)
      • misc scripts in root/scripts/
        • check-net.sh checks for internet connectivity. This is used by other scripts to tell if the E10 can talk to the internet. This will be tied into a script to automatically down and re-up wifi and cellular connections
        • cron scripts to run hourly, daily, weekly, and monthly. Easily modified for your own purposes



    *EDIT* 201201050927 This has been fixed.
    There is *ONE* thing that does not work right now. It is the push button on the E10. If you use the gpio9260 program to read the PB10, I am trying to find another way to read the push button. If you do not use the push button, then this will not be an issue right now. The gpio9260 program was compiled with old software and I do not have the code to re-compile it.

    See Jonathan's post below. He just posted the snap connect for python 2.7. It works on the E10.

    If you have ever done an "E10 Recovery", I have made a simpler and quicker way to upgrade.

    Please reply (or email me) if you are interested in testing out this build. I would like a couple more people to try it and post any issues (if there are some), and I will fix and repost.

    Thank you,
    J.C. Woltz

    *EDIT* There had have been updated builds, and other updates. I will do my best to keep this up to date.
    Last edited by jcwoltz; 04-16-2012, 07:58 PM. Reason: adding note about snap connect files below

  • #2
    Attached is a copy of the compiled SNAP Connect files to work with JC's update.

    This will work on the E10 without any issues.
    However, you'll need to purchase a license to operate on other platforms (PC or embedded).
    Attached Files
    sigpic
    Proven Solutions for the Internet of Things
    www.synapse-wireless.com

    Comment


    • #3
      Info from dmesg and busybox

      Output from Various commands on this build:
      Code:
      Linux version 3.0.4 (jcwoltz@g999) (gcc version 4.6.1 (Buildroot 2011.11-git-g05b6176) ) #1 Sat Oct 15 17:52:51 EDT 2011
      CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
      CPU: VIVT data cache, VIVT instruction cache
      Machine: Synapse Wireless Connect-E10
      Memory policy: ECC disabled, Data cache writeback
      On node 0 totalpages: 16384
      free_area_init_node: node 0, pgdat c044ae64, node_mem_map c0465000
       Normal zone: 128 pages used for memmap
       Normal zone: 0 pages reserved
       Normal zone: 16256 pages, LIFO batch:3
      Clocks: CPU 399 MHz, master 133 MHz, main 12.000 MHz
      pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
      pcpu-alloc: [0] 0
      Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
      Kernel command line: console=ttyS0,115200 root=/dev/mtdblock1 mtdparts=atmel_nand:16M(kernel)ro,120M(rootfs),4M(kernel2),16M(recovery),-(logs) rw rootfstype=jffs2
      PID hash table entries: 256 (order: -2, 1024 bytes)
      Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
      Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
      Memory: 64MB = 64MB total
      Memory: 60428k/60428k available, 5108k reserved, 0K highmem
      Virtual kernel memory layout:
         vector  : 0xffff0000 - 0xffff1000   (   4 kB)
         fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
         DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
         vmalloc : 0xc4800000 - 0xfee00000   ( 934 MB)
         lowmem  : 0xc0000000 - 0xc4000000   (  64 MB)
         modules : 0xbf000000 - 0xc0000000   (  16 MB)
           .init : 0xc0008000 - 0xc0025000   ( 116 kB)
           .text : 0xc0025000 - 0xc041e0b4   (4069 kB)
           .data : 0xc0420000 - 0xc044b7e0   ( 174 kB)
            .bss : 0xc044b804 - 0xc0464a28   ( 101 kB)
      NR_IRQS:192
      AT91: 96 gpio irqs in 3 banks
      Console: colour dummy device 80x30
      console [ttyS0] enabled
      Calibrating delay loop... 199.06 BogoMIPS (lpj=995328)
      pid_max: default: 32768 minimum: 301
      Mount-cache hash table entries: 512
      CPU: Testing write buffer coherency: ok
      devtmpfs: initialized
      NET: Registered protocol family 16
      AT91: Power Management
      AT91: Starting after software reset
      bio: create slab <bio-0> at 0
      SCSI subsystem initialized
      usbcore: registered new interface driver usbfs
      usbcore: registered new interface driver hub
      usbcore: registered new device driver usb
      i2c-gpio i2c-gpio: using pins 55 (SDA) and 56 (SCL)
      cfg80211: Calling CRDA to update world regulatory domain
      Switching to clocksource pit
      NET: Registered protocol family 2
      IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
      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.
      NetWinder Floating Point Emulator V0.97 (double precision)
      JFFS2 version 2.2. (NAND) (SUMMARY)  \xffffffc2\xffffffa9 2001-2006 Red Hat, Inc.
      msgmni has been set to 118
      io scheduler noop registered
      io scheduler cfq registered (default)
      atmel_usart.0: ttyS0 at MMIO 0xfefff200 (irq = 1) is a ATMEL_SERIAL
      atmel_usart.1: ttyS1 at MMIO 0xfffb0000 (irq = 6) is a ATMEL_SERIAL
      atmel_usart.2: ttyS2 at MMIO 0xfffb4000 (irq = 7) is a ATMEL_SERIAL
      brd: module loaded
      loop: module loaded
      atmel_nand atmel_nand: No DMA support for NAND access.
      NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-b
      it)
      Scanning device for bad blocks
      Bad eraseblock 582 at 0x0000048c0000
      Bad eraseblock 683 at 0x000005560000
      Bad eraseblock 1252 at 0x000009c80000
      Bad eraseblock 1550 at 0x00000c1c0000
      5 cmdlinepart partitions found on MTD device atmel_nand
      Creating 5 MTD partitions on "atmel_nand":
      0x000000000000-0x000001000000 : "kernel"
      0x000001000000-0x000008800000 : "rootfs"
      0x000008800000-0x000008c00000 : "kernel2"
      0x000008c00000-0x000009c00000 : "recovery"
      0x000009c00000-0x000010000000 : "logs"
      MACB_mii_bus: probed
      eth0: Atmel MACB at 0xfffc4000 irq 21 (00:1c:2c:4c:70:bd)
      eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:01, irq=-1)
      usbcore: registered new interface driver asix
      usbcore: registered new interface driver cdc_ether
      usbcore: registered new interface driver net1080
      usbcore: registered new interface driver rndis_host
      usbcore: registered new interface driver cdc_subset
      usbcore: registered new interface driver zaurus
      cdc_ncm: 01-June-2011
      usbcore: registered new interface driver cdc_ncm
      usbcore: registered new interface driver rtl8187
      usbcore: registered new interface driver rtl8192cu
      usbcore: registered new interface driver rndis_wlan
      usbcore: registered new interface driver rt2500usb
      usbcore: registered new interface driver rt73usb
      usbcore: registered new interface driver rt2800usb
      usbmon: debugfs is not available
      ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
      at91_ohci at91_ohci: AT91 OHCI
      at91_ohci at91_ohci: new USB bus registered, assigned bus number 1
      at91_ohci at91_ohci: irq 20, io mem 0x00500000
      hub 1-0:1.0: USB hub found
      hub 1-0:1.0: 2 ports detected
      Initializing USB Mass Storage driver...
      usbcore: registered new interface driver usb-storage
      USB Mass Storage support registered.
      udc: at91_udc version 3 May 2006
      mousedev: PS/2 mouse device common for all mice
      input: gpio-keys as /devices/platform/gpio-keys/input/input0
      rtc-m41t80 0-0068: chip found, driver version 0.05
      rtc-m41t80 0-0068: rtc core: registered m41t81 as rtc0
      cpuidle: using governor ladder
      Registered led device: redled
      Registered led device: greenled
      usbcore: registered new interface driver usbhid
      usbhid: USB HID core driver
      TCP cubic registered
      NET: Registered protocol family 17
      802.1Q VLAN Support v1.8
      lib80211: common routines for IEEE802.11 drivers
      lib80211_crypt: registered algorithm 'NULL'
      rtc-m41t80 0-0068: setting system clock to 2011-10-16 18:02:11 UTC (1318788131)
      usb 1-1: new full speed USB device number 2 using at91_ohci
      VFS: Mounted root (jffs2 filesystem) on device 31:1.
      lib80211: common routines for IEEE802.11 drivers
      lib80211_crypt: registered algorithm 'NULL'
      rtc-m41t80 0-0068: setting system clock to 2011-10-16 18:02:11 UTC (1318788131)
      usb 1-1: new full speed USB device number 2 using at91_ohci
      VFS: Mounted root (jffs2 filesystem) on device 31:1.
      devtmpfs: mounted
      Freeing init memory: 116K
      udevd[493]: starting version 173
      ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
      ieee80211 phy0: hwaddr 00:14:d1:eb:d3:eb, RTL8187BvE V0 + rtl8225z2, rfkill mask 2
      rtl8187: Customer ID is 0x00
      Registered led device: rtl8187-phy0::radio
      Registered led device: rtl8187-phy0::tx
      Registered led device: rtl8187-phy0::rx
      rtl8187: wireless switch is on
      wlan0: authenticate with 3c:ea:4f:60:f7:f1 (try 1)
      wlan0: authenticated
      wlan0: associate with 3c:ea:4f:60:f7:f1 (try 1)
      wlan0: RX AssocResp from 3c:ea:4f:60:f7:f1 (capab=0x431 status=0 aid=4)
      wlan0: associated
      busybox --help
      Code:
      BusyBox v1.19.2 (2011-10-15 17:10:11 EDT) multi-call binary.
      Copyright (C) 1998-2011 Erik Andersen, Rob Landley, Denys Vlasenko
      and others. Licensed under GPLv2.
      See source distribution for full notice.
      
      Usage: busybox [function] [arguments]...
         or: busybox --list[-full]
         or: function [arguments]...
      
              BusyBox is a multi-call binary that combines many common Unix
              utilities into a single executable.  Most people will create a
              link to busybox for each function they wish to use and BusyBox
              will act like whatever it was invoked as.
      
      Currently defined functions:
              [, [[, addgroup, adduser, ar, arping, ash, awk, base64, basename,
              bbconfig, beep, blkid, bunzip2, bzcat, bzip2, cal, cat, catv, chattr,
              chgrp, chmod, chown, chroot, chrt, chvt, cksum, clear, cmp, cp, cpio,
              crond, crontab, cut, date, dc, dd, deallocvt, delgroup, deluser,
              devmem, df, diff, dirname, dmesg, dnsd, dnsdomainname, dos2unix, du,
              dumpkmap, echo, egrep, eject, env, ether-wake, expr, false, fdflush,
              fdformat, fgrep, find, fold, free, freeramdisk, fsck, fuser, getopt,
              getty, grep, groups, gunzip, gzip, halt, hdparm, head, hexdump, hostid,
              hostname, httpd, hwclock, id, ifconfig, ifdown, ifup, inetd, init,
              insmod, install, ip, ipaddr, ipcrm, ipcs, iplink, iproute, iprule,
              iptunnel, kill, killall, killall5, klogd, last, less, linux32, linux64,
              linuxrc, ln, loadfont, loadkmap, logger, login, logname, losetup, ls,
              lsattr, lsmod, lspci, lsusb, lzcat, lzma, makedevs, man, md5sum, mdev,
              mesg, microcom, mkdir, mkfifo, mknod, mkswap, mktemp, modprobe, more,
              mount, mountpoint, mt, mv, nameif, netstat, nice, nohup, nslookup, od,
              openvt, passwd, patch, pidof, ping, pipe_progress, pivot_root,
              poweroff, printenv, printf, ps, pstree, pwd, pwdx, rdate, readlink,
              readprofile, realpath, reboot, renice, reset, resize, rfkill, rm,
              rmdir, rmmod, route, run-parts, runlevel, sed, seq, setarch,
              setconsole, setkeycodes, setlogcons, setserial, setsid, sh, sha1sum,
              sha256sum, sha512sum, sleep, sort, start-stop-daemon, strings, stty,
              su, sulogin, swapoff, swapon, switch_root, sync, sysctl, syslogd, tail,
              tar, tee, telnet, test, tftp, time, top, touch, tr, traceroute, true,
              tty, ttysize, ubimkvol, ubirmvol, ubirsvol, ubiupdatevol, udhcpc,
              umount, uname, uniq, unix2dos, unlzma, unxz, unzip, uptime, users,
              usleep, uudecode, uuencode, vconfig, vi, vlock, watch, watchdog, wc,
              wget, which, who, whoami, whois, xargs, xz, xzcat, yes, zcat

      Comment


      • #4
        Hi, J.C.,

        I would like to test the new E10 OS build. Could you send me instruction/packages about how to do it?

        Thanks,
        Feihong
        fxin@proventix.com

        Comment


        • #5
          Hello,

          The upgrade steps/process is here:
          https://github.com/jcwoltz/E10-build.../documentation

          I need a few hours to upload/post a URL to download the zip file.

          I realize the first time update/upgrade process looks scary, it really is not. It would be simpler if new E10's shipped with an updated U-Boot that supported the "source" command. *NUDGE*

          After the first time running through the upgrade process, any new updates are much easier. They consist of:
          Stop u-boot: type "run upgrade"
          login as root and type "./upgrade.sh"

          The first time upgrade is mostly setting up u-boot environment variables.

          Thank you,
          J.C. Woltz
          Last edited by jcwoltz; 11-04-2011, 12:47 PM.

          Comment


          • #6
            How to install testing E10

            Hello,

            First, you need to know that the upgrade will delete everything on your E10. So please be sure to back up your files. Especially your UserMain.py, as there is no UserMain.py in this distribution. (Not even an example. This is done so that I am not distributing Synapse Wireless Code.) The gpio9260 does not work right now, this only means the push button does not work.

            Please download the Snap*.zip that JHeath posted in the second post of this thread. Save it to a FAT or FAT32 formatted USB drive.

            Then download this file:
            https://www.jcwoltz.com/e10/e10-next-20111105003547.zip

            Extract the e10-next*.zip to the root of the flash drive. So that when you open up your USB drive, you should see these files:
            rootfs.jffs2
            setenv.img
            Snap-2.4.6-py2.7.zip
            uImage
            uImage-e10i

            From there, Please follow the steps outlined here:
            https://github.com/jcwoltz/E10-build.../documentation
            Section 2. How to upgrade the E10
            If you have issues, please report them to the issue tracker at:
            https://github.com/jcwoltz/E10-buildroot/issues
            or email me if you do not have or want to create a github account.

            Thank you for trying this out. I have been running the previous builds without issue.

            If during the upgrade, you get error messages about sda timeout or usb timeout, try a different usb drive.

            Comment


            • #7
              WIFI support

              Here is a quick list of WIFI built in. This list is not complete. There are more wifi drivers built as modules. Some of them require firmware. Since I don't have any of the wifi adapter that require firmware, I can't test/ship that firmware.

              Code:
               CONFIG_RTL8187:
                | This is a driver for RTL8187 and RTL8187B based cards.
                | These are USB based chips found in devices such as:
                |
                | Netgear WG111v2
                | Level 1 WNC-0301USB
                | Micronet SP907GK V5
                | Encore ENUWI-G2
                | Trendnet TEW-424UB
                | ASUS P5B Deluxe/P5K Premium motherboards
                | Toshiba Satellite Pro series of laptops
                | Asus Wireless Link
                | Linksys WUSB54GC-EU v2
                |   (v1 = rt73usb; v3 is rt2070-based,
                |    use staging/rt3070 or try rt2800usb)
              
              CONFIG_RT2500USB:
                |
                | This adds support for rt2500 wireless chipset family.
                | Supported chips: RT2571 & RT2572.
              
              CONFIG_RT73USB:
                |
                | This adds support for rt2501 wireless chipset family.
                | Supported chips: RT2571W, RT2573 & RT2671.
              
              CONFIG_RT2800USB:
                |
                | This adds support for rt27xx/rt28xx/rt30xx wireless chipset family.
                | Supported chips: RT2770, RT2870 & RT3070, RT3071 & RT3072
              
              CONFIG_RT2800USB_RT33XX:
                |
                | This adds support for rt33xx wireless chipset family to the
                | rt2800usb driver.
                | Supported chips: RT3370
              
              CONFIG_RT2800USB_RT53XX:
                |
                | This adds support for rt53xx wireless chipset family to the
                | rt2800pci driver.
                | Supported chips: RT5370
              
              CONFIG_RTL8192CU:
                |
                | This is the driver for Realtek RTL8192CU/RTL8188CU 802.11n USB
                | wireless network adapters.

              Comment


              • #8
                The upgrade process is pretty simple(a lot easier than I expected). It took less than 5 minutes to run the upgrade, and here is what's showing on my e10 now

                # uname -a
                Linux e10-nextc2b1 3.0.8 #1 Fri Nov 4 20:30:47 EDT 2011 armv5tejl GNU/Linux


                Great work, J.C.! I really appreciate all your help. I am playing with the USB adapters now and will test the new version of Snap connect too.

                Thanks,
                Feihong

                Comment


                • #9
                  Using a new image built by J.C.(Thanks a lot!), I have the USB WiFi adapter working,

                  # lsusb
                  Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
                  Bus 001 Device 002: ID 1737:0078 Linksys WUSB100 v2 RangePlus Wireless Network Adapter [Ralink RT3070]

                  # ifconfig
                  eth0 Link encap:Ethernet HWaddr 00:1C:2C:4C:72:C7
                  UP BROADCAST MULTICAST MTU:1500 Metric:1
                  RX packets:0 errors:1 dropped:0 overruns:0 frame:0
                  TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
                  collisions:0 txqueuelen:1000
                  RX bytes:0 (0.0 B) TX bytes:322 (322.0 B)
                  Interrupt:21 Base address:0x4000
                  lo Link encap:Local Loopback
                  inet addr:127.0.0.1 Mask:255.0.0.0
                  UP LOOPBACK RUNNING MTU:16436 Metric:1
                  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
                  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
                  collisions:0 txqueuelen:0
                  RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
                  wlan0 Link encap:Ethernet HWaddr 00:1E:E5:E8:28:1D
                  inet addr:10.200.150.57 Bcast:10.200.150.255 Mask:255.255.255.0
                  UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
                  RX packets:855 errors:0 dropped:244 overruns:0 frame:0
                  TX packets:74 errors:0 dropped:0 overruns:0 carrier:0
                  collisions:0 txqueuelen:1000
                  RX bytes:93461 (91.2 KiB) TX bytes:12956 (12.6 KiB)

                  Also, the new Snap connect for Python 2.7 is wroking fine too. I am going to run more tests and let you all know if I see any problems.

                  Thanks,
                  Feihong

                  Comment


                  • #10
                    Originally posted by feihongxin View Post
                    Using a new image built by J.C.(Thanks a lot!), I have the USB WiFi adapter working,

                    ...

                    Thanks,
                    Feihong
                    Feihong, you are welcome. Thank you for trying this out. We have had a bunch of private conversations, so I want to put this here for the benefit of others.

                    To everyone else:
                    One of the advantages of my build system is someone can clone it (download it), and then make custom images for their own needs. Buildroot (the system that builds all the software and kernel) is a very powerful system. If you need to add certain packages that are not compiled by default, there is a good chance it is an option you can select in buildroot to have built in. Another benefit of the buildroot systems is you can add your own packages. So if you have custom software you need to run on the E10, buildroot not only builds the cross compilers, it can also build you custom application into the E10 OS image. In my opinion, this is a very powerful option.

                    I have put a lot of effort into making the upgrade as painless as possible. As Feihong said earlier, the upgrade process is fairly simple. He said he thought it would be harder than it actually was.

                    *I am not a Synapse Wireless employee, nor am I related to Synapse Wireless in any way (other than a happy customer). I can not accept responsibility for any damage done.* With that said, I have taken every precaution to make sure things work as expected. I have not had any complaints about my builds. So please try out these builds. They will help you.

                    Thank you to everyone who has started using these builds. As your input is important in future improvements.

                    If you need to run custom compiled application on your E10, start off with one of my builds. Then download my repo and compile your own custom build. You will be up and running in no time.

                    Comment


                    • #11
                      J.C.
                      Thanks for doing this - I just found your project, and it looks like it'll save a lot of work.

                      A couple of questions - the upgrade.sh script does not work for me.

                      There is no /dev/mtd0 on my SnapConnect , so all the /mtd0 things fail. There is also no /dev/mtdblock1. (They exist once I boot into our older kernel, but not during the initial stages described in your startup document).

                      I thought I'd try just using kermit to send uImage, but kermit just hangs in U-Boot - basically all the bytes go down, but "loadb" doesn't ever "notice" that the download is done - you probably haven't dealt with this, but I thought i'd put it in here just in case....

                      Comment


                      • #12
                        Originally posted by mquinn View Post
                        J.C.
                        Thanks for doing this - I just found your project, and it looks like it'll save a lot of work.

                        A couple of questions - the upgrade.sh script does not work for me.

                        There is no /dev/mtd0 on my SnapConnect , so all the /mtd0 things fail. There is also no /dev/mtdblock1. (They exist once I boot into our older kernel, but not during the initial stages described in your startup document).
                        OK, so are you downloading one of my zip files, modifying u-boot, and running from there? OR did you build your own image and try to do that. If you are doing the second, I need to document it. I have not documented that at all.

                        Originally posted by mquinn View Post
                        I thought I'd try just using kermit to send uImage, but kermit just hangs in U-Boot - basically all the bytes go down, but "loadb" doesn't ever "notice" that the download is done - you probably haven't dealt with this, but I thought i'd put it in here just in case....
                        Let's start with:
                        I'm sorry for the delay. I just got my power back on. A storm last Friday took out a lot of power in the region.

                        Next, can you please email me a more detail description of what and how you are trying to do. Then we can post back into new thread for others to see/learn. I'm trying to keep this thread as minimal as possible.

                        Thank you,
                        J.C. Woltz

                        Comment


                        • #13
                          Sweet! JC's github repo helped point me in the right direction for getting buildroot-2013.08.1 / Linux-3.10.10 running on my E10:

                          # uname -a
                          Linux e10-buildroot 3.10.10 #10 Fri Oct 11 15:46:37 CDT 2013 armv5tejl GNU/Linux
                          In addition to that, I'm booting the kernel and mounting the root filesystem using NFS from a server running Linux Mint 15. We're looking at doing some funky stuff with our E10 so this will certainly help for development.

                          Thanks for sharing JC!

                          --tim

                          Comment

                          Working...
                          X