Posts by telerob

Thanks for this new release. Especially the new kernel version is a great benefit. Is there a plan to have the same kernel for a yocto release? If yes, is there a roadmap?

We use a GPIO to switch external hardware on/off with an external pull up. At the moment we have an issue on startup that the signal has not the state it should have.
The signals name is the SD_A_WP / GPIO01_IO07.
You see the behavior on the attached image - yellow line. What we did was a soft reboot with command "reboot" from linux.
So I guess as soon as linux resets, the signal reaches the pull up. Then it goes down to ~1V for about 300ms and goes back to pull up.
I already checked if the signal is used in UBoot but that seems not to be the case for the mx8MP. I also guess that there is no u-boot running in the first 300ms.
Is that behavior caused by nboot or by the chip itself? Is there a solution or should we switch over to another GPIO in the next hardware version?

Hi there,

we have a two color indicator LED connected to two GPIOs. The LED shows different states of the system. As the LEDs are controlled by the M7 so it takes some time till the user can see that the system is running.
What we need, is that both GPIOs(GPIO4_IO20,GPIO3_IO22) are set to high not long after powering the system on. A time of about 500-1000ms would be sufficient so we thought of modifying u-boot.

Questions:

1. Is the uboot that is build with the yocto build that one that is already installed on the board?

2. What would be the easiest way to modify it?

3. Is there an example, and are the GPIO names the same as in linux?

4. Do you suggest another solution?

Thanks!

We are using now the LVDS adapter. Do we have to look for a special configuration? Or can we use the normal config file ?

Thanks for the config file.
But i have a question about the parameter "config" and "type". I don't find them listed in the documentation "NetDCU9_Display_eng.pdf"
So, are this parameter "Bit-or" values?

Hello,

I need help to make a configuration file for the display G084SN05 V9 from AUO.
I'm running a NetDCU9 with LVDS Adapter.

I cannot upload the data sheet because is too big.

Thanks

So, with the next windows 10 update to version 1709 we got more troubles. We looked into microsoft forums and fixed so far the problems. But one pc still do not want to install the WMDC. We got the error of a missing DLL during the installation of the WMDC. Are there any ideas what to do?

Hi,

Yes it's'the Creatures Update i have to talk with my IT. Maybe they can remove it.
I hope also we can get a fast response from F&S.

Greetings.

Hi,

I have to check it....

Hello,

we have installed a computer with windows 10 and we want to connect to to the netdcu board "netdcu9". But we get no connection to the board. Neither with windows 10 synchronizing centre nor with the windows mobile device centre.
Any ideas where to look ?

Greetings

Hello together,

can someone tell me what are the default parameter of the touch display for NetDCU 9.2?

Greetings.

Thanks,

it's working.

But will this installation issue under windows 10 soon be fixed?

Hello,

I tried under windows 10 (logged in as local administrator) a kernel uodate with the netdcu usb loader 2.4.1
After connecting the serial and usb cable and starting the kernelupdate process in the bootlader menu with DU, i got following message from the dcuterm shell:
+USB_Init()
RNDISFN: UFN_RESET received
RNDISFN: UFN_RESET received
RNDISFN: UFN_RESET received

than it stops

In the application NetDCU-USB-Loader the red LED don't switch to green.

After checking the forums i tried to install manually the FSBoardUSB driver with the FSBoardUSB.inf file.
It returns with the message "Die INF-Datei des Drittanbieters enthält keine Digitalsignaturinformationen".

Is this the problem?

Any help is welcome.

Greetings.

I use fsimx6-V2.1 we also added some packages based on the minimal configuration.

Network is initialized over the /etc/network/interfaces.conf:

This is my buildroot configuration:

This is the code which is used...

Kernel output.... check first line and last lines

Limiting the speed in U-Boot works as you suggested. But as soon as the kernel is started it switches back to 1GBits.

I applied the kernel patch and tested it. Nothing changed.... link speed is still 1000MBit.

PHY: 1:04 - Link is Up - 1000/Full
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

I didn't change the rate in u-boot.....

Any ideas?

I also see a different in U-Boot and C example:
val &= ~0x0300; vs
dio write FEC 0 3300

Yes, after compiling this package in, I have a limits.conf file. But it is still not working. I also added pam to busybox, without success. I'm not sure but as I see, all settings in limits.conf are applied as soon the user logs in. In my case, the process is started by start-stop-daemon which switches to another user and then start the executable. So I don't know if settings are applied... I also don't know if pam is working because I don't know how I would see this.
Is there any other possibility to give a user the rtprio right? sysctl or something else?

Hello,

in our application some threads run with rtprio. If I start the program as root, everything works as expected. If starting as normal user it is not possible to change the priority to rt. I know that this is nothing special, because not all users have the same rights.
On a "normal" Linux systems I modify the /etc/security/limits.conf file. On the device, there is no such file and also after creating it, it is not used by the system.
Any ideas?

That sounds good, but is it right, that there are no hardware encoders for H.264?

Some time ago we did some tests with the imx6 and its hw encoder/decoder capabilities. We are very happy with the performance but we need to integrate it into an "old" system.

One device should act as an encoder for fbas/composite PAL signal to h.264 and on the other side backwards from h.264 to fbas/composite PAL.
Is there an "easy" solution to get fbas into the system and fbas out?