Posts by fs-support_DB

Sorry, but we can't help with JTAG.

have you tried holding 's' during power-up?

If the board does not respond to the key then the nboot is not working.

For the PicoCOM series you need a special adapter to set it to recovery mode.

Please send the board back with RMA.

What exactly did you do? Which update tools were used?

Which files did you program?

You need to switch UART_A_RTS signal to the CLKREQ function in the device tree. Then this pin is routed to the PCIe function in the processor.

This pin is then no longer used by the UART.

The CLKREQ pin is availabe on J1.14 (UART_A_RTS) or J1.3 (I2C_B_SCL, 2.49k pull-up).

You have to configure your device tree accordingly.

The serial number is for a PCOMA9X-V3I-LIN.

This board has 2x ethernet and no audio.

https://fs-net.de/en/embedded-…rocessor/pcoma9x-v3i-lin/

Please contact your distributor Batenburg/Adelco for more information.

Please send the serial numers of the failing boards

Please send the boards back with RMA so we can analyze them.

to check the signal path of the audio signal, you can use a WAV-file with a known amplitude and frequency (can be created with the Audacity sound editor, e.g. 1kHz sine, 90% signal amplitude).

Play the WAV-File and measure the signal along the signal path and make sure that on every location the signal is in the allowed voltage range and no clipping occurs. Also make sure that the signal is the same if played several times.

If you can see, that the signal at LOUT changes, then the problem is on the PicoCOM side.

did you try USB in nboot?

Is there the same error?

Did all boards have the same software version (nboot, eboot) before you updated them?

Did you update only the kernel or also the bootloaders?

You can update nboot and eboot over serial in nboot ('d') to the lastest versions.

Were all boards updated with the same setup on the same day from the same person?

Is the nboot version the same on all boards? You can check with 's' on startup.

Is the uboot version the same?

Was a USB-Hub used to connect the NetDCUs?

32kHz can be routed to:

J1-18 UART_A_RXD -> GPIO1_IO03 ALT3

J2-93 JTAG_TCK -> JTAG_TCK ALT6

This is an undocumented feature of the processor, these settings are not in the IOMUX tables.

We cannot guarantee that it will work on future revisions of the processor and the board.

These settings are also specific to the PicoCoreMX6100 and are not available on other boards of the PicoCore family.

For compatibility you have to add a mounting option for an oscillator.

You need to install the lastest version of eboot and kernel to support the new flash:

eboot_pc4_112.nb0

XIPNKPC4_CORE_CF35_V117_210216.bin

You might have to adjust the partition sizes for the new kernel and filesystem in the PSD file.

There are no changes necessary from the application side.

Spread Spectrum for PLL1 and PLL2 is enabled since V12 (2014)

You can select another clock source for UART and SPI in Linux.

You could use an older nboot, but we can't guarantee that is works on current production boards.

We are delivering the 'new' 1.23 revision since 2015.

Where did you read the board revision? From the board or from nboot?

nboot reports 1.23 since version V13.

So maybe the 'new' board has a new version of the nboot.

V15 ist the standard nboot since end of 2019.

You can look in the kernel sources for supported touch controllers or if the manufacturer of the touch controller provides a linux driver.

You can try the TI TSC2004 , this is a widely used touch controller.

You can use the SX8674IWLTRT, this device is not EOL.

NetDCU11/NetDCU11.2 has a diode in the VBAT line.