Posts by RSchubert

Thanks for information. How to do this for:

RXD1 Pin 15
TXD1 Pin 13
RTS1 Pin 19
CTS1 Pin 21

Dear support,

is it possible to have RTS/CTS for UART_B on armstoneA9 (1.10) on pins 19/21 like it's available on armstoneA9r2? Or is UART_A the only full connected UART?

Thanks in advance

Dear Support-Team,

is it possible to use the SX825x touch controller on the i2c5 instead of i2c2? If yes we can reduce a connector from our board to the 6 pin connector on armstoneA9r2 and use the pin 16/17 from the feature connector. Do we have to move the following code in armstonea9r2dlq.dtsi i2c2 section to a i2c5 section?

Thanks and kind regards.

When will these pins 16/17 be available for I2C in device tree? Is this possible anytime or not (then we will have to change our hardware what is in beta state)?

Kind regards

Any idea ?
No one else with this problem ?

Dear F&S Support Team,

I got the RS485 working completely now. The final problem was a resistor on the RS485 lines (I don't know exactly but I guess that should be used for ESD protection on our hardware ???).

Thanks for great support.

Dear fs-support_PJ,

thank you very much for checking this issue. I'm facing the same problems when using the terminating resistor. As soon as the RTS line will be drawn to low level the Modbus package will be refused by the receiver. When holding RTS on high level all the time it's possible to write at least. I will try using UART1 instead of UART2 now. Is it possible to get your little c program just to exclude software issues on my side.

I guess the different RS485 transceiver SN65HVD10 should be no problem - there are no significant differences: http://www.ti.com/product/SN75HVD12

Thanks again.

I guess this can be solved by the USB power management. Even if I shutdown armstone by using the "halt" command the USB devices will keep powered on.
I also played around with the

directory but was not able to suspend USB power.
I also had a look into the device tree:

Is there any possibility to get control over USB power?

Dear support-team,

I'm using a special USB device that is providing an interface to a field bus system. The device driver is creating a virtual network interface. In my software I connect to this virtual network and can read/write the field bus. This is working well as long as I do not reboot the armstone (warm boot e.g. by calling reboot in console). After reboot this USB device is not available anymore and cannot be seen when calling lsusb. When I power off/on the armstone everything is working well again. I'm also using other USB devices (e.g. capacitive USB Touch). These other devices are working after warm boot. On other platforms/kernel versions the field bus USB device was working after warm boot also.

Any idea?
Thanks.

Yes, that's clear now. I tried both pins (RTC/CTS) anyway.
When I check the RTS line with an OSCI I can see the level going from 0V to 3.3V and going back to 0V after sending the data.
This RTS is connected to the SN65HVD10 RE/DE pins. That seems to be working so far.

But it's not possible for me to read or write data to a Modbus RTU Relais module with this configuration.
When I wire the RE/DE pins to 3.3V directly I can write data without problems and switch some relais. But of course it's not possible to read back data with RE/DE on high level.

The problem seems to be when the RTS line will be set to 0V. Then the RS485 receiver will discard the sent data (RED error led).
Maybe the problem is caused by levels of RX/TX lines before setting RE/DE to low for reading?
Maybe the problem is a timing issue because

values seem not to be used inside the imx6 driver.

I tried many things beginning from driving the RE/DE with an GPIO instead of RTS to using different new versions of /drivers/tty/serial/imx.c from the NXP/Freescale imx6 kernel branches. All without success.

Can anyone confirm this or has anyone RS485 working in both directions?

Thanks for any hint.

Any news ?

WLAN is working now so far in my configuration (I can scan existing networks). I guess the reason was missing /lib/firmware directory but I'm not sure.

That would be nice to have this working because it's one of the last things to complete our hardware around the armstone. I also had a look at some imx6 forums and found some (maybe old) issues but it was impossible for me to get them into the kernel for now.

Thanks

Thanks for your answer. If it's working in the standard configuration I guess it's my matter. I'm using my own kernel and buildroot configuration (base on your standard). I have to look through handling firmware and modules because that's missing in my rootfs. I will tell you later if I solved this issue.

Dear Support-Team,

how do I enable wlan (the onboard wlan device) on armstonea9r2dl ?

What I tried yet:
loading kernel modules mwifiex.ko and mwifiex_sdio.ko (I don't know if this are the right ones).
WLAN seems to be enabled in devicetree.
wlan0 is define in /etc/network/interfaces.

I expected to have a wlan0 interface when I check ifconfig.

Thanks for hints.

As I see on efus Starterboard a RS485 driver circuit is assembled on UART C. Has anyone used this successfully?

Dear Support Team,

has anyone succesfully used an UART as RS485 port? I tried with UART B (/dev/ttymxc1) and a SN65HVD10 driver circuit. I'm able to send data but I'm not able to receive data. RS485 support in general is included in kernel /drivers/tty/serial/imx.c.
(armstonea9r2dl with software release 3.0)

CTS is wired to circuits RE/DE pins. This seems to work OK. Maybe the problem may come from levels of RX/TX lines before setting RE/DE to low for reading?

Here some pieces of code from my application:

I also tried to find some newer versions of /drivers/tty/serial/imx.c but without success (at least while compiling the kernel).

Anyone any idea?
Thanks.

Dear Support-Team,

thanks for your answer. That was much information. I need a little summary to look through.

Is it possible to use the OV5647 with your changes on kernel and device tree?
If not, is it better to use an OV5640 based camera with your changes on kernel and device tree?
Please send me the changes that have to be made.

Thanks again.

Have a nice weekend.

Thank you. I found it. It was hidden because I had enabled BR2_TOOLCHAIN_EXTERNAL_GDB_SERVER_COPY.

I'm sorrry but I cannot find the debugger in buildroot/output/host/usr/bin (or anywhere else).
I compiled buildroot myself (maybe with some changes). I even do not find where to enable the debugger in buidlroot menuconfig (only gdbserver but not the host).