Posts by fs-support_DK

  • Problems when using ALSA driver and GStreamer framework

    RTP Audio


    PicoCOM4 is not capable to stream 44100 from alsasrc ([..] This is most likely because downstream can't keep up and is consuming samples too slowly.) Changing to 32000 rate works.
    But using two channels also results in problems (default of L16 is one channel)


    PicoCOM4 as sender:

    Code
    1. gst-launch -v gstrtpbin name=rb alsasrc ! audioconvert ! "audio/x-raw-int,format=S16LE,channels=1,rate=32000" ! rtpL16pay ! rb.send_rtp_sink_0 rb.send_rtp_src_0 ! udpsink host=$IP port=5302 ttl-mc=10 rb.send_rtcp_src_0 ! udpsink host=$IP port=5303 ttl-mc=10 sync=false async=false


    Receiver:

    Code
    1. gst-launch -v gstrtpbin name=rb latency=1000 udpsrc port=5302 caps="application/x-rtp, media=(string)audio, clock-rate=(int)32000, encoding-name=(string)L16, encoding-params=(string)1, channels=(int)1, payload=(int)96" ! rb.recv_rtp_sink_0 rb. ! rtpL16depay ! audioconvert ! alsasink udpsrc port=5303 ! rb.recv_rtcp_sink_0

  • NetDCU14 Starterkit - Serial Ports

    Yes you are right with the connectors.


    ttySAC0 is usable (with RTS/CTS)
    ttySAC1 is used as debug port (and linux serial console)
    ttySAC2 is usable (but there is no level converter on the starterkit)
    ttySAC3 is deactivated (lines are shared with RTS0/CTS0)


    Note:
    in multiplatform-linux-f+s-V2.0 ttySAC0 is not properly configured and is therefore floating. So please find
    NetDCU14-Correct-UART-configuration.-UART0-with-RTS-.patch attached to this post.

  • FrameBuffer

    Please see here:


    <!-- l --><a class="postlink-local" href="http://www.forum.fs-net.de/viewtopic.php?f=55&t=3222">viewtopic.php?f=55&t=3222</a><!-- l -->

  • Remote Debugging

    Hello,


    what platform you are talking about?


    With multiplatform-linux-f+s-V2.0 (PicoMOD7A, NetDCU14 and armStoneA8) we provide Buildroot based RFS with gdbserver included.
    In MultiPlatform-Linux-FirstSteps.pdf document you will find information how to debug in chapter 13+14.

  • PWM Signals

    Hello,


    with multiplatform-linux-f+s-V2.0 you can access backlight brightness for display by:


    Code
    1. # cat /sys/class/backlight/pwm-backlight.0/actual_brightness
    2. 255
    3. # echo 0 > /sys/class/backlight/pwm-backlight.0/brightness


    To use PIFPWM pin (TOUT1 - FS Bus J4 Pin 15) you need to apply attached patch. This will create a pwm-backlight.1 entry in sysfs.
    You can change duty by adjust the brightness value from 0 to 255. To setup frequency you can adjust respective value (.pwm_period_ns) in mach-netdcu14.c and recompile:

    Code
    1. static struct platform_pwm_backlight_data netdcu14_fsbus-pwm_data = {
    2. .pwm_id = 1,
    3. .pwm_period_ns = 1000,
    4. };


    For next release we will provide functionality to setup frequency by SYSFS.


    Please find Activate-TOUT1-PWM.1-via-backlight-system.patch attached to this post.

  • PicoMOD7A/Linux development state and releases

    Multi-Platform Linux V2.0


    We have uploaded a new Linux version to our server. This is the first Multi-Platform Linux Release that supports several boards at the same time. At the moment these are the boards based on Samsung S5PV210 SoC: armStoneA8, NetDCU14 and PicoMOD7a. In the future more boards and also different architectures will be added to this Multi-Platform Release.


    This release is based on an earlier version that was only available on armStoneA8. Therefore the Release Notes below show the modifications in relation to this armStoneA8 version.


    In the download area on our website you'll find two tar archives:


    multiplatform-linux-f+s-V2.0.tar.bz2
    This is the main release itself containing all sources, the binary images, the documentation and the toolchain.


    sd-card-V2.0.tar.bz2
    If you copy the contents of this archive to an SD card, you can install our precompiled standard system in a very straightforward and comfortable way on the board. The SD card archive is meant for people who just want to try a release first without having to download the quite large main archive. Its content is also contained in the main release archive, so if you want to download the main archive anyway, you don't need to bother with the SD card archive.


    These tar archives are compressed with bzip2. So to see the files, you first have to unpack the archives

    Code
    1. tar jxvf multiplatform-linux-f+s-V2.0.tar.bz2


    This will create a directory multiplatform-linux-f+s-V2.0 that contains all the files of the release.


    Please read the file doc/MultiPlatform-Linux-FirstSteps.pdf. It lists the meaning of all files and shows how to install and use everything.



    Release Notes for Multi-Platform Linux V2.0


    This is a major release with lots of changes. It is the first release that supports several boards at once. The boards that are supported through all levels (NBoot, U-Boot, Linux Kernel, BuildRoot) are:


    armStoneA8, NetDCU14, PicoMOD7A


    Please note that you have to update NBoot first to be able to use the automatic installation process described in the FirstSteps document.


    Here is a list of the most noticeable changes in this release.


    NBootV210 (V18) (21.11.2012)
    Supported boards: armStoneA8, NetDCU14, PicoMOD7A


    Changes in V18

    • 0001421: [NBoot] Add ubotv210.nb0 as possible load source
    • 0001428: [NBoot] Ram test not working for 512 MB version
    • 0001426: [NBoot] Small change in SDHC clock calculation


    Changes in V17

    • 0001405: [NBoot] PM7A: Detect config jumper UARTSEL
    • 0001404: [NBoot] Enable QoS_fast for memory access


    Changes in V16

    • 0001367: [NBoot] Always detects digital RGB interface


    Changes in V15

    • 0001166: [NBoot] ND14: Some config pins are not configured with pull down
    • 0001167: [NBoot] Add support for PicoMOD7A
    • 0001182: [NBoot] wrong PCB revision displayed
    • 0001278: [NBoot] If started from SD card, run actions.txt automatically if it exists.
    • 0001280: [NBoot] Add empty commands '\r' and '\n' to re-display menu
    • 0001070: [NBoot] Add support for nanoRISC
    • 0001069: [NBoot] Add support for 512MB NAND flash



    U-Boot V2.0 (20.11.2012, based on u-boot-2012.07)
    Supported boards: PicoMOD6, PicoCOM3, armStoneA8, NetDCU14, PicoMOD7A


    • Rebase to u-boot-2012.07
    • Add support for PicoMOD7A
    • New environment variables 'platform' and 'arch' that contain the current board type and architecture
    • Completely new FAT/VFAT implementation (write support still missing)
    • New wildcard module to allow for '*' and '?' in path and file names; currently only working in combination with FAT (fatls, fatload)
    • Improve output of device descriptions (indendation, interface)
    • Patch serial port in zImage (use by zImage decompressor), so the same zImage can be used on boards with different default serial port
    • Allow different ECC modes by virtually splitting NAND; one for NBoot, one for the rest; remove old nboot protection as the new scheme allows a more generic protection per device
    • Fix ecc.bytes and ecc.layout->eccbytes settings
    • Allow a dynamic environment size depending on NAND blocksize
    • Reduce environment size on large NAND blocksizes
    • Allow different default mtdparts sizes depending on NAND blocksize
    • Allow using '.' as default argument in commands with addresses or bootfiles; it is replaced by $(loadaddr) or $(bootfile) respectively
    • Combine PicoMOD6 and PicoCOM3 to a common fss3c64xx platform
    • Bring fss3c64xx in line with fss5pv210 platform
    • Allow board specific default serial port, set sercon variable to it
    • Improve serial driver for S3C64XX to allow CONFIG_SERIAL_MULTI
    • Use ttySACx (instead of s5p_uartx) as name for serial devices
    • Fix early access to serial port
    • Fix serial download
    • Fix generic SDHC driver on S5P
    • Add similar SDHC infrastructure for S3C64XX as for S5P and switch from F&S NBoot MMC driver to generic SDHC driver
    • Add commands update and install to manually trigger installation
    • Improve update command, unused arguments can be skipped with '.'
    • Use NetLoop() instead of netboot_common() for network update/install
    • Allow board specific defaults for updcheck/instcheck
    • Change environment to use new bootz command for loading zImages
    • Remove support to access single files within UBIFS and JFFS2 images
    • Enable device tree support and fdt command
    • Enable unzip command
    • Disable bootelf, bootvx and itest commands
    • Add new default variables bootnfsdhcp, bootubidhcp, bootjffs2dhcp; if called with run, Linux initializes the network devices with DHCP
    • Fix bootcmd to load to dynamic loadaddr instead of fix 0x41000000
    • Fix ethernet settings for boards with more than one port
    • RTC: remove reading of alarm values, they are not used anyway



    Linux Kernel V2.0 (22.11.2012, based on linux-3.3.7)
    Supported boards: armStoneA8, NetDCU14, PicoMOD7A


    • Add support for PicoMOD7A, default console on ttySAC2
    • Add support for NetDCU14, default console on ttySAC1, 2nd CAN
    • Completely new touch driver with down-force evaluation and far lessjitter; tuning parameters can be set via Kconfig (make menuconfig) and /sys/devices/platform/s3c64xx-ts/
    • Activate Atmel mXT I2C capacitive touchscreen and add configuration
    • Add support for FocalTouch FT5x06 series touch controllers
    • Set default display configuration for Chi Mei G070Y2-L01 (800x480)
    • Add default and maximum bpp to generic LCD configuration
    • Fix CAN interrupt handling that could cause a system hang
    • Improve CAN performance by setting maximum possible SPI speed
    • Move platform dependent code from s5p-sgtl5000.c to mach-*
    • Modify zImage decompressor code to allow default serial port (console) to be patched by U-Boot at runtime
    • armStoneA8: Fix missing SPI0 device
    • Fix bad maximum speed computation for SPI
    • Enable SPIDEV in the default config (required for userspace SPI)
    • armStoneA8/NetDCU14: Block I2C0 if SPI0 is running and vice versa
    • Modify packet buffer out threshold for USB EHCI on S5P
    • Fix non running RTC due to missing base clock
    • Fix clocks and GPIO configuration for UARTs
    • Enable SYSVIPC in default config (required for shared memory accesses, e.g. in the X-Server)
    • Add optional device fs_phkmem to allow setting HW registers of the SOC from userspace



    BuildRoot V2.0 (22.11.2012, based on buildroot-2012.08)
    Supported Boards: armStoneA8, NetDCU14, PicoMOD7A, PicoCOM4


    • Rebase to buildroot-2012.08, this updates lots of packages
    • Add support for PicoMOD7A
    • Add support for NetDCU14
    • Add support for PicoCOM4
    • Move F&S specific stuff from target/device/f+s to board/f+s
    • Remove JFFS2 from the set of automatically generated filesystem images
    • [STD] Add openssh, x11vnc, xhost, input-tools, input-event-daemon
    • Update to busybox-1.20.x, this adds the command lsof
    • Add support for Atmel mXT and FocalTech FT5x06 series capacitive touch controllers (via I2C)



    Toolchain
    The toolchain remained unchanged



    Documentation

    • New MultiPlatform-Linux-FirstSteps.pdf document



    Your F&S Support Team

  • NetDCU14/Linux development state and releases

    Multi-Platform Linux V2.0


    We have uploaded a new Linux version to our server. This is the first Multi-Platform Linux Release that supports several boards at the same time. At the moment these are the boards based on Samsung S5PV210 SoC: armStoneA8, NetDCU14 and PicoMOD7A. In the future more boards and also different architectures will be added to this Multi-Platform Release.


    This release is based on an earlier version that was only available on armStoneA8. Therefore the Release Notes below show the modifications in relation to this armStoneA8 version.


    In the download area on our website you'll find two tar archives:


    multiplatform-linux-f+s-V2.0.tar.bz2
    This is the main release itself containing all sources, the binary images, the documentation and the toolchain.


    sd-card-V2.0.tar.bz2
    If you copy the contents of this archive to an SD card, you can install our precompiled standard system in a very straightforward and comfortable way on the board. The SD card archive is meant for people who just want to try a release first without having to download the quite large main archive. Its content is also contained in the main release archive, so if you want to download the main archive anyway, you don't need to bother with the SD card archive.


    These tar archives are compressed with bzip2. So to see the files, you first have to unpack the archives

    Code
    1. tar jxvf multiplatform-linux-f+s-V2.0.tar.bz2


    This will create a directory multiplatform-linux-f+s-V2.0 that contains all the files of the release.


    Please read the file doc/MultiPlatform-Linux-FirstSteps.pdf. It lists the meaning of all files and shows how to install and use everything.



    Release Notes for Multi-Platform Linux V2.0


    This is a major release with lots of changes. It is the first release that supports several boards at once. The boards that are supported through all levels (NBoot, U-Boot, Linux Kernel, BuildRoot) are:


    armStoneA8, NetDCU14, PicoMOD7A


    Please note that you have to update NBoot first to be able to use the automatic installation process described in the FirstSteps document.


    Here is a list of the most noticeable changes in this release.


    NBootV210 (V18) (21.11.2012)
    Supported boards: armStoneA8, NetDCU14, PicoMOD7A


    Changes in V18

    • 0001421: [NBoot] Add ubotv210.nb0 as possible load source
    • 0001428: [NBoot] Ram test not working for 512 MB version
    • 0001426: [NBoot] Small change in SDHC clock calculation


    Changes in V17

    • 0001405: [NBoot] PM7A: Detect config jumper UARTSEL
    • 0001404: [NBoot] Enable QoS_fast for memory access


    Changes in V16

    • 0001367: [NBoot] Always detects digital RGB interface


    Changes in V15

    • 0001166: [NBoot] ND14: Some config pins are not configured with pull down
    • 0001167: [NBoot] Add support for PicoMOD7A
    • 0001182: [NBoot] wrong PCB revision displayed
    • 0001278: [NBoot] If started from SD card, run actions.txt automatically if it exists.
    • 0001280: [NBoot] Add empty commands '\r' and '\n' to re-display menu
    • 0001070: [NBoot] Add support for nanoRISC
    • 0001069: [NBoot] Add support for 512MB NAND flash



    U-Boot V2.0 (20.11.2012, based on u-boot-2012.07)
    Supported boards: PicoMOD6, PicoCOM3, armStoneA8, NetDCU14, PicoMOD7A


    • Rebase to u-boot-2012.07
    • Add support for PicoMOD7A
    • New environment variables 'platform' and 'arch' that contain the current board type and architecture
    • Completely new FAT/VFAT implementation (write support still missing)
    • New wildcard module to allow for '*' and '?' in path and file names; currently only working in combination with FAT (fatls, fatload)
    • Improve output of device descriptions (indendation, interface)
    • Patch serial port in zImage (use by zImage decompressor), so the same zImage can be used on boards with different default serial port
    • Allow different ECC modes by virtually splitting NAND; one for NBoot, one for the rest; remove old nboot protection as the new scheme allows a more generic protection per device
    • Fix ecc.bytes and ecc.layout->eccbytes settings
    • Allow a dynamic environment size depending on NAND blocksize
    • Reduce environment size on large NAND blocksizes
    • Allow different default mtdparts sizes depending on NAND blocksize
    • Allow using '.' as default argument in commands with addresses or bootfiles; it is replaced by $(loadaddr) or $(bootfile) respectively
    • Combine PicoMOD6 and PicoCOM3 to a common fss3c64xx platform
    • Bring fss3c64xx in line with fss5pv210 platform
    • Allow board specific default serial port, set sercon variable to it
    • Improve serial driver for S3C64XX to allow CONFIG_SERIAL_MULTI
    • Use ttySACx (instead of s5p_uartx) as name for serial devices
    • Fix early access to serial port
    • Fix serial download
    • Fix generic SDHC driver on S5P
    • Add similar SDHC infrastructure for S3C64XX as for S5P and switch from F&S NBoot MMC driver to generic SDHC driver
    • Add commands update and install to manually trigger installation
    • Improve update command, unused arguments can be skipped with '.'
    • Use NetLoop() instead of netboot_common() for network update/install
    • Allow board specific defaults for updcheck/instcheck
    • Change environment to use new bootz command for loading zImages
    • Remove support to access single files within UBIFS and JFFS2 images
    • Enable device tree support and fdt command
    • Enable unzip command
    • Disable bootelf, bootvx and itest commands
    • Add new default variables bootnfsdhcp, bootubidhcp, bootjffs2dhcp; if called with run, Linux initializes the network devices with DHCP
    • Fix bootcmd to load to dynamic loadaddr instead of fix 0x41000000
    • Fix ethernet settings for boards with more than one port
    • RTC: remove reading of alarm values, they are not used anyway



    Linux Kernel V2.0 (22.11.2012, based on linux-3.3.7)
    Supported boards: armStoneA8, NetDCU14, PicoMOD7A


    • Add support for PicoMOD7A, default console on ttySAC2
    • Add support for NetDCU14, default console on ttySAC1, 2nd CAN
    • Completely new touch driver with down-force evaluation and far lessjitter; tuning parameters can be set via Kconfig (make menuconfig) and /sys/devices/platform/s3c64xx-ts/
    • Activate Atmel mXT I2C capacitive touchscreen and add configuration
    • Add support for FocalTouch FT5x06 series touch controllers
    • Set default display configuration for Chi Mei G070Y2-L01 (800x480)
    • Add default and maximum bpp to generic LCD configuration
    • Fix CAN interrupt handling that could cause a system hang
    • Improve CAN performance by setting maximum possible SPI speed
    • Move platform dependent code from s5p-sgtl5000.c to mach-*
    • Modify zImage decompressor code to allow default serial port (console) to be patched by U-Boot at runtime
    • armStoneA8: Fix missing SPI0 device
    • Fix bad maximum speed computation for SPI
    • Enable SPIDEV in the default config (required for userspace SPI)
    • armStoneA8/NetDCU14: Block I2C0 if SPI0 is running and vice versa
    • Modify packet buffer out threshold for USB EHCI on S5P
    • Fix non running RTC due to missing base clock
    • Fix clocks and GPIO configuration for UARTs
    • Enable SYSVIPC in default config (required for shared memory accesses, e.g. in the X-Server)
    • Add optional device fs_phkmem to allow setting HW registers of the SOC from userspace



    BuildRoot V2.0 (22.11.2012, based on buildroot-2012.08)
    Supported Boards: armStoneA8, NetDCU14, PicoMOD7A, PicoCOM4


    • Rebase to buildroot-2012.08, this updates lots of packages
    • Add support for PicoMOD7A
    • Add support for NetDCU14
    • Add support for PicoCOM4
    • Move F&S specific stuff from target/device/f+s to board/f+s
    • Remove JFFS2 from the set of automatically generated filesystem images
    • [STD] Add openssh, x11vnc, xhost, input-tools, input-event-daemon
    • Update to busybox-1.20.x, this adds the command lsof
    • Add support for Atmel mXT and FocalTech FT5x06 series capacitive touch controllers (via I2C)



    Toolchain
    The toolchain remained unchanged



    Documentation

    • New MultiPlatform-Linux-FirstSteps.pdf document



    Your F&S Support Team

  • Kernelupdate in runtime

    Code
    1. # cat /sys/class/mtd/mtd4/name
    2. Kernel
    3. # ls -lah /dev/mtd4
    4. crw-rw---- 1 root root 90, 8 Jan 1 00:00 /dev/mtd4
    5. # flash_eraseall -j /dev/mtd4
    6. Erasing 128 Kibyte @ 400000 - 100% complete.Cleanmarker written at 3e0000.


    Please make sure your bootargs look like (and run 'saveenv' to save modifications):

    Code
    1. Kernel command line: console=ttySAC2,38400 mtdparts=qba8nand0:128k(NBoot)ro,512k(UBoot)ro,128k(UBootEnv)ro,512k(UserDef),4m(Kernel),-(TargetFS) init=linuxrc root=/dev/nfs rw nfsroot=/rootfs ip=10.0.0.27:10.0.0.74:10.0.0.5:255.255.255.0

  • Kernelupdate in runtime

    Take a look at the debug output (again this is PicoMOD7A):


    Creating 5 MTD partitions on "fsnand0":
    0x000000040000-0x0000000c0000 : "UBoot"
    0x0000000c0000-0x000000100000 : "UBootEnv"
    0x000000100000-0x000000500000 : "UserDef"
    0x000000500000-0x000000800000 : "Kernel"
    0x000000800000-0x000008000000 : "TargetFS"


    You see 0=UBoot .. 3=Kernel


    # cat /sys/class/mtd/mtd3/name
    Kernel


    Pls search for 'Kernel' and use the corresponding mtd*

  • Kernelupdate in runtime

    Yes, that is possible.
    You need set modify the bootargs/mtdparts like that (see the access rights for Kernel) - this line is from PicoMOD7A, pls set appropriate for your PicoMOD7:

    Code
    1. mtdparts=fsnand1:256k(NBoot)ro;fsnand0:512k@256k(UBoot)ro,256k(UBootEnv)ro,4m(UserDef),3m(Kernel),-(TargetFS)


    In Buildroot you need to add tools to busybox with:

    Code
    1. make busybox-menuconfig


    and add:

    Code
    1. CONFIG_NANDWRITE and CONFIG_FLASH_ERASEALL


    Then with the new rootfs and the corresponding bootargs you can update Linux Kernel Image from the serial command line (Linux) like: