QUICC ENGINE VALlDATION

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

QUICC ENGINE VALlDATION

950件の閲覧回数
chidambaram_km
Contributor I

Hello All,

I'm currently working on LS1021A - TWR Board. We have Successfully loaded the QUICC Firmware please find the below logs for your reference.

"Firmware 'Microcode version 0.0.1 for LS1021a r1.0' for 1021 V1.0
QE: uploading microcode 'Microcode for LS1021a r1.0' version 0.0.1"

I included the qe_ic driver and UCC Uart driver into the kernel. I got below logs for the successful loading of UCC uart driver.

[ 1.955532] Freescale QUICC Engine UART device driver
[ 1.961056] 2402000.ucc: ttyQE0 at MMIO 0x2402000 (irq = 38, base_baud = 9375000) is a QE
[ 1.969579] ucc_uart 2402000.ucc: UCC1 assigned to /dev/ttyQE0
[ 1.975734] 2402200.ucc: ttyQE1 at MMIO 0x2402200 (irq = 39, base_baud = 9375000) is a QE
[ 1.984191] ucc_uart 2402200.ucc: UCC3 assigned to /dev/ttyQE1

Once i get the console i check the interrupt entry of QUICC driver using the below command "cat /proc/interrupts"


Find the below attachment "interrupts.txt".

 

Please let me know whether I need to get the interrupt entry in the "/proc/interrupts".  And also I'm running the below commands for transmitting the data through ttyQE0 by using the below command.

echo "hi" > /dev/ttyQE0

Here I want to check whether I got transmitted the interrupt or not. Can you please help me to check it.

For your reference "TWR-LS1021A-kernel-logs.txt" attached below.


Thanks in Advance.

0 件の賞賛
返信
15 返答(返信)

907件の閲覧回数
chidambaram_km
Contributor I

1. After running the microcom command, we are getting the QUICC interrupt entry in cat /proc/interrupts.

Command: microcom -s 115200 /dev/ttyQE0

log :

~# cat /proc/interrupts
CPU0 CPU1
16: 0 0 GIC 29 Edge arch_timer
17: 956 781 GIC 30 Edge arch_timer
18: 0 0 GIC 27 Edge kvm guest timer
22: 0 0 GIC 25 Edge vgic
25: 0 0 GIC 107 Level SCM_IRQ
26: 6957 0 GIC 126 Level mmc0
29: 0 0 GIC 129 Level 2110000.dspi
30: 87 0 GIC 120 Level 2180000.i2c
31: 0 0 GIC 121 Level 2190000.i2c
32: 292 0 GIC 118 Level serial
40: 0 0 GIC 150 Level 29d0000.ftm0
41: 0 0 GIC 147 Level 2ad0000.watchdog
43: 0 0 GIC 167 Level eDMA
47: 0 0 GIC 205 Level gianfar_ptp
51: 0 0 GIC 125 Level xhci-hcd:usb1
56: 0 0 QEIC 32 Level ucc-uart
57: 9 0 GIC 176 Level eth0_g0_tx
58: 133 0 GIC 177 Level eth0_g0_rx
59: 0 0 GIC 178 Level eth0_g0_er
60: 52 0 GIC 179 Level eth0_g1_tx
61: 0 0 GIC 180 Level eth0_g1_rx
62: 0 0 GIC 181 Level eth0_g1_er
IPI0: 0 0 CPU wakeup interrupts
IPI1: 0 0 Timer broadcast interrupts
IPI2: 1695 1349 Rescheduling interrupts
IPI3: 0 0 Function call interrupts
IPI4: 2 13 Single function call interrupts
IPI5: 0 0 CPU stop interrupts
IPI6: 1 0 IRQ work interrupts
IPI7: 0 0 completion interrupts


2. When I transmit data through microcom, the UCC_uart interrupt is not getting triggered.

3.We suspect that the QUICC interrupt controller is enabled in the GIC (interrupt number - 141). We need the procedure to enable the GIC interrupt (interrupt number - 141).

0 件の賞賛
返信

847件の閲覧回数
yipingwang
NXP TechSupport
NXP TechSupport

In the dts file, please define the device node similar as the following.

&uqe {

        serial: ucc@2000 {

                device_type = "serial";

                compatible = "ucc_uart";

                port-number = <0>;

                rx-clock-name = "brg1";

                tx-clock-name = "brg1";

        };

If your problem persists, in Linux Kernel driver file drivers/tty/serial/ucc_uart.c, please enable LOOPBACK mode, then check whether you could read and write the same value.

0 件の賞賛
返信

836件の閲覧回数
chidambaram_km
Contributor I
I enabled the below loopback macro in the ucc_uart.c file

* Enable this macro to configure all serial ports in internal loopback
mode */
#define LOOPBACK

And I ran microcom application on the board. And enabled some of the prints in the ucc_uart.c file during the transmit.
Whatever I am pressing the key in the microcom application, I am able to get the same ascii key in the driver. I did not get any interrupt for the TX and I did not receive any RX data.

Please find the below log
~# microcom -s 115200 /dev/ttyQE0
Loopback requires the preamble bit to be set on the first TX BD
1. Enabled Loopback
random: nonblocking pool is initialized
Entering into the qe_uart_start_tx()
Entering into the qe_uart_tx_pump()
Tx data = 1
Tx Len = 1
Setting BD_SC_READY in BD status
Entering into the qe_uart_start_tx()
Entering into the qe_uart_tx_pump()
Tx data = w
Tx Len = 1
Setting BD_SC_READY in BD status
Entering into the qe_uart_start_tx()
Entering into the qe_uart_tx_pump()
Tx data = e
Tx Len = 1
Setting BD_SC_READY in BD status
Entering into the qe_uart_start_tx()
Entering into the qe_uart_tx_pump()
Tx data = r
Tx Len = 1
Setting BD_SC_READY in BD status

Look forword to receving your suggestion.
0 件の賞賛
返信

737件の閲覧回数
chidambaram_km
Contributor I

Waiting for the response.

0 件の賞賛
返信

644件の閲覧回数
yipingwang
NXP TechSupport
NXP TechSupport

UCC UART feature is formal supported in QorIQ SDK 1.9. It's better to do verification with Linux Kernel provided in QorIQ SDK 1.9.

In addition, I checked ls1021atwr dts file in QorIQ SDK 1.9, it is as the following.

&uqe {
tdma: ucc@2000 {
compatible = "fsl,ucc-tdm";
rx-clock-name = "clk8";
tx-clock-name = "clk9";
fsl,rx-sync-clock = "rsync_pin";
fsl,tx-sync-clock = "tsync_pin";
fsl,tx-timeslot = <0xfffffffe>;
fsl,rx-timeslot = <0xfffffffe>;
fsl,tdm-framer-type = "e1";
fsl,tdm-mode = "normal";
fsl,tdm-id = <0>;
fsl,siram-entry-id = <0>;
};

serial: ucc@2200 {
device_type = "serial";
compatible = "ucc_uart";
port-number = <1>;
rx-clock-name = "brg2";
tx-clock-name = "brg2";
};
};

So please use UCC UART on port ucc@2200.

0 件の賞賛
返信

628件の閲覧回数
chidambaram_km
Contributor I
We followed the suggestions and updated the mentioned "dts" entry, but the interrupt ( number 141) is still not appearing.
We are currently using the RCW configuration shown below. Is there anything we need to change about this configuration?
00000000: 0408000a 00000000 00000000 00000000
00000010: 10000000 00007900 60040a00 21046000
00000020: 00000000 00000000 00000000 0022cd00
00000030: 80000104 04093340 00000000 00000000
0 件の賞賛
返信

616件の閲覧回数
yipingwang
NXP TechSupport
NXP TechSupport

In RCW, we have set both QE_TDMA and QE_TDMB to 010.

Please try UCC3 instead of UCC1.

TWR board they need to set the switch setting for SW3[6] =1 to get all the QE TDM signals are routed to the UCC block.

In ls1021a.dtsi, please make sure the following is defined.

    ucc@2000 {

                                cell-index = <1>;

                                reg = <0x2000 0x200>;

                                interrupts = <32>;

                                interrupt-parent = <&qeic>;

                        };

 

                        ucc@2200 {

                                cell-index = <3>;

                                reg = <0x2200 0x200>;

                                interrupts = <34>;

                                interrupt-parent = <&qeic>;

                        };

0 件の賞賛
返信

588件の閲覧回数
chidambaram_km
Contributor I
Could you please provide the binary for the LS1021ATWR reference board we have?
0 件の賞賛
返信

487件の閲覧回数
yipingwang
NXP TechSupport
NXP TechSupport

I don't have the binary files for ls1021atwr.

I attached Linux Kernel source code from QorIQ SDK 1.9 release to you.

Please copy arch/arm/configs/ls1021a_defconfig as .config, then menuconfig Linux Kernel as the following.

Device Drivers  --->
        [*] Freescale QUICC Engine (QE) Support  --->
        Character devices  --->
                Serial drivers  --->
                        <*> Freescale QUICC Engine serial port support

Then build Linux Kernel image.

0 件の賞賛
返信

453件の閲覧回数
chidambaram_km
Contributor I

I have downloaded the (git.tar.gz) file you attached in the same thread but could not open the file. It is throwing the error: "The link 'git' is broken. Move it to Trash." we have observed that the file is a soft link with file size zero and the file needs to be in the path “/home/yiping/QorIQ-SDK-V1.9-20151210-yocto/..........” which  we assume is specific to your build.

Additionally, I have verified the menuconfig, and the following configuration was already enabled:

 

Device Drivers  --->
        [*] Freescale QUICC Engine (QE) Support  --->
        Character devices  --->
                Serial drivers  --->
                        <*> Freescale QUICC Engine serial port support

chidambaram_km_0-1721287490867.png

Could you please resend the file? Thank you for your assistance.

 

0 件の賞賛
返信

363件の閲覧回数
chidambaram_km
Contributor I

We have downloaded the SDK 1.9 for LS1021TWR and enabled the Freescale QUICC Engine (QE) support and Freescale QUICC Serial Port support in the menuconfig. We also verified the TWR board switch setting for SW3[6] = 1. Despite these configuration changes, we are still unable to get the interrupt. Additionally, I have attached the binary files we used for testing the QUICC Engine.

Could you please assist us? Thank you in advance.

image (2).png

image.png

0 件の賞賛
返信

324件の閲覧回数
yipingwang
NXP TechSupport
NXP TechSupport

In RCW, we have to set both QE_TDMA and QE_TDMB to 010

You configured them as 110

Please try my attached images.

Please note:

ucc_uart 2402200.ucc: UCC3 assigned to /dev/ttyQE1

0 件の賞賛
返信

414件の閲覧回数
yipingwang
NXP TechSupport
NXP TechSupport
0 件の賞賛
返信

338件の閲覧回数
chidambaram_km
Contributor I

We have downloaded the SDK 1.9 for LS1021TWR and enabled the Freescale QUICC Engine (QE) support and Freescale QUICC Serial Port support in the menuconfig. We also verified the TWR board switch setting for SW3[6] = 1. Despite these configuration changes, we are still unable to get the interrupt. Additionally, I have attached the binary files we used for testing the QUICC Engine.

Could you please assist us? Thank you in advance.

image (1).png

image (2) (1).png

0 件の賞賛
返信

332件の閲覧回数
yipingwang
NXP TechSupport
NXP TechSupport

I am investigating.

0 件の賞賛
返信