• Hello,
    When I run the deploy script , I get the following error:


    Entering steppingstone
    Erasing flash
    Sending uboot image for steppingstone
    Please patient, this can take a while...
    4096+0 records in
    4096+0 records out
    262144 bytes (262 kB) copied, 260,71 seconds, 1,0 kB/s
    *ERR*
    Error: Timeout waiting for board.


    The script seems to wait for a responds from the board after sending the uboot.ss file:"Type 'f' to save" but this it is not received?
    Can you help me to solve this problem ? Do you have documentation about the F&S Nand loader ?


    Thnx,

  • We also noticed the same problem here.
    I suppose your are running the VirtualBox Image that has been offered with the Linux CD.


    Unfortunatly the problem seems to be that the virtualbox generates some transmission errors.
    Nboot is waiting for a predefined amount of bytes on the serial line. When there are lost some characters nboot is still waiting for receiption until the deployment script generates a timeout error.
    I have also found a bug entry on the virtualbox homepage that might correspond to this problem:
    <!-- m --><a class="postlink" href="http://www.virtualbox.org/ticket/1548">http://www.virtualbox.org/ticket/1548</a><!-- m -->
    I have tesed it with VirtualBox 3.2.8 without success. Also changing the serial port settings in the VirtualBox does not solve this problem.


    On a "regular" linux system the script might work well I suppose.


    An alternative for the deplyment script is installing Uboot manually. To do so please enter Nboot menu (sometimes also called steppingstone loder) by sending small "s" when powering on PicoCOM.
    Afterwards press "E" to erase the Nand flash.
    Then press "d" to start serial download. Nboot may now wait to receive the Nboot image over serial line. Use a terminal programm (e.g. DCUTerm) and send the uboot.ss file. After the file hase been transfered completly Nboot will offer some addiotional commands to save and start the image. Please press "f" to save UBoot peramently.
    After restarting the module UBoot should bootup correctly.
    In fact these are the same steps the deplyoment script arranges automatically.

    Software developer, F&amp;S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

  • Hi,


    I succeeded to put the uboot and the kernel on the board.
    This is what i see on when the board boots:
    ]
    U-Boot 1.3.3 (Jun 12 2008 - 14:44:43)


    PicoCOM1 (c) 2008 emlix GmbH


    I2C: ready
    DRAM: 32 MB
    NAND: 32 MiB
    *** Warning - bad CRC or NAND, using default environment


    WDC: disabled
    In: serial
    Out: serial
    Err: serial
    Net: macb0
    macb0: link down (status: 0x7849)
    Hit any key to stop autoboot: 0


    Loading from NAND 32MiB 3,3V 8-bit, offset 0x100000
    Image Name: emlix gmbh - F+S PicoCOM1
    Created: 2008-06-12 15:00:37 UTC
    Image Type: ARM Linux Kernel Image (gzip compressed)
    Data Size: 1418809 Bytes = 1.4 MB
    Load Address: 20008000
    Entry Point: 20008000
    ## Booting kernel from Legacy Image at 21000000 ...
    Image Name: emlix gmbh - F+S PicoCOM1
    Created: 2008-06-12 15:00:37 UTC
    Image Type: ARM Linux Kernel Image (gzip compressed)
    Data Size: 1418809 Bytes = 1.4 MB
    Load Address: 20008000
    Entry Point: 20008000
    Verifying Checksum ... OK
    Uncompressing Kernel Image ... OK


    Starting kernel ...


    Linux version 2.6.25-Eval-BSP-1.0 (root@kserv) (gcc version 4.2.4 (Emlix Linux PicoCOM1 Eval-BSP-1.0)) #1 PREEMPT Thu Jun 12 14:33:57 UTC 2008
    CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
    Machine: PicoCOM1 - AT91SAM9260 based
    Memory policy: ECC disabled, Data cache writeback
    Clocks: CPU 198 MHz, master 99 MHz, main 18.432 MHz
    CPU0: D VIVT write-back cache
    CPU0: I cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
    CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
    Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
    Kernel command line: console=ttyS1,38400,8n1 root=/dev/mtdblock4 rootfstype=jffs2
    AT91: 96 gpio irqs in 3 banks
    PID hash table entries: 128 (order: 7, 512 bytes)
    Console: colour dummy device 80x30
    Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
    Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
    Memory: 32MB = 32MB total
    Memory: 29452KB available (2692K code, 201K data, 92K init)
    SLUB: Genslabs=12, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1
    Mount-cache hash table entries: 512
    CPU: Testing write buffer coherency: ok
    net_namespace: 152 bytes
    NET: Registered protocol family 16
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    NET: Registered protocol family 2
    IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
    TCP established hash table entries: 1024 (order: 1, 8192 bytes)
    TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
    TCP: Hash tables configured (established 1024 bind 1024)
    TCP reno registered
    audit: initializing netlink socket (disabled)
    type=2000 audit(0.382:1): initialized
    JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
    fuse init (API version 7.9)
    io scheduler noop registered
    io scheduler anticipatory registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    atmel_usart.0: ttyS0 at MMIO 0xfffb4000 (irq = 7) is a ATMEL_SERIAL
    enable RS485 on port0...done
    atmel_usart.1: ttyS1 at MMIO 0xfffb8000 (irq = 8) is a ATMEL_SERIAL
    console [ttyS1] enabled
    atmel_usart.2: ttyS2 at MMIO 0xfffb0000 (irq = 6) is a ATMEL_SERIAL
    ssc ssc.0: Atmel SSC device at 0xc2868000 (irq 14)
    F&S I/O Driver loaded (fsio char devices major nr. 60)
    picocom_adc: ADC with 3 ports on fsio6 ready
    MACB_mii_bus: probed
    eth0: Atmel MACB at 0xfffc4000 irq 21 (00:05:51:01:90:f5)
    eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:00, irq=-1)
    NAND device: Manufacturer ID: 0xec, Chip ID: 0x75 (Samsung NAND 32MiB 3,3V 8-bit)
    AT91 NAND: 8-bit, Software ECC
    Scanning device for bad blocks
    Creating 5 MTD partitions on "at91_nand":
    0x00008000-0x00048000 : "U-boot Bootloader"
    0x00048000-0x00050000 : "U-Boot Environment"
    0x00050000-0x00100000 : "User Block"
    0x00100000-0x00280000 : "Kernel raw"
    0x00280000-0x02000000 : "User Block targetfs"
    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
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 2 ports detected
    mice: PS/2 mouse device common for all mice
    i2c /dev entries driver
    pcf8563 0-0051: chip found, driver version 0.4.2
    pcf8563 0-0051: rtc core: registered pcf8563 as rtc0
    i2c-gpio i2c-gpio: using pins 23 (SDA) and 24 (SCL)
    at91sam9_wdt: Watchdog register already programmed.
    at91_mci: Card detect thread activated
    usbcore: registered new interface driver usbhid
    drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
    TCP cubic registered
    NET: Registered protocol family 1
    NET: Registered protocol family 17
    NET: Registered protocol family 15
    can: controller area network core (rev 20071116 abi 8)
    NET: Registered protocol family 29
    can: raw protocol (rev 20071116)
    can: broadcast manager protocol (rev 20071116)
    RPC: Registered udp transport module.
    RPC: Registered tcp transport module.
    registered taskstats version 1
    pcf8563 0-0051: low voltage detected, date/time is not reliable.
    pcf8563 0-0051: retrieved date/time is not valid.
    pcf8563 0-0051: hctosys: invalid date/time
    VFS: Mounted root (jffs2 filesystem) readonly.
    Freeing init memory: 92K
    Warning: unable to open an initial console.
    Kernel panic - not syncing: No init found. Try passing init= option to kernel.



    Any idea ?

  • Quote from "televic"

    *** Warning - bad CRC or NAND, using default environment


    U-Boot uses the default environment. This might not be suited for your purposes. Usually you have to set environment variable bootargs to a linux command line that suits your needs.


    Quote

    Kernel panic - not syncing: No init found. Try passing init= option to kernel.


    Well, that's exactly what needs to be done: set the bootargs-Variable in U-Boot to include init= with your specific settings. Please see chapter 12.4 of the PicoCOM1 documentation of what can be set in the bootargs variable.

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.