Mity CPU Platforms » MityDSP-L138 (ARM9 Based Platforms)

Hmmm
It should autoboot into linux. Can you post the output of the u-boot print command
U-Boot > print
And try just typing boot at the prompt
U-Boot > boot
to see if it boots into linux. The bootcmd environment variable should be set to
"sf probe 0; sf read 0xc0700000 0x100000 0x280000;bootm 0xc0700000"
to boot from SPI NOR flash.

cheers
/Tim

The output of print:

U-Boot > print
    bootdelay=3
    baudrate=115200
    bootfile="uImage" 
    flashuboot=tftp 0xc0700000 mityomap/u-boot-ubl.bin; sf probe 0; sf erase 0x10000 0x80000; sf write 0xc0700000 0x10000 ${filesize}
    flashkernel=tftp 0xc0700000 mityomap/uImage; sf probe 0; sf erase 0x100000 0x280000; sf write 0xc0700000 0x100000 ${filesize}
    flashubl=tftp 0xc0700000 mityomap/UBL_SPI_MEM.ais; sf probe 0; sf erase 0 0x10000; sf write 0xc0700000 0 0x10000
    flashrootfs=tftp 0xc2000000 mityomap/mityomap-base-mityomapl138.jffs2; nand erase 0 0x08000000; nand write.jffs2 0xc2000000 0 ${filesize}
    serverip=10.0.0.23
    autoload=no
    mtdids=nand0=nand
    mtdparts=mtdparts=nand:128M(rootfs),-(userfs)
    bootargsbase=mem=96M console=ttyS1,115200n8
    flashargs=setenv bootargs ${bootargsbase} ${mtdparts} root=/dev/mtdblock0 rw,noatime rootfstype=jffs2
    stdin=serial
    stdout=serial
    stderr=serial
    ethaddr=00:50:c2:bf:8e:12
    ver=U-Boot 2009.11 (Mar 31 2011 - 19:39:18)

Environment size: 905/65532 bytes
    U-Boot >

The (non)-result of boot:

U-Boot > boot
    U-Boot >

I tried setting the bootcmd variable as suggested and the executed boot. This is what I got:

U-Boot > editenv bootcmd
    edit: sf probe 0; sf read 0xc0700000 0x100000 0x280000;bootm 0xc0700000
    U-Boot > printenv bootcmd
    bootcmd=sf probe 0; sf read 0xc0700000 0x100000 0x280000;bootm 0xc0700000
    U-Boot > boot
    8192 KiB M25P64 at 0:0 is now current device
    Wrong Image Format for bootm command
    ERROR: can't get kernel image!
    U-Boot >

Because of a purchasing SNAFU on our side, we got the board a week late. The project isn't very long so I'm anxious to get basic Linux up and an app running on the DSP.

Hi,

Are you booting on an Industrial I/O (development kit) board? If so, we can walk you through installing the kernel and filesystem (do you want to run from NAND, or SD?). The process shouldn't take very long and flashing up the kernel and the root filesystem is documented on the Wiki pages.

Are you developing using the virtual box image provided? If so, the image should contain the files you need to flash up the unit.

-Mike

Yes, I'm using the Industrial I/O dev kit. I'm using the virtual box image provided.

Mike, I'd love your help walking me through this. Give me a number and I'll call. If you have Skype, I'll share my screen.

I tried TFTP. First I checked that it was enabled and to see what directory it is sharing:

mitydsp@mitydsp-dev:~/tftpd$ grep -i tftp /etc/inetd.conf 
    #:BOOT: TFTP service is provided primarily for booting.  Most sites
    tftp        dgram    udp    wait    root    /usr/sbin/tcpd    /usr/sbin/in.tftpd /home/mitydsp/tftpd

Then, I placed the uImage file in the tftpd directory under ~mitydsp:

