Posts by didier.guillemyn@telenet.be

    This doesn't seem to work:

    1. setenv console=ttynull returns a syntax error (= is not allowed). setenv console ttynull is accepted.

    2. but even after this change, the console is not disabled on /dev/ttyxmc1: the kernel boot messages still appear on that port and a console prompt to login is still shown.

    Thanks again for the support.


    Didier.

    Hi,


    When booting, U-boot shows the following

    I see "Board: armStoneMX8MP Rev 1.00 (2x LAN, WLAN, eMMC, 1x DRAM)", so I assume this is Rev 1.00?


    Not sure how to get the serial number. Don't see a label on the board with the serial number (but it might be hidden behind the heatsink?). Or is this the label on the HDMI port (which is used as the MAC address)?


    Regards,


    Didier.

    Dear F&S support,


    We are currently migrating our software from an ArmstoneA9r2/r4 running WEC 7 to ArmstoneMX8MP.We want to maintain our interface board as much as possible without hardware changes.
    To accomplish that, we want to ensure UARTs are on the following Rx / Tx pins:

    * UART 1: pin 56 + 58
    * UART 2: pin 13 + 15

    * UART 3: pin 36 + 38

    (note: this numbering is our internal numbering, not related to the UART numbering of the F+S hardware doc)


    UART 1 is the console UART (UART_A, /dev/ttymxc1) which is fine.


    However, we are having trouble to correctly configure UART2 and UART3:

    * in the hardware doc, UART_B is assigned to pin 13, pin 15, and looking at the armstonemx8mp.dtsi file, it should be assigned to /dev/ttymxc2 as it is identified as uart3 in the dtsi file. However, we are not able to communicate on that port. What strikes me is that although the hardware doc assigns UART_B to pin13, 15, in the dts file, the comment says that UART_B is assigned to pin 17 and 19:
    /* UART_B - Feature connector J20 pins 17,19 */

    * the UART assignments for pin 36 + 38 are very confusing in the hardware doc: it states that both UART_C and UART_D are assigned to it, with a comment "Note 5: UART_C, UART_D can be chosen for RS232 RXD and TXD signals".


    Can you clarify how we can assign (i guess by patching the dts file) UART's to pin 13, 15 and pin 36,38 respectively?


    Thanks for your support.

    The crash happens with OpenJDK 11 - server.

    The crash is systematic. I tested with different setups and different buildroot environments.


    Meanwhile I could build successfully with OpenJDK 17 - server, and this version runs properly.

    Note that I first could not compile OpenJDK 17 (which was the prime reason I was forced to use OpenJDK 11), but this was because of my specific compilation setup (which is based on a WSL2 Ubuntu).


    Bottomline: I can continue with my java setup using OpenJDK 17, so no need for the OpenJDK 11 issue to be resolved anymore...


    Regards,


    Didier.

    Hi,


    I tried to add OpenJDK to my buildroot platform. It only compiles without errors if I select OpenJDK 11, server version.

    However, when running java, I get the following:

    Any Idea why I get this error? The alignment trap seems to indicate a bad compilation of the package?

    Hi,


    Is ssh supported on Windows CE? I see that the BSP contains the SSH tool: in the catalog items view under ThirdParty -> F&S -> Tools there is SSH-SSL-SMTP entry, but I cannot activate it. Clicking on it results in a red cross, which indicates that this item is excluded from the OS design..


    Thank you for the support.

    Hi,


    I tried the memcfg program on an Armstone A9 board. The program works but only reductions of the standard storage size are accepted, not increases.
    The board is configured with approx. 132 MB storage size and approx. 840 MB program memory (from which 190 MB is in use).


    After recompilation of the memcfg program, and adding some debug statements the SetSystemMemoryDivision() routine does not return any error (return code 0).


    Why can I not increase the storage size on the Armstone A9?

    Dear,


    I configured GPIO pins 12 and 14 on the Armstone A9 as GPIO inputs, and disabled the SPI (Flags = 4).


    [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\DIGITALIO]
    "UseAsIO"=dword:07fc07ff
    "DataDir"=dword:00000000
    "Prefix"="DIO"
    "Dll"="fs_digio.dll"
    "Order"=dword:00000097
    "Index"=dword:00000001
    "Ioctl"=dword:00000004
    "Port"=dword:00000000
    "DataInit"=dword:00000000
    "FriendlyName"="Digital I/O driver for iMX6"
    "Debug"=dword:00000000




    However, measuring the levels on 12 and 14 (both through software and from an oscilloscope), I get a high level. Strange enough, the level of pin 14 is about 2.2 V, while the level of pin 12 is 3.3V.


    Could it be that the SPI driver is still interfering with these GPIO pins?


    I have following firmware:
    Eboot: v 1.20
    Nboot: PVN26
    Kernel: V1.80 - Build Dec 17 2015



    Regards,


    Didier Guillemyn

    Hi,


    I seem to have the same problem. COM1: till COM3: are defined with the configuration as in the first post of this thread (although with my config COM1: and COM2: are swapped) but not able to communicate with COM2: I can communicate with COM1: (debug port though).


    I'm using the kernel released Mar 2015. Can you confirm this bug is resolved in this release? Or is this still considered as a bug?


    Thank you for your response,


    Regards,


    Didier Guillemyn.