Activity
From 10/28/2013 to 11/26/2013
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();
> ......
11/08/2013
- MW 01:56 PM Software Development: RE: EDMA conflict DSP <-> Linux
- What baseboard file are you using?
The devkit one configures MCASP for use by the ARM/linux. Could be a resource contention?
The board-da850-evm.c code is reserving EDMA channels such that the linux OS doesn't try to use them. ... - Hej,
I try to use the EDMA to copy data from the McASP to and from a buffer for further processing on the DSP.
If I don't use the EDMA but McASP interrupts to copy the data it works fine, but when I try to use the EDMA it does not ...
11/05/2013
- BD 10:37 AM Software Development: RE: How to launch application on startup
- MF 09:55 AM Software Development: RE: How to launch application on startup
- So, from the command line:
- MW 07:05 AM FPGA Development: RE: uPP receive issues
- Yes, this is the issue. The pin-muxed OMAP-L138 net that includes the UPP_CHB_CLOCK is not connected to a GCLK pin. We didn't have the routing resources (or the clock pins) to connect every possible clock pin on the OMAP-L138 to a GCLK...
- MT 06:18 AM FPGA Development: RE: uPP receive issues
- I have resolve that problems. Maybe I was wrong to select uPP clock sources (PLL1_SYSCLK2).
But, when my FPGA sytem is bigger. I have an other bugs when mapping the logic.
Place:1108 - A clock IOB / BUFGMUX clock component pair hav...
11/04/2013
- BD 01:09 PM Software Development: RE: How to launch application on startup
- Mary,
When you exit a shell, all processes connected to the shell are typically terminated. When you execute a script, the shell used to run the script terminates at the end. Your application is probably being terminated prematurely.... - JC 12:54 PM Software Development: RE: How to launch application on startup
- Do you happen to know if your system is using systemd for starting processes?
You can check to see if the following directory exists: /etc/systemd/
If you have a filesystem that uses systemd then reading the following may be helpfu... - JC 12:48 PM Software Development: RE: How to launch application on startup
- You can run the command "ps | grep myApplication" and look for your process in order to tell if its running.
Also normally you would redirect output from the console to a log file for your application, something like:
/home/root/He... - JC 12:44 PM Software Development: RE: How to launch application on startup
- Mary,
I think you have a typo here:
./home/root/HelloWorldDSP/Debug/myApplication myArgument &
There shouldn't be a period at the beginning of the line. - Could you provide an example of how to start an application on startup. I get that you can run it from a script in init.d which is referenced in rc5.d. My problem is that if I start it in the background (even from a shell command) it s...