PicoCOMA9X Windows Release V1.10

  • PicoCOMA9X Windows Release V1.10

    After a while, we released a new standard access for the Board PicoCOMA9X.

    NBoot: nbootimx6sx_32.bin
    EBoot: ebootIMX6SX_13.nb0
    Kernel: W13: XIPiMX6SX_C8E_V110_180131.bin W7: XIPiMX6SX_C7E_V1 10_180124.bin

    Fixed bugs from parent Version

    • Correct IO table for PicoCOMA9X.
    • Background bitmap can’t be loaded.
    • Add basic support for background scan of stored data.
    • Deactivation of FCR doesn’t work correctly.
    • Background color of buttons doesn’t work.
    • Bad memory alignment for DMA descriptors and DMA buffers.
    • ndcucfg: command “core clock” doesn’t report 400MHz or 200MHz.
    • Reboot via “ndcucfg” does not work.
    • ETHMAN hangs when no shell is registered.
    • ETHMAN doesn’t start because of missing shell API registration.
    • Serial debug output blogged after COM Open()/Close().
    • Improve read/write access.
    • Use static IP instead of DHCP is not possible.
    • Can’t write bootscreen bmp with ndcucfg.
    • Sometimes occurs an exception while boot process.
    • Implement IO control for adjust the timer without reset.
    • EC7: Section // <SYSGENS> in ceconfig.h are missing.
    • NDCUCFG: Add support for version V64.
    • Update ndcucfg to V62.
    • IOCTL_NSPI_WAITIRQ_XXX are not implemented.
    • WEC2013: Add control panel app for storage manager.
    • Free resources while deinitialize the driver.
    • Disable audio driver in case 2nd LAN is mounted.
    • Add support for 2nd LAN interface.
    • Add BootScreen support.
    • Add support forPicoCOMA9X Rev 1.10.
    • Implement registry value IntPullUp and DrvStrength (see documentation).
    • Add registry settings for SDHC slot on efus SKIT.
    • Add registry value CDIO for card detect pin.
    • Add DVFC driver.
    • The driver is not active and not activatable.
    • Add support for F3S.
    • Add power management capabilities to driver.
    • Serial debug message doesn’t show active key.
    • DHCP don’t work correctly.
    • Add possibility to limit transfer sped to 100Mbit.
    • IOCTL_HAL_QUERY_BOARD_ID should return F6S board type (CEDDK_BOARDTYPE).
    • In several display modes contrast is not working.
    • Disable debug messages.
    • Rotation doesn’t work after cold boot.
    • Clock for larger displays (i.e. 1024x600) is not correct.
    • Enable NEON as default acceleration.

    We tested different port and there availability

    We tested the availability with a test program named CanCheck.
    With that program, we sent and received CAN notification with different IDs and data.

    To check if the Ethernet works correctly, we copied a file with different data inside, from Desktop PC to the root directory via FTP.

    With a specific I2C test program, we sent different instructions to the board.
    Those instructions turned the LEDs on the I2C Extension Kit on and off.
    We tested the I2C with three different frequencies: 50000, 100000 and 400000.

    To test the I2S functionality, we heard some soundfiles and wav-data from the board.
    Also we set the volume on the board.

    We controlled with a visual check, if the color and position of the screen are right.

    With a program we adjust the PWM in different periods: 500ns, 1ms and 2ms.
    We tested it with a mark-space ratio from 1%, 25%, 50%, 75% and 99%.

    The PWM BL_CTRL is responsible for the background light.
    With “contrast set” we set different brightness on the display.

    To test the RTC, we set the board to a different time and date.
    After that we saved the new time setting and put the board away from his electric circuit.
    A few minutes later, we pulled the board on his electric circuit back and checked if the time and date doesn’t changed.

    With a program, we wrote some text data on the SD Card and copy it to the Desktop PC.
    We compare both data (SD Card and FTP) and checked if they are the same.

    By testing the SPI, we put together the MISO and MOSI Pin.
    With a test program we sent and received data.
    Every data had a different frequency and mode.

    We connected RxD and TxD together, so we can send and receive data with a test program.
    The transmitted and received data should have the same number of bytes.

    With a program, we wrote some text data on the USB Stick and copy it to the Desktop PC.
    We compare both data (USB Stick and FTP) and checked if they are the same.