Activity
From 11/09/2013 to 12/08/2013
12/06/2013
- MF 11:49 AM Software Development: RE: Accessing SPI1 bus
- I don't see a SPI /dev/ entry.
Tried this (as in the example at https://www.kernel.org/doc/Documentation/spi/spidev_test.c) - GG 11:07 AM Software Development: RE: Accessing SPI1 bus
- Hi Mary,
Reading and writing over a SPI bus on Linux is pretty simple. You need to open a file descriptor for the SPI /dev/ entry and use ioctl SPI_IOC_MESSAGE commands to send spi_ioc_transfer structs to the device.
Here's a for... - How do you read/write to a device on the SPI1 bus (CS1) on the ARM side? Is there an example? Can I do low level register read/writes or is there a driver?
I am using MDK_2012-08-10
I have recompiled the kernel with a custom base... - JC 09:43 AM Software Development: RE: First base with USB, OMAP-L138F
- Once you have the network connection up you can easily move files using ssh and winscp.
- JC 09:39 AM Software Development: RE: First base with USB, OMAP-L138F
- It maybe of use to you to have the usb port act as a network device so you can send files over the network. See http://support.criticallink.com/redmine/projects/arm9-platforms/wiki/Enabling_USB_RNDIS_Support.
- I have inherited development responsibility for a custom base board using an OMAP-L138F SoM. I need to get USB working in one manner or another.
The cable designed by the board originator has a USB-A type plug on it, implying that ...
12/05/2013
- SH 02:59 PM Software Development: RE: DSP software sometimes does not start
- Thanks for the reply Mike - I took a look at my code and the Debug outbound is created before the inbound in the DSP software. In any case, the problem "went away" - after a couple of glitches after first loading the software in the /mn...
- MW 12:37 PM Software Development: RE: DSP software sometimes does not start
- I suspect that you may have a race condition between the ARM and the DSP setting up inbound and outbound message Qs.
The inbound message queues create local message q structures. The outbound message queues attempt to continuously a...
12/04/2013
- I have a strange problem with starting up some software on bootup. I have followed the instructions in this link:
[[http://support.criticallink.com/redmine/projects/arm9-platforms/wiki/ARM_Software_FAQs]]
with a line that looks like... - GG 01:46 PM Software Development: RE: Loading DSP-Code from Linux without DSPLink/DSPBios
- Hello Benedikt,
As far as I know, we've really only had experience running DSP code that uses the BIOS. Have you downloaded and looked at our MDK or our [[DSP Hello World]] starter guide? In the MDK we have a class called dspapp that... - Hej hej,
I have a coff-file with my DSP-Algorithm which runs perfectly when I start it via JTAG or via U-Boot. [Linux is up on the ARM in parallel. The communication between Linux and DSP is also working.]
Now I want to load the DS...
12/03/2013
- JC 04:21 PM Software Development: RE: Read-only file system using systemd for startup
- I think that's the first step. The programs that have problems should then print error messages in the boot log. Might make things easier to take a boot log of the rw and ro boots to compare them so you can find the errors easier.
- SH 04:19 PM Software Development: RE: Read-only file system using systemd for startup
- Yes, I was going to try just updating /etc/fstab and the bootarg environment variable and see if that works...what do you think?
- BD 02:48 PM Software Development: RE: Read-only file system using systemd for startup
- Stephen,
Do you have an /etc/fstab in your filesystem? Have you tried updating that file as described in step 4?
-Bob
12/02/2013
- There is a discussion of how to set up a read-only filesystem in the following link:
[http://support.criticallink.com/redmine/projects/arm9-platforms/wiki/Configuring_a_Linux_Filesystem_for_Uncontrolled_Shutdowns]
but the instruction... - MW 10:44 AM Software Development: RE: problem with spinlocks in linux kernel module
- Steven,
I think the reason why you see the difference is that your PC is likely a multi-core (multi-processor), on single core systems spin_lock and spin_unlock really don't do much for you because that is the only possible thread run... - Hi,
I tried to run a trivial test driver pasted in below on a PC using Redhat linux and on the ARM core of the OMAP-138 using Angstrom linux. The function "spinlock_test" trys to obtain a spinlock it has already by calling itself two ... - NK 12:51 AM Software Development: RE: "Regarding developing real time application"
- Hi Mike,
We are planning UART from linux on arm9 cortex. Or can you suggest any feasible solution in this regard, as we are planning DSP only for image algorithms.
With regards,
Naveen K S
11/30/2013
- MW 07:34 AM Software Development: RE: "Regarding developing real time application"
- Do you mean using a "UART from Linux":http://en.wikibooks.org/wiki/Serial_Programming/Serial_Linux? Or are you trying to use the UART with the DSP?
I'm afraid we can't help you design your application without detailed requirements.
... - Dear sir,
we are working on developing vision system, wherein we are using your mitydsp L138F SOM and Industrial I/o Board (as a sub system module in our entire system) for image processing. Our requirement is we need to interact with... - MW 07:29 AM FPGA Development: RE: Driving DVI-D with Spartan6 LX45 Fpga
- The issue cannot be resolved without redesigning the PCB.
If you are using an LX-45, you cannot use the DVI interface on the dev kit. Why Xilinx did not bond out these pins remains a mystery.
I am sorry for any inconvenience.
... - From the following discussion, it is said that Spartan6 LX45 FPGA based MityDSP-L138F SOM cannot drive DVI-D on Industrial IO boards. Is this case true now also or this issue resolved??
Kindly reply as soon as possible.
Thanks in Adv...
11/28/2013
- MW 07:52 AM Software Development: RE: "Regarding driving two displays using MitydspL138F vision development kit"
- The DVI interface on the L138F / Industrial I/O kit is DVI-D (see "wikipedia page about DVI interface types":http://en.wikipedia.org/wiki/Digital_Visual_Interface) compliant only.
To drive the displays you have attached using the VGA ... - "
ARM9 Based Platforms - Software Development: RE: "Regarding Driving Displays in MitydspL138F Vision Devlopement Kit"
Michael Williamson
If both the LCD display and the display connected to the DVI interface can run using the timin...
11/27/2013
- MW 08:09 PM Software Development: RE: "Regarding Driving Displays in MitydspL138F Vision Devlopement Kit"
- If both the LCD display and the display connected to the DVI interface can run using the timings (e.g., same resolution, same pixel clock rate, same front / back porch settings, same vertical refresh rate) then you should be able to run ...
- Hi sir,
Initially our requirement is to drive two displays in MitydspL138F VDK.
In Mitydsp L138F based vision development kit datasheets it was given LCD panel interface and DVI interface are provided. Can we drive two displays bot...
11/23/2013
- MW 03:34 PM FPGA Development: RE: JFFS2 driver errors
- You can do it in the DSP using tcDspSyscfg::SetMasterPriority() in the dsp core library.
-Mike
- SH 01:30 PM FPGA Development: RE: JFFS2 driver errors
- Thanks for those suggestions, Mike. According to Table 11-2, the default priority for EDMA is 0 (highest) and for ARM instruction and data is 2 (lower). When I look at these registers in debug mode (DSP), I see these default priorities...
- MW 08:40 AM FPGA Development: RE: JFFS2 driver errors
- Hi Steven,
Is the DMA priority configured higher than the ARM data access priority in the Master Priority Configuration registers (see the OMAP-L138 Technical Reference Manual regarding DMA bus mastering priority)?
We have seen FPG...
11/22/2013
- I'm seeing some errors similar to those mentioned in the following thread:
http://support.criticallink.com/redmine/boards/12/topics/2954
I am using the CL FPGA modules for EMIF, etc with no changes and making DMA transfers from the FP...
11/21/2013
- MW 07:14 AM Software Development: RE: Compiling the HelloWorld application with CGT
- You should dump out the full build texts between the two operations and compare.
I suspect that the memory configuration templates (which define the shared regions for DSPLINK) are somehow not the same between the 2 builds.
-Mike
11/18/2013
- Hi,
I was trying to compile the DSP HelloWorld Application available at the following location. http://support.criticallink.com/redmine/projects/arm9-platforms/wiki/DSP_Hello_World. I got both the ARM side and the DSP side files to co... - BK 11:58 AM Software Development: RE: EDMA conflict DSP <-> Linux
- Hej Mike,
I just checked the master priorities. I changed it to the following values:
> 0: EDMA3_0_TC0
> ...
I use EDMA3_0_TC0 for the McASP-transfers and EDMA3_0_TC1 for all other requests.
Unfortunatly the behavior is exactly t... - MW 10:42 AM Software Development: RE: EDMA conflict DSP <-> Linux
- The reservation of resource may be non-sense, but the resources specific to device drivers (like McASP channel queues) will not be touched by the linux kernel if the drivers are not activated, so I suspect that is not the problem.
Ins... - BK 09:54 AM Software Development: RE: EDMA conflict DSP <-> Linux
- The bug was in the param-sets of the edma which were not set correctly in my application.
But now I have another issue with the edma:
I use linux on the ARM to configure external devices via I2C like DAC/ADCs and to communicate via... - BD 10:06 AM Software Development: RE: Linux startup with app running after boot
- Steven,
Once you have your program output going to stdout, you can redirect it to a file that can be viewed after the system boots: - JC 09:31 AM Software Development: RE: Linux startup with app running after boot
- You should be using normal stdout printf's in your program and not opening the serial port.
11/16/2013
- SH 08:13 PM Software Development: RE: Linux startup with app running after boot
- I was wrong about starting the app with the full pathnames for both the app and the DSP executable. I wrote a service to start it up that way, and it works, but it crashes the terminal program (I am using Putty) and I have to restart my...
11/15/2013
- SH 07:26 PM Software Development: RE: Linux startup with app running after boot
- Thanks for that, but how do you do the same thing with a systemd service? My filesystem is using systemd for startup.
- TI 06:30 PM Software Development: RE: Linux startup with app running after boot
- Steven
In your script that runs the app, just "cd" to the correct directory. I.e.
cd /mnt/user_nand
./myApp mydspExecutable &
cheers
/Tim - SH 06:27 PM Software Development: RE: Linux startup with app running after boot
- I have what might seem like a dumb question. I like the idea of starting the app as a service, and I have written and tested a service that loads the fpga_ctrl and DSPLink modules on startup. My application and the files it needs to ru...
11/12/2013
- JC 02:33 PM Software Development: RE: EDMA conflict DSP <-> Linux
- Was the bug in the kernel or your application?
- BK 02:09 PM Software Development: RE: EDMA conflict DSP <-> Linux
- Found the reason. The DMA configuration was wrong.
- TI 07:59 AM Software Development: RE: Linux startup with app running after boot
- Steven
One other note..
If you are using a newer filesystem with systemd (does /etc/systemd exist) things are a bit different. The link in step 4 talks about it a bit.
cheers
/Tim - TI 07:52 AM Software Development: RE: Linux startup with app running after boot
- Steven
1 - No you don't need to log in as root... the init system will run your script for you. One thing that may catch you (it got me) is that HOME will not be defined when your script is run by init.
2 - Copy a simple script in /e...
11/11/2013
- I am at the final stage in getting my project working on the MityDSP L138 board. I want to load the FPGA control module and the DSPLink module and then start my application, which is designed to run until the sun goes nova or the batter...
11/09/2013
- BK 06:06 PM Software Development: RE: EDMA conflict DSP <-> Linux
- Hej Mike,
I'm using my own board and also my own baseboard-configuration.c which is based on your baseboard-industrialio.c. I removed everything related to SPI, McASP and USB - espacially the functions
> baseboard_setup_spi();
> ......