Find the answer to your Linux question:
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 11
Hello Members, Can any one please explain me that how can we access the in built memory to save our program on embedded Linux based cobra5329 board support package which ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Jul 2011
    Posts
    18

    how to Acess memory in embedded linux Based cobra5329 BSP ??


    Hello Members,

    Can any one please explain me that how can we access the in built memory to save our program on embedded Linux based cobra5329 board support package which is based on MCF5329 coldfire processor.

    Also there is option to put extra memory card into the board . How Can I access this and save my program on to it because every time I shut down my system I have to download the program again to my board. This is too much time consuming and also rubbish !

    There is no manual support comes with this board that how to do this . Can any one please explain me and guide me about this.

    Thanks

  2. #2
    Trusted Penguin
    Join Date
    May 2011
    Posts
    4,353
    Quote Originally Posted by zawii87 View Post
    Hello Members,

    Can any one please explain me that how can we access the in built memory to save our program on embedded Linux based cobra5329 board support package which is based on MCF5329 coldfire processor.
    By built-in memory, do you mean the on-board Flash memory (typically 16MB upgradable to 64MB)? That should be as easy as just saving files directly to the filesystem.

    Also there is option to put extra memory card into the board . How Can I access this and save my program on to it because every time I shut down my system I have to download the program again to my board.
    I assume it is an SDCard interface? If so, when you insert the card, a block device should be created for it by the kernel (hopefully) and will appear as /dev/mmcblk0 or something. Look at the output of dmesg after you insert it. On one of my ARM boards, my SD Card was represented as /dev/mmcblk0 and the first partition was mccblk0p1, which I formatted as VFAT.

    Once I had a mountable partition, it was as simple as putting this in /etc/fstab:
    Code:
    /dev/mmcblk0p1 /mnt/sdcard vfat defaults 1 2
    Make sure the dir exists:
    Code:
    mkdir -p /mnt/sdcard
    Then test it out:
    Code:
    mount -a
    That should mount the card (if that is truly the device name and it is formatted, etc.).

    hth

  3. #3
    Just Joined!
    Join Date
    Jul 2011
    Posts
    18
    yes talking about the in built flash memory on the board . How to access it and how to store my downloaded application to my in built flash memory ?

    The file system in the "dev" folder appears like this

    # ls
    zero ttyp3 sda1 ram3 ptyp5 mtdr0 mem
    urandom ttyp2 sda ram2 ptyp4 mtdblock6 kmem
    ttypf ttyp1 rtc ram1 ptyp3 mtdblock5 i2c0
    ttype ttyp0 rom9 ram0 ptyp2 mtdblock4 fb0
    ttypd ttyS1 rom8 ptypf ptyp1 mtdblock3 cua1
    ttypc ttyS0 rom7 ptype ptyp0 mtdblock2 cua0
    ttypb tty3 rom6 ptypd psaux mtdblock1 console
    ttypa tty2 rom5 ptypc null mtd6 can0
    ttyp9 tty1 rom4 ptypb mtdr6 mtd5 adc1
    ttyp8 tty0 rom3 ptypa mtdr5 mtd4 adc0
    ttyp7 tty rom2 ptyp9 mtdr4 mtd3 mtdblock0
    ttyp6 sda4 rom1 ptyp8 mtdr3 mtd2
    ttyp5 sda3 rom0 ptyp7 mtdr2 mtd1
    ttyp4 sda2 random ptyp6 mtdr1 mtd0



    Also there is an MMC card slot in the board and when i insert it the the file list in the dev folder remains same as I checked

    # ls
    zero ttyp3 sda1 ram3 ptyp5 mtdr0 mem
    urandom ttyp2 sda ram2 ptyp4 mtdblock6 kmem
    ttypf ttyp1 rtc ram1 ptyp3 mtdblock5 i2c0
    ttype ttyp0 rom9 ram0 ptyp2 mtdblock4 fb0
    ttypd ttyS1 rom8 ptypf ptyp1 mtdblock3 cua1
    ttypc ttyS0 rom7 ptype ptyp0 mtdblock2 cua0
    ttypb tty3 rom6 ptypd psaux mtdblock1 console
    ttypa tty2 rom5 ptypc null mtd6 can0
    ttyp9 tty1 rom4 ptypb mtdr6 mtd5 adc1
    ttyp8 tty0 rom3 ptypa mtdr5 mtd4 adc0
    ttyp7 tty rom2 ptyp9 mtdr4 mtd3 mtdblock0
    ttyp6 sda4 rom1 ptyp8 mtdr3 mtd2
    ttyp5 sda3 rom0 ptyp7 mtdr2 mtd1
    ttyp4 sda2 random ptyp6 mtdr1 mtd0

    the output of the dmsg looks like this

    Linux version 2.6.17-uc0 (root@bserv) (gcc version 3.4.3 (Emlix Linux 3.4.3-6))
    #1 Tue Nov 14 12:34:36 UTC 2006


    uClinux/COLDFIRE(m532x)
    COLDFIRE port done by Greg Ungerer, gerg@snapgear.com
    Flat model support (C) 1998,1999 Kenneth Albanowski, D. Jeff Dionne
    On node 0 totalpages: 4064
    Normal zone: 4064 pages, LIFO batch:0
    Built 1 zonelists
    Kernel command line: rootfstype=romfs console=tty1 console=ttyS0,115200 video=m5
    32xfb:mode:320x240@60,yres_virt:720
    PID hash table entries: 64 (order: 6, 256 bytes)
    Console: colour dummy device 80x25
    Dentry cache hash table entries: 2048 (order: 1, 8192 bytes)
    Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
    Memory available: 10240k/16256k RAM, (1546k kernel code, 315k data)
    Calibrating delay loop... 158.92 BogoMIPS (lpj=794624)
    Mount-cache hash table entries: 512
    NET: Registered protocol family 16
    USB-MCF532x: (HOST module) EHCI device is registered
    USB-MCF532x: (OTG module) EHCI device is registered
    SCSI subsystem initialized
    usbcore: registered new driver usbfs
    usbcore: registered new driver hub
    NET: Registered protocol family 2
    IP route cache hash table entries: 128 (order: -3, 512 bytes)
    TCP established hash table entries: 512 (order: -1, 2048 bytes)
    TCP bind hash table entries: 256 (order: -2, 1024 bytes)
    TCP: Hash tables configured (established 512 bind 256)
    TCP reno registered
    JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
    io scheduler noop registered (default)
    Initing M532x Framebuffer
    Console: switching to colour frame buffer device 40x30
    fb0: M532x FB frame buffer device
    ISA-Philips-Basic-CAN memory mapped CAN Driver 3.0_ColdFire_FlexCAN (c) Nov 14 2
    006 12:34:06
    ColdFire internal UART serial driver version 1.00
    ttyS0 at 0xfc060000 (irq = 90) is a builtin ColdFire UART
    ttyS1 at 0xfc064000 (irq = 91) is a builtin ColdFire UART
    RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
    FEC ENET Version 0.2
    fec: PHY @ 0x1, ID 0x20005c90 -- DP83848
    eth0: ethernet ac:de:48:53:29:01
    uclinux[mtd]: RAM probe address=0x401f188c size=0x3e7000
    Creating 1 MTD partitions on "RAM":
    0x00000000-0x003e7000 : "ROMfs"
    uclinux[mtd]: set ROMfs to be root filesystem
    Cobra5329 flash device: 2000000 at 0
    COBRA5329Flash: Found 1 x16 devices at 0x0 in 16-bit bank
    COBRA5329Flash: Found an alias at 0x1000000 for the chip at 0x0
    Amd/Fujitsu Extended Query Table at 0x0040
    COBRA5329Flash: CFI does not contain boot bank location. Assuming top.
    number of CFI chips: 1
    cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
    Creating 3 MTD partitions on "COBRA5329Flash":
    0x00000000-0x00100000 : "bootloader"
    0x00100000-0x00700000 : "kernel"
    0x00700000-0x01000000 : "data"
    QSPI: spi->max_speed_hz 9600000
    QSPI: Baud set to 4
    COLDFIRE-QSPI: probed and master registered
    ADC122S101 registered
    usbmon: debugfs is not available
    MCF532x USB EHCI: is found. ID=0x5 Rev=0x41
    ehci ehci.1: EHCI Host Controller
    ehci ehci.1: new USB bus registered, assigned bus number 1
    ehci ehci.1: irq 176, io mem 0xfc0b4000
    ehci ehci.1: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 1 port detected
    MCF532x USB EHCI: is found. ID=0x5 Rev=0x41
    ehci ehci.0: EHCI Host Controller
    ehci ehci.0: new USB bus registered, assigned bus number 2
    ehci-mcf532x: can't find transceiver!
    ehci ehci.0: can't setup
    ehci ehci.0: USB bus 2 deregistered
    Initializing USB Mass Storage driver...
    usbcore: registered new driver usb-storage
    USB Mass Storage support registered.
    usbcore: registered new driver usbhid
    drivers/usb/input/hid-core.c: v2.6:USB HID core driver
    mice: PS/2 mouse device common for all mice
    i2c /dev entries driver
    x1205 0-006f: chip found, driver version 1.0.7
    x1205 0-006f: rtc intf: dev (254:0)
    x1205 0-006f: rtc core: registered x1205 as rtc0
    TCP bic registered
    NET: Registered protocol family 1
    NET: Registered protocol family 17
    x1205 0-006f: setting the system clock to 2496-12-17 00:20:22 (3744420934)
    VFS: Mounted root (romfs filesystem) readonly.
    Freeing unused kernel memory: 72k freed (0x401bb000 - 0x401cc000)
    eth0: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX.
    VFS: Can't find a romfs filesystem on dev mtdblock3.

  4. $spacer_open
    $spacer_close
  5. #4
    Trusted Penguin
    Join Date
    May 2011
    Posts
    4,353
    Regarding your onboard flash, just try making a directory somewhere (like "mkdir -p /opt/myfiles/") and saving your files there (how you get the on there is another question perhaps - scp, ftp, etc.).

    As to the MMC card:
    1. did you run that dmesg command AFTER you inserted the card?

    2. do you know that this board/kernel supports MMC cards?

    3. do you know that MMC card to be good?

  6. #5
    Just Joined!
    Join Date
    Jul 2011
    Posts
    18
    when I do mkdir it gives me the following reply

    BusyBox v1.00 (2006.11.14-12:36+0000) multi-call binary

    Usage: mkdir [OPTION] DIRECTORY...

    but I don't how to create my own folder to save my file there ??

  7. #6
    Just Joined!
    Join Date
    Jul 2011
    Posts
    18
    Quote Originally Posted by atreyu View Post

    As to the MMC card:
    1. did you run that dmesg command AFTER you inserted the card?

    2. do you know that this board/kernel supports MMC cards?

    3. do you know that MMC card to be good?
    and yes I run the command after inserting MMC card I just again run it and that the output

    # dmesg
    Linux version 2.6.17-uc0 (root@bserv) (gcc version 3.4.3 (Emlix Linux 3.4.3-6))
    #1 Tue Nov 14 12:34:36 UTC 2006


    uClinux/COLDFIRE(m532x)
    COLDFIRE port done by Greg Ungerer, gerg@snapgear.com
    Flat model support (C) 1998,1999 Kenneth Albanowski, D. Jeff Dionne
    On node 0 totalpages: 4064
    Normal zone: 4064 pages, LIFO batch:0
    Built 1 zonelists
    Kernel command line: rootfstype=romfs console=tty1 console=ttyS0,115200 video=m5
    32xfb:mode:320x240@60,yres_virt:720
    PID hash table entries: 64 (order: 6, 256 bytes)
    Console: colour dummy device 80x25
    Dentry cache hash table entries: 2048 (order: 1, 8192 bytes)
    Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
    Memory available: 10240k/16256k RAM, (1546k kernel code, 315k data)
    Calibrating delay loop... 158.92 BogoMIPS (lpj=794624)
    Mount-cache hash table entries: 512
    NET: Registered protocol family 16
    USB-MCF532x: (HOST module) EHCI device is registered
    USB-MCF532x: (OTG module) EHCI device is registered
    SCSI subsystem initialized
    usbcore: registered new driver usbfs
    usbcore: registered new driver hub
    NET: Registered protocol family 2
    IP route cache hash table entries: 128 (order: -3, 512 bytes)
    TCP established hash table entries: 512 (order: -1, 2048 bytes)
    TCP bind hash table entries: 256 (order: -2, 1024 bytes)
    TCP: Hash tables configured (established 512 bind 256)
    TCP reno registered
    JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
    io scheduler noop registered (default)
    Initing M532x Framebuffer
    Console: switching to colour frame buffer device 40x30
    fb0: M532x FB frame buffer device
    ISA-Philips-Basic-CAN memory mapped CAN Driver 3.0_ColdFire_FlexCAN (c) Nov 14 2
    006 12:34:06
    ColdFire internal UART serial driver version 1.00
    ttyS0 at 0xfc060000 (irq = 90) is a builtin ColdFire UART
    ttyS1 at 0xfc064000 (irq = 91) is a builtin ColdFire UART
    RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
    FEC ENET Version 0.2
    fec: PHY @ 0x1, ID 0x20005c90 -- DP83848
    eth0: ethernet ac:de:48:53:29:01
    uclinux[mtd]: RAM probe address=0x401f188c size=0x3e7000
    Creating 1 MTD partitions on "RAM":
    0x00000000-0x003e7000 : "ROMfs"
    uclinux[mtd]: set ROMfs to be root filesystem
    Cobra5329 flash device: 2000000 at 0
    COBRA5329Flash: Found 1 x16 devices at 0x0 in 16-bit bank
    COBRA5329Flash: Found an alias at 0x1000000 for the chip at 0x0
    Amd/Fujitsu Extended Query Table at 0x0040
    COBRA5329Flash: CFI does not contain boot bank location. Assuming top.
    number of CFI chips: 1
    cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
    Creating 3 MTD partitions on "COBRA5329Flash":
    0x00000000-0x00100000 : "bootloader"
    0x00100000-0x00700000 : "kernel"
    0x00700000-0x01000000 : "data"
    QSPI: spi->max_speed_hz 9600000
    QSPI: Baud set to 4
    COLDFIRE-QSPI: probed and master registered
    ADC122S101 registered
    usbmon: debugfs is not available
    MCF532x USB EHCI: is found. ID=0x5 Rev=0x41
    ehci ehci.1: EHCI Host Controller
    ehci ehci.1: new USB bus registered, assigned bus number 1
    ehci ehci.1: irq 176, io mem 0xfc0b4000
    ehci ehci.1: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 1 port detected
    hub 1-0:1.0: 1 port detected
    ehci ehci.0: EHCI Host Controller
    ehci ehci.0: new USB bus registered, assigned bus number 2
    ehci-mcf532x: can't find transceiver!
    ehci ehci.0: can't setup
    ehci ehci.0: USB bus 2 deregistered
    Initializing USB Mass Storage driver...
    usbcore: registered new driver usb-storage
    USB Mass Storage support registered.
    usbcore: registered new driver usbhid
    drivers/usb/input/hid-core.c: v2.6:USB HID core driver
    mice: PS/2 mouse device common for all mice
    i2c /dev entries driver
    x1205 0-006f: chip found, driver version 1.0.7
    x1205 0-006f: rtc intf: dev (254:0)
    x1205 0-006f: rtc core: registered x1205 as rtc0
    TCP bic registered
    NET: Registered protocol family 1
    NET: Registered protocol family 17
    x1205 0-006f: setting the system clock to 2496-12-17 00:20:22 (3744420934)
    VFS: Mounted root (romfs filesystem) readonly.
    Freeing unused kernel memory: 72k freed (0x401bb000 - 0x401cc000)
    eth0: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX.
    VFS: Can't find a romfs filesystem on dev mtdblock3.
    #

    And as far as the support for the kernel is concerned I don't have any idea about it . There is nothing any document comes with it which states
    anything . But if it has MMC slot in it then it should response to it !

    and as far as MMC card, it's just newly opened from the pack

  8. #7
    Trusted Penguin
    Join Date
    May 2011
    Posts
    4,353
    as to the mkdir command, just leave off the "-p" (the busybox version of mkdir probably doesn't support that switch, e.g.:

    mkdir /opt
    mkdir /opt/mydir/

    as to MMC support in the kernel: just b/c the board has an MMC interface does not mean the OS (i.e., kernel) has support - though I agree with you that I does indicate that there is a good chance that it does. can you post a website link to your exact board from the manufacturer or vendor?

    unfortunately, i don't have access to the ARM board that had MMC connectivity so I can't trouble-shoot your problem myself any better.

  9. #8
    Just Joined!
    Join Date
    Jul 2011
    Posts
    18
    Quote Originally Posted by atreyu View Post
    as to the mkdir command, just leave off the "-p" (the busybox version of mkdir probably doesn't support that switch, e.g.:

    mkdir /opt
    mkdir /opt/mydir/
    This happen when I try to rum the upper command


    Usage: mkdir [OPTION] DIRECTORY...

    # mkdir /opt/mkdir
    mkdir: Cannot create directory `/opt/mkdir': Read-only file system

  10. #9
    Trusted Penguin
    Join Date
    May 2011
    Posts
    4,353
    bummer! so their root filesystem is read-only then (or perhaps just /var or /tmp are writable?). I guess you'll have to get the SD Card working. Do you have a mfr link?

  11. #10
    Just Joined!
    Join Date
    Jul 2011
    Posts
    18
    How I need to make MMC card work ...That is the question .
    and what mfr link ...what is this i dont have any idea about it

Page 1 of 2 1 2 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •