Activity
From 01/08/2016 to 02/06/2016
02/04/2016
- DV 03:59 PM MitySOM-5CSX Altera Cyclone V Software Development: RE: Board info files MittySOM-5cse-l2-3y8
- Hello Brian,
Are you trying to manually by hand create the DTS or are you using the Altera Sopc2dts tool that will take the output of your quartus build and create the DTS for you?
We normally go about creating the DTS by hand. The... - I'm having trouble creating a dts file that shows the peripherals on the fpga of my design. I can't find the correct xml board info files needed to create the dts file. Any help would be appreciated. The goal is to create all the necessa...
- BA 01:37 PM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: gcc 4.8 for OMAP-L138
- Jonathan,
Thank you very much for your help. This uImage works.
Regards,
Ben - JC 12:53 PM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: gcc 4.8 for OMAP-L138
- Updated dbric3 defconfig to support systemd.
http://support.criticallink.com/gitweb/?p=linux-davinci.git;a=commit;h=1c88227846c09e6d482ebcc3b898b94dc05f3ae0
I setup the toolchain and built the kernel for you. See attached. - BA 12:17 PM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: gcc 4.8 for OMAP-L138
- Jonathan,
Yes I am using the dbric3 hardware. Do you have a kernel image for it?
Regards,
Ben - JC 12:09 PM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: gcc 4.8 for OMAP-L138
- The industrialio baseboard image expects the phy id to be 0:03. Your phy id appears to be 0:00. The kernel would need to be rebuilt with the correct phy id.
arch/arm/mach-davinci/baseboard-industrialio.c - BA 11:38 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: gcc 4.8 for OMAP-L138
- ... and here is the boot message file.
- BA 11:36 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: gcc 4.8 for OMAP-L138
- Jonathan,
I think we're getting somewhere now. The newest kernel is working better. I went back to the original, unmodified Critical Link JFFS2 FS and the new uImage kernel, and I no longer get the ipv6 messages, and I the /dev/ttyS... - JC 09:30 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: gcc 4.8 for OMAP-L138
- Alright thanks. Sometimes the bootargs aren't set.
I tried booting the uImage Bob posted and it hung for me too. I've re-uploaded the uImage and this one appears to work. Sorry for the trouble.
You can find it on the Files tab or ...
02/03/2016
- BA 05:10 PM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: gcc 4.8 for OMAP-L138
- Jonathan,
U-Boot > print bootargs
print bootargs
bootargs=mem=96M console=ttyS1,115200n8 mtdparts=nand:128M(rootfs),-(userfs) root=/dev/mtdblock0 rw,noatime rootfstype=jffs2
U-Boot >
Regards,
Ben - JC 05:05 PM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: gcc 4.8 for OMAP-L138
- Is the bootargs environment variable set when you do the tftp boot?
- BA 05:01 PM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: gcc 4.8 for OMAP-L138
- Bob,
On my target system I had:
# cd /boot
# ls -la u*
lrwxrwxrwx 1 root root 13 Nov 13 21:13 uImage -> uImage-3.2.0+
-rw-r--r-- 1 root root 2538632 Nov 13 19:50 uImage-3.2.0+
When I did a binary file comparison be... - BD 04:08 PM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: gcc 4.8 for OMAP-L138
- Ben, you shouldn't have to redo your filesystem. Just copy over the kernel.
- BA 03:33 PM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: gcc 4.8 for OMAP-L138
- Bob,
Thanks. Just to be clear, should I put the new uImage in /boot and re-create the jffs2 image? Currently the following is in /boot:
- uImage -> uImage-3.2.0+
- uImage-3.2.0+
My target is a custom board.
Regards,
Ben - BD 03:08 PM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: gcc 4.8 for OMAP-L138
Ben, I apologize for the assumptions in my original advice. Any time you change a kernel you need to bring along the asociated modules (typically located in /lib/modules) for that kernel. You would've needed to grab the /lib/modules/...- BA 02:55 PM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: gcc 4.8 for OMAP-L138
- I did not build a new kernel. A kernel was already on my target system, and I believe it came from the MDK_2014-01-13.
The only thing I did was:
- Took the mitydsp-l138-rootfs.tar.bz2 from the ALPHA 2016.01 and added my /etc/networ... - JC 02:47 PM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: gcc 4.8 for OMAP-L138
- Ben Atkinson wrote:
> Jonathan,
> ...
Did you build the kernel your currently booting from or was it copied from the old MDK_2014-01-13? - BA 02:44 PM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: gcc 4.8 for OMAP-L138
- Jonathan,
Thanks for the reply. I didn't build a new kernel based on the comment from Bob Duke, above:
> Please note that our current kernel will not compile with this SDK. We have a fix,
> but it is not released yet. If yo... - JC 02:20 PM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: gcc 4.8 for OMAP-L138
- Ben Atkinson wrote:
> Jonathan,
> ...
The kernel your booting doesn't match the kernel modules its trying to load. Delete the kernel modules in /lib/modules/ and replace with modules from kernel you built. - BA 02:09 PM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: gcc 4.8 for OMAP-L138
- Jonathan,
I was able to load your ALPHA Linux file system onto my target, and I've had some success. The system is running, and I can establish an SSH terminal connection to it.
I've attached two dumps from the console as the syst...
02/01/2016
- JC 10:49 AM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- Fred, I'm not sure what is wrong. Perhaps if you sent us your schematic someone could look it over.
I'm pretty sure the spidev driver works. However you could try implementing a simple kernel driver to access the spi calls directly....
01/29/2016
- FF 03:08 PM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- A single IOCTL call with len=4 returns 4 bytes of 0 value instead of 2 with no difference in the SPI signals.
- JC 12:04 PM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- I believe you want a single IOCTL. See the attached source code duplex method.
Example usage - FF 11:51 AM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- Correction in above code
fd = open(devname, O_RDWR|O_SYNC);
should be
fd = open(devname, O_RDWR); - FF 11:49 AM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- This is based on spidev_test.c and other examples. There are two devices on the bus that have to be configured to read address input pins before they can be configured. That is working fine since the correct device is responding to the ...
- JC 11:06 AM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- Fred Frantz wrote:
> Yes, I am looking at all the SPI0 signals on a scope, and they are correct. The transmitted data is configuring the devices correctly, and the received data from the device on d1 is correct, but it is not returned ... - FF 11:02 AM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- Yes, I am looking at all the SPI0 signals on a scope, and they are correct. The transmitted data is configuring the devices correctly, and the received data from the device on d1 is correct, but it is not returned from ioctl(). I have v...
- JC 10:44 AM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- Fred Frantz wrote:
> The data is now being clocked out correctly, and the device is responding with the correct data on the spi0_d1 line.
Does this mean you have a spi analyser attached to the bus?
- JC 10:42 AM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- Fred Frantz wrote:
> Mike, are you referring to the .d0_is_mosi parameter in the ompa2_mcspi_device_config structure?
Yes. You should have it correct if you are seeing the data output coming on the correct pin.
> ...
Not that I can th... - FF 10:36 AM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- Mike, are you referring to the .d0_is_mosi parameter in the ompa2_mcspi_device_config structure? That is set to 1, but all of the SPI_MODE's give a similar result. All the data bytes returned are the same value, which is not what is be...
01/28/2016
- MW 12:12 PM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- I think there is also a control for the McSPI that can swap the din / dout pins between "d0" and "d1". We had trouble with this in the past.
-Mike - JC 12:06 PM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- Fred Frantz wrote:
> Thanks for the correction. Setting the .bus_num = 1 solved the module issue, and the .controller_data information is required for the spi0_d0 line to be used as MOSI.
> ...
It should be correct. If data is coming... - FF 11:59 AM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- Thanks for the correction. Setting the .bus_num = 1 solved the module issue, and the .controller_data information is required for the spi0_d0 line to be used as MOSI.
The data is now being clocked out correctly, and the device is re...
01/27/2016
- JC 09:34 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: gcc 4.8 for OMAP-L138
- Ben,
Part of the reason this filesystem is alpha is to discover differences from the old filesystem. We hadn't noticed this so good catch. Could you try creating the interface file and report back whether it worked? - BA 09:29 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: gcc 4.8 for OMAP-L138
- I want to set a static IP address on my target using the ALPHA Release 2016.01 file system, but I was surprised to see the /etc/network/interfaces file didn't exist in the file system image. I expected to see this file populated with so...
01/26/2016
- JC 05:02 PM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- Fred Frantz wrote:
> After erasing the NAND, the ECC errors are resolved. Thanks, that was a self inflicted problem due to misinterpretation of our documentation.
Glad that helped.
> ...
The SOM is using the spi1 bus to talk to the NO... - JC 04:54 PM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- Michael Williamson wrote:
> SPIDEV sits on top of McSPI. It's an abstraction layer on top of the specific SPI driver. That may be the problem.
What Mike said. The McSPI driver is necessary for the spidev driver to work.
> ...
He h... - MW 03:49 PM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- SPIDEV sits on top of McSPI. It's an abstraction layer on top of the specific SPI driver. That may be the problem.
You may need to configure (either via a platform file or via device tree) a SPIDEV device that is attached to a speci... - FF 03:36 PM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- After erasing the NAND, the ECC errors are resolved. Thanks, that was a self inflicted problem due to misinterpretation of our documentation.
Can the McSPI conflict with SPIDEV if both are trying to access the same port? Disabling Mc... - JC 11:44 AM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- Jonathan Cormier wrote:
> For your case you just need to erase the kernel section.
> ...
Do double check my math on this, if wrong it could erase part of your filesystem image.
- JC 11:43 AM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- > U-Boot# tftp 0x82000000 $serverip:uImage
> ...
By writing the nand like this without erasing, you will corrupt the image stored including the ECC. Nand flash must be erased before writing to it.
Note in the following guide I erase ... - FF 11:17 AM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- The kernel and environment were reloaded just to get to a known point where everything was working previously. The kernel is being loaded via tftp.
U-Boot# tftp 0x82000000 $serverip:uImage
U-Boot# nand write.i 0x82000000 0x340000 $... - JC 10:39 AM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- Just checked and the 0x340000 address the ECC errors mention is the location of the kernel not the environment I initially assumed. How are you loading the kernel to boot the system if loading it from nand isn't working (tftp)? How are...
- JC 09:35 AM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- Fred Frantz wrote:
> Thanks for the suggestions, but ZCAT on the target indicates that SPIDEV is enabled.
Interesting. My troubleshooting steps when trying to diagnose a driver not loading is the following.
* Check the boot log for ... - FF 09:13 AM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- Thanks for the suggestions, but ZCAT on the target indicates that SPIDEV is enabled. Regarding the ECC errors, I reloaded an earlier version of the kernel and an environment variable file that was working without any problems, but the E...
01/25/2016
- JC 05:33 PM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- Hmm no noticeable errors. You can double check the kernel, on the booted device for the spidev support:
- FF 04:21 PM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- I added the boot log for the ECC errors also.
- FF 03:39 PM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- Hope this helps.
- JC 03:15 PM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- Can you attach the bootlog for the device?
- FF 03:09 PM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- It looks like it is enabled to me.
- JC 01:41 PM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: Spidev issues
- A pinmux conflict would likely cause the device not to work but it would not affect the creation of the spidev device file.
You need to make sure that SPIDEV is enabled in the kernel. It doesn't look like it is by default. - The dev kit baseboard file has been modified to include a "spidev" device, and the kernel was compiled to include the SPI device driver for users. However, the expected /dev/spidev0.1 file is not generated. Can a pinmux conflict with o...
- MJ 03:16 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: MityDSP-L138F - Qt application not seeing USB keyboard
- Hi
Thanks, I did very quickly look at the 2015 Alpha release but didn't see the Qt libraries.
At the same time I was investigating the Qt 'configure' parameters posted above and what is suggested by https://wiki.qt.io/Building_Qt_for_E...
01/21/2016
- FF 08:56 AM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: SocketCAN configuration
- After the links were corrected on my system, it works using iproute2 also.
Thanks
01/20/2016
- JC 05:05 PM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: SocketCAN configuration
- Apparently the filesystem ip utility isn't using busybox.
- JC 04:37 PM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: SocketCAN configuration
- It would be the busybox that comes in the TI filesystem we ship with the devkits.
- FF 04:32 PM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: SocketCAN configuration
- Thanks for the quick response. What version of busybox are you using?
Thanks,
Fred - JC 03:24 PM MitySOM-335x (ARM Cortex-A8 Based Products) Software Development: RE: SocketCAN configuration
- I used the busybox ip utility to configure can when I last tested it.
I found the following script which I created to configure can.
attachment:config_can.sh
See the following cantest script which is used to test can by connecting... - What is the recommended method for configuring a socketCAN port on the MitySOM3354? I have tried using the iproute2 utility as described in the TI instructions.
http://processors.wiki.ti.com/index.php/AM335X_DCAN_Driver_Guide#Building... - JC 11:23 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: gcc 4.8 for OMAP-L138
- Here is the command we run to create the jffs file for the original MDK. Where $root is the path to the extracted filesystem.
- BA 11:01 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: gcc 4.8 for OMAP-L138
- We have a tool that reprograms the root FS on our target device with a jffs2 file. I saw in the Release 2010.05 there are root FS files in both the jffs2 file and a tar.gz file. Do you have a tool or procedure that can convert the mity...
- BD 10:38 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: MityDSP-L138F - Qt application not seeing USB keyboard
Mat,
You could try testing the Alpha MDK release we uploaded under the Files tab (2016.01). This is a Yocto-based MDK. It looks like Qt was built with keyboard support as part of this MDK.
- MJ 03:13 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: MityDSP-L138F - Qt application not seeing USB keyboard
- That's interesting, so it does look like the 12/03/2012 MDK (with Qt 4.7.4) was built with -qt-kbd-tty but not with: qt-kbd-qvfb and qt-kbd-linuxinput.
I noticed that it +does+ have the mouse support (-plugin-mouse-tslib -qt-mouse-pc -q...
01/19/2016
- JC 03:19 PM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: MityDSP-L138F - Qt application not seeing USB keyboard
- The build logs for the 4.7.4 qt show the following configure. According to this neither qt-kbd-linuxinput nor qt-kbd-linuxinput were built but qt-kbd-linuxinput was.
- MJ 10:56 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: MityDSP-L138F - Qt application not seeing USB keyboard
- Hi Jonathan, thanks, I've read something similar or the same links.
I've just tried - JC 09:13 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: MityDSP-L138F - Qt application not seeing USB keyboard
- http://doc.qt.io/qt-4.8/qt-embedded-charinput.html#specifying-a-keyboard-driver
The above link lists the TTY and LinuxInput driver as what would be needed for keyboard input.
According to this link https://wiki.qt.io/Building_Qt_...
01/18/2016
- MJ 08:17 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: MityDSP-L138F - Qt application not seeing USB keyboard
- Hi Tim
I am currently launching my application with the -qws flag, e.g. - TI 07:14 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: MityDSP-L138F - Qt application not seeing USB keyboard
- Mat,
Its been a while since I have worked in this area, so I'm a bit rusty... Are you launching your app with the -qws flag? This tells the Qt framework to start up the input server and might explain things...
cheers
/Tim - Hi
I'm having trouble with Qt getting input from a USB keyboard. USB mouse input is fine.
I have a MityDSP-L138 running on the IndustrialIO dev board, connected to a monitor via DVI.
The USB keyboard happily works with the console o...
01/15/2016
- AD 02:57 PM MitySOM-5CSX Altera Cyclone V FPGA Development: RE: LVDS transceiver for 1000Mb Ethernet MAC & 1000Base-X problem
- Hi Charles,
The GXB TX details can be found in Altera's documentation:
https://www.altera.com/content/dam/altera-www/global/en_US/pdfs/literature/hb/cyclone-v/cv_5v3.pdf
Are you using the on-chip biasing network and termination, o...
01/13/2016
- MJ 08:52 AM MityDSP-L138 (ARM9 Based Platforms) FPGA Development: RE: Linux application cannot read/write FPGA registers
- Hi Greg
Excellent, that has definitely helped as I can now see /dev/0 after the following two commands (with FPGA loaded from uBoot).
01/12/2016
- MW 12:43 PM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: DVI Framebuffer (fpga i2c) problem
- Hi Mathew,
Very sorry about that. I didn't catch the LX45 version. The LX45 has some pins that are not bonded to the FPGA package causing the limitation on our devkit (originally designed for the LX16).
Are you using a widescree... - MJ 11:26 AM MityDSP-L138 (ARM9 Based Platforms) Software Development: RE: DVI Framebuffer (fpga i2c) problem
- From our investigation and suggestions from other wiki/forum pages it is apparent now that it is not possible to output to a DVI monitor from a MityDSP-L138 + Industrial IO development board, with the LX45 FPGA. We have since purchased t...
- GG 11:35 AM MityDSP-L138 (ARM9 Based Platforms) FPGA Development: RE: Linux application cannot read/write FPGA registers
- Hi Matthew,
First we need to deal with the issue of /dev/0 not being present. Using /dev/mem is ultimately not what you want to do as you will run into caching issues.
/dev/0 is created after the FPGA is loaded and the device driv... - I am trying write a simple C application (for Linux on the MityDSP-L138 ARM) that can access registers within an LX16 FPGA image, which is yet to be implemented but I'd like to get the basics working for now with any of the CriticalLink ...
- Hi,
I have been attempting to use the development kit to setup and implement a system which interfaces to an externally connected SFP module which I have connected via the SPIe connection to the dev board. I instantiated the TSE Ethern...