Daniel Åvall

Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • in reply to: Problem getting mLinux on Conduit 300 #32811
    Daniel Åvall
    Participant

    I got it back to original state! 🙂

    To reset the environment variables to default values in u-boot I ran this:

    env default -a
    saveenv
    reset
    in reply to: Problem getting mLinux on Conduit 300 #32798
    Daniel Åvall
    Participant

    I tried that:
    => setenv partition_swap_f 1
    => boot
    Unknown command ‘nboot.jffs2’ – try ‘help’

    That’s the same error when booting normally (partition_swap_f = 0)
    => printenv
    ..
    bootcmd=nboot.jffs2 ${loadaddr} 0 ${kernel_addr} && bootm ${loadaddr}
    ..

    That’s probably my fault, when trying the u-boot flash instructions I ran this file: http://git.multitech.net/cgi-bin/cgit.cgi/meta-multitech-atmel.git/plain/contrib/uboot-setenv-mtcdt.minicom

    Maybe the partitions are intact, but only wrong u-boot environment variables. Do you know the default values?

    in reply to: Problem getting mLinux on Conduit 300 #32796
    Daniel Åvall
    Participant

    Thanks, that would explain it. No, I don’t have any special layers for Conduit 300, I naively assumed mLinux would work if it had mPower installed. Are you planning on adding support for it?

    In the meanwhile I’ll construct a opkg package with our custom stuff that I can install on the Conduit 300.

    How would I go about to recover a Conduit 300 that only boots into u-boot?

Viewing 3 posts - 1 through 3 (of 3 total)