mitydsp@mitydsp-dev:~/projects/linux-davinci/arch/arm/boot$ cp uImage /home/mitydsp/tftpd/
    mitydsp@mitydsp-dev:~/projects/linux-davinci/arch/arm/boot$ cd /home/mitydsp/tftpd/
    mitydsp@mitydsp-dev:~/tftpd$ ls
    u-boot-ubl.bin  uImage
    mitydsp@mitydsp-dev:~/tftpd$ chmod 777 uImage 
    mitydsp@mitydsp-dev:~/tftpd$ ls
    u-boot-ubl.bin  uImage
    mitydsp@mitydsp-dev:~/tftpd$ ls -l
    total 2384
    -rwxrwxrwx 1 mitydsp mitydsp  260588 2011-04-08 14:44 u-boot-ubl.bin
    -rwxrwxrwx 1 mitydsp mitydsp 2177284 2012-07-23 20:04 uImage

Then I tried TFTP booting from u-Boot:

U-Boot > setenv ipaddr 192.168.2.121
    U-Boot > tftp 0xC0700000 192.168.2.120:/uImage
    Using  device
    TFTP from server 192.168.2.120; our IP address is 192.168.2.121
    Filename '/uImage'.
    Load address: 0xc0700000
    Loading: *
    TFTP error: 'Access violation' (2)
    Starting again
    Using  device
    TFTP from server 192.168.2.120; our IP address is 192.168.2.121
    Filename '/uImage'.
    Load address: 0xc0700000
    Loading: T T T T T T T T T T T T T T T T T T T T
    Retry count exceeded; starting again

That's where I stand. Let me know if we can try tonight. If we cannot try tonight, I'd like to schedule a time with you tomorrow.

--Jeff

Hi Jeff,

Is your VM network adaptor set to be a "bridged" connection and not a "NAT"?. Can you ping your VM IP address frmo the MityDSP? E.g., on your VM do an "ifconfig -a" and confirm the address is 192.168.2.120 and on the MityDSP you can "ping 192.168.1.120".

Let's set up a time tomorrow, would you be willing to use Goto Meeting? We have an account and I should be able to host a meeting. This would allow me to see you setup and get you going the quickest.

I would be available to start a meeting between 7-8:30 AM and 11-3:30 PM EST.

-Mike

Virtual Box is in "bridged" mode - see attached, with the following network configuration for mitydsp-dev:

    
mitydsp@mitydsp-dev:~/tftpd$ ifconfig -a
eth0      Link encap:Ethernet  HWaddr 08:00:27:2c:be:23  
          inet addr:192.168.2.120  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fe2c:be23/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:625204 errors:0 dropped:0 overruns:0 frame:0
          TX packets:315907 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:938776595 (938.7 MB)  TX bytes:21184845 (21.1 MB)

The MityDSP target can ping the development VM:

U-Boot > setenv ipaddr 192.168.2.121
U-Boot > ping 192.168.2.120
Using  device
host 192.168.2.120 is alive
U-Boot >

Hi,

We also have received a batch of Mity1808 cards which have not been programmed with kernel. We are able to programme a kernel and filesystem onto these cards - so no immediate problems. However we are not sure as to what to expect their default configuration to be (The cards were purchased without development kit).

Receiving them without a kernel and file system is not too bad, but would we ever expect to receive boards without a version u-boot ?

Hi Keith,

If you purchased the cards without a development kit then it is expected that they come only with u-boot installed. All of the cards purchased from us will have at least u-boot installed.

\Greg

Hi everyone, I'm starting with the PROFIBUS development kit and I was trying to follow the starter guide until I came to the boot up in linux step just like Jeff

I have Enabled the serial port from VBox and configured the port mode like "HostDevice".

I got mi MityDSP hooked up with the Serial cable to my PC serial port, and plugged up, the "Power good led" is strong green, I'm in the mitydsp VM but I don't have any response.

1.- Should the target autoboot in Linux or what should I do for booting it?

2.- About the U-Boot commands that you post above, should I type them in an specific directory? //// I have type them in main terminal and I got a command not found message.

I have checked the state of the Serial port with dsmeg | grep tty in the VM, and in the host Windows machine in the Device Manager, it looked all to be OK,

3.- Should the MityDSP connection be detected on my Host machine serial devices or that is not expected? ///// Just like reference for knowing that the serial port is working properly.

I hope you can guide me in the right way, thanks!

Hector, I'm going to respond in your other forum post.
https://support.criticallink.com/redmine/boards/10/topics/4825