Thank you very much I used EZSDK as you suggested and was needed to edit two more parameters in auto-build in nginx and was succeed
↧
Forum Post: RE: Linux/TMS320DM8147: TI 8147 NGINX compile
↧
Forum Post: RE: Linux/dra726: QSPI boot on dra726
[quote user="Pavel Botev"] It might be HW problem of your custom board. So I have the below question. I assume you connect your SD card to DRA72x MMC1 interface. MMC1 IO buffers are powered by DRA72x VDDSHV8 power domain. What is the power source of your VDDSHV8 (MMC1 power domain)? [/quote] It is connected to LDO1_OUT, pin 23 on TPS65917-Q1 The micro SD is powered directly with 3.3V, LDO1 is connected to the pullups and QSPI flash. What are the correct entries for the PMIC in u-boot configuration for this device? There is no switch for the SD card as on the automotive EVM. For a test I hacked the mmc source to keep from ever trying to switch voltage to 3.0V or 1.8V and the SD is now always recognized in the early stage, it was never recognized at that point before. It still is not listed as a dev in Linux, the problem may be in Linux or is it just not enable for some reason in u-boot when I boot off QSPI? If I delete the kernel from QSPI it has no problem booting from the eMMC as long as I have the device tree and kernel available in the eMMC. I can provide you with the schematic and devicetree if you would send me an Email. We have an NDA with Texas Instruments. Michel Catudal ACTIA Corp
↧
↧
Forum Post: RE: Linux/dra726: QSPI boot on dra726
[quote user="Michel Catudal"]LDO1 is connected to the pullups and QSPI flash.[/quote] LDO1 is connected to QSPI flash? Can you provide more info on that point? Do you mean that LDO1 is connected to QSPI flash power supply? Regards, Pavel
↧
Forum Post: RE: Linux/dra726: QSPI boot on dra726
[quote user="Pavel Botev"]LDO1 is connected to QSPI flash? Can you provide more info on that point? Do you mean that LDO1 is connected to QSPI flash power supply?[/quote] That is correct. The device is a S25FL512S, VCC and VIO/RFU are connected to MMC1_3V3 which is also connected to misc pull ups (QSPI, micro SD, eMMC and sysboot pins). This is connected to VDDSHV8.1 and VDDSHV8.2 (Y8 and W8). Both micro SD and eMMC VCC are connected to a fixed 3.3V supply which is connected to the SMPS inputs on the PMIC The supply that provides the 3.3V supply is controlled by an STM32 processor Michel Catudal ACTIA Corp
↧
Forum Post: RE: Linux/AM3352: Kernel Oops (AM3352, kernel 3.14.26 – SDK Linux 01.00.00.03)
Hi, I see that the last two kernel crashes happen right after suspend/resume of your ethernet phy. It seems like memory corruption. It is worth recheking your ethernet dts node. Best Regards, Yordan
↧
↧
Forum Post: RE: Linux/dra726: QSPI boot on dra726
Pavel, I forgot to mention, both STM32 and DRA726 are power up on cold boot. The STM32 can then turn the supply of the DRA726 but only does it on request from the DRA726 . The reasoning from our hardware designer for using this is that the DRA726 takes too much current in sleep mode so the STM32 is used for the wakeups. The STM32 is also used for analog and binary inputs which do not exist on the DRA726 . Michel
↧
Forum Post: RE: Linux/dra726: QSPI boot on dra726
Michel, I sent you a private message. Regards, Pavel
↧
Forum Post: RE: Linux/PROCESSOR-SDK-OMAPL138: u-boot (process-sdk-omapl138) / nand boot
Hi, Did you sign the MLO with AISGen tool? Then check this thread: e2e.ti.com/.../327220 Best Regards, Yordan
↧
Forum Post: RE: Linux/AM5728: Ducatijpegdec GStreamer Plugin adds 8 extra lines of decoded image, produces incompatibility issue with VPE
All are tested without RGB patch and with RGB patch, on the newest processor SDK. 1. 'Scaling' as you specified ends in a segfault for me, with or without the RGB patch. 2. I see segfault in YUY2, interlacing issues with YUYV without RGB patch as well as with the RGB patch 3. Errors with and without patch as well, as specified above. My guess is that the segfaults are coming from the interface with between VPE and the Ducati. Backtrace log is attached. It's from PSDK 3.04, but I haven't made a PSDK 4.0 build with all the -dbg packages in yocto yet. I ran a GDB backtrace on the PSDK 4 pipeline though and it appears the same, but without the full trace. (Please visit the site to view this file)
↧
↧
Forum Post: RE: Linux/AM5728: Ducatijpegdec GStreamer Plugin adds 8 extra lines of decoded image, produces incompatibility issue with VPE
Hmm, I just tried it again with a new '1.mjpg' and it worked.... 1. scaling works with NV12 2. YUY2 works, YUYV causes a compatibility issue with waylandsink and kmssink, but I'm planning on using appsink in my final application so that's no big issue. 3. RGB patch and non-RGB patch pipelines tested. This may appear to be only on 'live' sources. In our final application we're going to be working with udpsrc, perhaps there is an issue with how ducati handles that type of source.
↧
Forum Post: RE: Linux/66ak2e05: Running 1Gig ethernet over a 10Gig ethernet interface
The 1GbE over XFI is not supported, and the auto-negotiation over XFI is also not working due to the 3rd party firmware issue. There isn't an existing example that can be referred to . The original design was meant to have GbE using one of the 8 GbE ports on K2E.
↧
Forum Post: Linux/AM3352: AM335x USB 2.0 COMPLIACE TEST PATTERN GENERATION
Part Number: AM3352 Tool/software: Linux We are in process of USB compliance testing, for which we have to generate standard test pattern on the USB host interface in order to analyze the output waveform. We tried to generate test patterns as described in link “ http://processors.wiki.ti.com/index.php/UsbgeneralpageLinuxCore#musb_driver_debugfs ”, but we facing following issues: Test_J, Test_K : Commands #echo "test K" > /sys/kernel/debug/musb-hdrc. X .auto/testmode & #echo "test J" > /sys/kernel/debug/musb-hdrc. X .auto/testmode & are observed to be working fine. TEST_PACKET: After executing command #echo "test packet" > /sys/kernel/debug/musb-hdrc. X .auto/testmode, no test packets are observed to be generated on USB0/USB1. Occasionally we have observed the USB packets on USB0 when no load is connected. What are we missing here? Do we need to follow any other procedure to see the generation of test packets? TEST_SE0_NAK: After executing command #echo "test SE0 NAK" > /sys/kernel/debug/musb-hdrc. X .auto/testmode, there is no activity observed on USB. How shall we test this? What are we missing here. We are using 3.12.10 kernel.
↧
Forum Post: RE: Linux/PROCESSOR-SDK-AM437X: Win7 can't recgonize the USB mass storage 2nd time when unplug the usb while the read test running and then plug the usb again
Hi Cvetolin Shulev-XID, I have found a WA for this issue, as following: diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c index a83f79b9..01755d6 100644 --- a/drivers/usb/dwc3/gadget.c +++ b/drivers/usb/dwc3/gadget.c @@ -2708,6 +2708,7 @@ static void dwc3_gadget_interrupt(struct dwc3 *dwc, switch (event->type) { case DWC3_DEVICE_EVENT_DISCONNECT: dwc3_gadget_disconnect_interrupt(dwc); + dwc3_gadget_reset_interrupt(dwc); break; case DWC3_DEVICE_EVENT_RESET: dwc3_gadget_reset_interrupt(dwc); I think this is a potential bug of the dwc3 driver, how do you think? Thanks.
↧
↧
Forum Post: RE: Linux/dra726: QSPI boot on dra726
Pavel, I hacked the mmc drivers in u-boot and linux and the problem is gone. I had to add a patch after the micro SD was always recognized correctly but if I had the micro SD card inserted it could not boot. Now the mmc is labeled according to the order of the mmc and not which one is recognized first. That way the eMMC is always recognized as mmcblk1 Next for me is Early boot, late attach. I have some issues with the documentation for the Linux kernel, could you help on that ? I will post in a different message Michel Catudal ACTIA Corp
↧
Forum Post: Linux/DRA726: Early boot - late attach on DRA726
Part Number: DRA726 Tool/software: Linux I need to connect early with the Cortex M4 on IPU1, we have 5 CAN ports to handle and need a wake up on CAN with one of them. Right now it takes around 11 seconds for the wakeup to be recognized which is about the time that it takes to get to the M4 code. I don't have quite enough information to fully understand how to implement the Linux portion of things. I do not see any good information on how to load the module when booting in Falcon mode. I was looking thru the processors.wiki.ti.com/.../Early_Boot_and_Late_Attach There is a problem with the info Device Drivers ---> Remoteproc Drivers ---> OMAP remoteproc support [*] OMAP remoteproc support for IPU [*] Attach to already-running IPU2 (no reset/load/start) [*] OMAP remoteproc support for DSP [*] OMAP remoteproc support for IPU1 (DRA7xx only) [ ] Attach to already-running IPU1 (no reset/load/start) [*] OMAP remoteproc support for DSP2 (DRA7xx only) Actual possible setting in the kernel Device Drivers ---> Remoteproc Drivers ---> OMAP remoteproc support [*] OMAP remoteproc watchdog timer [*] Attach to already-running IPU2 (no reset/load/start) STE-Modem remoteproc support TI PRUSS remoteproc support That is with kernel 4.4.45 coming with the TI 3.02 automotive SDK The memory carveaout in the dra7xx code in u-boot and the kernel is outside of the memory for our board Here is the content of my portion of the device tree in the kernel, does it look good? 1M seems a little big, how much does it actually need? /* * Memory reserved for IOMMU table carveout 0xa0000000 for length 0x100000 * Page Table Address for IPU1 0xa0000000 */ &reserved_mem { latea_pagetbl: late_pgtbl@a0000000 { reg = ; no-map; status = "okay"; }; }; &ipu1 { ti,late-attach; ti,no-idle-on-init; ti,no-reset-on-init; }; &timer11 { ti,late-attach; ti,no-idle-on-init; ti,no-reset-on-init; }; &timer7 { ti,late-attach; ti,no-idle-on-init; ti,no-reset-on-init; }; &timer8 { ti,late-attach; ti,no-idle-on-init; ti,no-reset-on-init; }; Michel Catudal ACTIA Corp
↧
Forum Post: Linux/PROCESSOR-SDK-OMAPL138: How to add qt5/ and libQt* to Linux-devkit?
Part Number: PROCESSOR-SDK-OMAPL138 Tool/software: Linux My sdk is 'PROCESSOR-SDK-LINUX-OMAPL138 04_00_00_04' I want to use QT5. I referenced 'Sitara Linux Training: Hands on with QT' I checked my linux sdk tools, But it does not have qt5/(qmake...) and libQt* . -- qt5/qmake... -- [linux-devkit]:~/ti-processor-sdk-linux-omapl138-lcdk-04.00.00.04/linux-devkit/sysroots/x86_64-arago-linux/usr/bin> ls qt* ls: cannot access qt*: No such file or directory -- qt-lib -- [linux-devkit]:~/ti-processor-sdk-linux-omapl138-lcdk-04.00.00.04/linux-devkit/sysroots/armv5e-linux-gnueabi/usr/lib> ls libQt* ls: cannot access libQt*: No such file or directory ----------------------------------------------------------------------------------------------------------------------------------------------------------------- How to add qt5/(qmake...) & libQt* component to linux-devkit ? Thanks.
↧
Forum Post: RE: Linux/AM5728: Ducatijpegdec GStreamer Plugin adds 8 extra lines of decoded image, produces incompatibility issue with VPE
Hello, I am glad that is working on your side. [quote user="Tom Wallis"]2. YUY2 works, YUYV causes a compatibility issue with waylandsink and kmssink, but I'm planning on using appsink in my final application so that's no big issue.[/quote] I asked only to try with yuy2 yuyv only for the tests. In this case you could connect the vpe to the fakesink element. [quote user="Tom Wallis"]This may appear to be only on 'live' sources. In our final application we're going to be working with udpsrc, perhaps there is an issue with how ducati handles that type of source.[/quote] Could you try to remove multicast-iface property and give a try? BR Margarita
↧
↧
Forum Post: RE: Linux/dra726: QSPI boot on dra726
Hi Michel, Glad to see you have fixed your issue. Could you mark this thread as resolved. I will have a look in your another e2e thread and provide hints if I have something there. Regards, Pavel
↧
Forum Post: Linux/AM5728: Ducati gstreamer plugins error: "Could not initialize supporting library"
Part Number: AM5728 Tool/software: Linux I'm trying to use hardware accelerated video codecs on customboard, based on sitara am5728 processor, with ti-sdk-03.03.00.04. But when I'm trying to execute any pipeline, using ducati encoders or decoders, from this ti wiki guide processors.wiki.ti.com/.../Processor_Training:_Multimedia , it stops with following error. As I understand it's something wrong with DSP libs for hardware codecs, how can I fix this problem?
↧
Forum Post: RE: Linux/AM5728: Ducati gstreamer plugins error: "Could not initialize supporting library"
Hello, Could you try pipeline like: gst-launch-1.0 videotestsrc num-buffers=100 ! 'video/x-raw,format=(string)NV12,width=1280,height=720' ! ducatih264enc ! h264parse ! filesink location=1.h264 Let me know the result? Are you observing this problem with the decoders also? Are you made some changes connected with gstreamer ot IPUMM ? BR Margarita
↧