Activity
From 06/15/2011 to 07/14/2011
07/14/2011
- MW 02:03 PM Software Development: RE: uPP/DMA registers
- You will definitely need to configure the pin mux. You should assume that the UPP is powered down (in the reset state) as well. You may need to add the UPP clock to the clock tree in linux and turn it on, I haven't checked if that has ...
- SW 01:58 PM Software Development: RE: uPP/DMA registers
- Mike,
Thanks for the link to the OMAP specification. I think that is all I needed to start work on my driver. In the default mityDSP configuration, are the clocks and power enabled to the uPP? I assume I will need to set the pin m... - MW 01:13 PM Software Development: RE: uPP/DMA registers
- Hi Scott,
Unfortunately, TI (nor Critical Link) provides linux drivers for the UPP.
The memory map that includes the base address of the UPP peripheral is in the "OMAP-L138 specification":http://www.ti.com/lit/gpn/omap-l138. The r... - Hello,
I want to use the uPP and EMIFA to pass data between an FPGA and the ARM on the OMAP. I think I've got what I need for the EMIFA, pick one of the available chip selects and create a driver to remap that memory. I'm a bit lost...
07/13/2011
- MW 03:17 PM Software Development: RE: Default Clock Speed
- No, it won't change the clocks. It will just feed the RTOS the correct numbers.
You really should set the frequency using the ARM unless you are not running any OS on it at all. The linux OS needs to know about changes made to the P... - ML 02:55 PM Software Development: RE: Default Clock Speed
- Will GBL_setFrequency(); actually change the clock, or just feed the RTOS will correct numbers like you were talking about?
My goal is to set the OMAP to 375MHz, preferably using the DSP and CCS. - MW 02:49 PM Software Development: RE: Default Clock Speed
- Hi,
I want to clarify a couple of things here.
The DSP and the ARM clocks are driven by the same system clock. Modifying the ARM modifies the DSP clock.
The MityDSP modules (i.e., the OMAP-L138/ARM-1808/ARM-1810) come up at 300... - GG 02:07 PM Software Development: RE: Default Clock Speed
- Hi Marc,
The boards default to running at 300 MHz, though they can be run at 456 MHz. You can change this in the DSP in two ways. You can do this statically by double clicking the .tcf file in your project, going to "Global Settings,"... - Hey All,
What speed will an out of the box MityDSP-L138 run at? I was under the assumption it was 456MHz, but when I look in the provided .tcf it says 300MHz. Any information would be much appreciated.
-Marc
07/06/2011
- MW 05:13 PM Software Development: RE: core/regs_gpio.h
- Hello Mads,
Thanks for the heads up on the GpioRegs structure. You are right, that is indeed an error in the file.
There is also an error in J701 GP0_N connections in the Industrial I/O card sheet. For Rev-E and higher boards, th... - Hi
I had some trouble getting GPIO working correctly in the OMAP.
Until I found out that the below structure is wrong...
typedef struct GpioRegs
{
volatile uint32_t REVID;
volatile uint32_t BINTEN;
tsGpioBankPair BANKPA... - Dear Sir,
I am looking for an evaluation board that supports real-time embedded linux.
I found that MityDSP-L138 uses TI 2.6.33 kernel with Real Time Extensions.
If possible, could you give me more information about Real Time Extens...
07/05/2011
- MC 02:23 AM Software Development: RE: MITYDSP OMAP-L138 EMIF FPGA / NAND shared bus access
- Hi Mike
Many thanks for your reply.
It is really latency we are worried about. We won't be transferring a lot of data, but timing is important.
We will have a look at the UPP interface.
Thanks,
Mads
07/04/2011
- MW 03:03 PM Software Development: RE: MITYDSP OMAP-L138 EMIF FPGA / NAND shared bus access
- Hi Mads,
NAND does share the EMIF bus with the FPGA and you may run into a potential latency issue if you do not manage the accesses. NAND acceses, particularly writes, may be rather slow as the device can stall the bus (it uses the ... - Hi
This is NOT a problem we are seeing (yet?), but we are wondering whether this is a problem we might be seeing in the future.
We have the OMAP-L138 module where the ARM side will be running Linux and DSP side SYS/BIOS.
Our con... - MC 10:32 AM Software Development: RE: HelloWorldARM DSPLINK example causes Assertion failed
- Hi Greg
Sorry I haven't replied yet.
Has been busy on other tasks, and this was a low low priority :-)
I have built the dsplinkk.ko myself. It might very well be the problem.
I will have a look into it, some time soon hopefully.
...
07/03/2011
- MW 01:36 PM Software Development: RE: mtdblock kernel crash
- Oh, if you need an /dev/mtdx device, you need to enable in the kernel:
CONFIG_MTD_CHAR
Should be in the device drivers->MTD config page.
Never had the chance to use mdev, but the device should be major 90, minor is 2x the device... - MW 01:31 PM Software Development: RE: mtdblock kernel crash
- Hi Zoltan,
Well, for the SPI issue, I have some information for you along with couple of work-arounds. Feel free to skip to the bottom for those if you like. Please note that there will also be some additional patches to the davinci...
07/02/2011
- CM 11:05 AM Software Development: RE: Eval Board will not boot
- I tried re-seating the module several times with no success. Got same results with another kit's cables so I think cables are ok. Checked continuity of serial connector pins from socket on front thru holes to back of board and they all c...
07/01/2011
- MW 01:08 PM Software Development: RE: Eval Board will not boot
- Hi Craig,
Other than trying to re-seat the module and the serial port cables in their respective connectors, I don't have any other suggestions. If the board is not presenting the "BOOTME" description, then there must be hardware fa... - CM 11:50 AM Software Development: RE: Eval Board will not boot
- Did as instructed but did not see BOOTME on console.
Board serial # is 110251. - MW 11:39 AM Software Development: RE: Eval Board will not boot
- Hi Craig,
Can you please monitor the console (115200 baud, no flow control) and, while holding the boot button down, press the reset button? You should see "BOOTME" appear on the screen. Can you please confirm?
Also, can you plea... - Purchased 3 kits 80-000268RI-1 with SoM L138-FI-225-RC. One kit does not boot when power is applied. Green LED does light to indicate power. Monitoring serial port in hyperterminal same as we did for the other two kits that boot fine. Fo...
- GG 10:12 AM Software Development: RE: HelloWorldDSP.out syntax error
- Hi Marc,
Before you run the application, run the command: - ML 10:10 AM Software Development: RE: HelloWorldDSP.out syntax error
- Greg,
Is there anywhere in the wiki that explains how to set up the dsplink driver on the ARM? When I run ./HelloWorld HelloWorldDSP.out it fails to open the driver, which should be located in /dev/dsplink according to the error I ge... - GG 09:44 AM Software Development: RE: HelloWorldDSP.out syntax error
- Hi Marc,
With the latest MDK there is no need to rebuild DSPLink. I've updated the DSP Hello World wiki page to outline where the libraries are located that you need to link against in order to build the Hello World example for the AR... - ML 09:13 AM Software Development: RE: HelloWorldDSP.out syntax error
- I would prefer not to rebuild DSPLink. Is there somewhere I can find the HelloWorldDSP executable?
-Marc
06/30/2011
- TC 05:34 PM Software Development: RE: Industrial board USB mini-B connector problem
- Hi Zoltan -
You are correct. Thank you for pointing this out!
This fix will go into the next build of boards. I apologize for any inconvenience.
Thanks,
Tom - Hi,
Sorry I post my problem here, but there is no forum for the industrial board.
We had issues with some USB devices using the mini-B USB connector, and it seems the pin-out is wrong, and the ID (pin4) and GND (pin5) is swapped.
... - GG 02:32 PM Software Development: RE: HelloWorldARM DSPLINK example causes Assertion failed
- Hi Mads,
I'm not seeing this same behavior on my system. Can you give me more details? It seems you're running with the latest MDK, but did you change anything else on your board? Namely, what dsplinkk.ko module are you loading (the o... - MC 07:21 AM Software Development: RE: HelloWorldARM DSPLINK example causes Assertion failed
- Should probably note that we are using the OMAPL138 module.
- Hi
When the HelloWorldARM (DSPLINK) example applications runs lpDspApp->StopApp() I get the following error:
Assertion failed (ipsEventList [i].eventHandlerCount == 0). File : /home/mitydsp/MDK_2011-03-31/sw/3rdparty/dsplink_linux_... - GG 02:16 PM Software Development: RE: HelloWorldDSP.out syntax error
- Hi Marc,
With the latest MDK you should not actually need to rebuild DSPLink (I'm updating the DSP Hello World wiki to reflect this now).
The kernel object for dspplink is located at MDK_2011-03-31/images/modules/dsplinkk.ko and t... - ML 01:39 PM Software Development: RE: HelloWorldDSP.out syntax error
- Oh ok, that clears up my confusion on how the DSP actually gets loaded with the executable. I dident realize HelloWorldDSP was an ARM executable, because I was stuck in the linux section of the guide where it asks you to
•Build DSPL... - MW 01:18 PM Software Development: RE: HelloWorldDSP.out syntax error
- Hi Marc,
The HelloWorldDSP.out is a DSP executable. It must be loaded by an ARM executable that uses the DSPLINK interface. The wiki instructions call for: - Hi,
I'm to the very last step of the DSP Hello World guide, but when I run ./HelloWorldDSP.out on the board, it gives me the error
./HelloWorldDSP.out: line 2: syntax error: "|" unexpected
I followed the guide for setting up CCS... - ZC 12:37 PM Software Development: RE: mtdblock kernel crash
- Mike,
I'm good with my version, and I'm not in a hurry to upgrade my kernel.
Btw I'm using mitydspl138 with the industrial base board (revD) (if it matters)
Thanks again for your help!
Zoltan - MW 12:28 PM Software Development: RE: mtdblock kernel crash
- Hi Zoltan,
We've confirmed the SPI issue and are working on it. There were a couple of patches to the (linus) mainline regarding the SPI drivers that may be impacting your use case (there was a problem with 65535 or more byte accesse... - ZC 12:18 PM Software Development: RE: mtdblock kernel crash
- Mike,
Here is some extra information:
1. SPI flash engine got broken on 4/23. 4/23 0:00 revision was ok, 4/24 0:00 kernel crash. (probably with the new spi engine)
2. The NAND mtdblock got broken on 3/21 (with the 8/16 bit chang... - ZC 10:02 AM Software Development: RE: mtdblock kernel crash
- I have the mtdblock0 write problem (read is ok), and I have the SPI crash when writing mtdblocks on the SPI flash (read is ok)
I put it in one post because both are mtdblock related
I have no code running in the DSP, or any module ...
06/29/2011
- MW 08:34 PM Software Development: RE: mtdblock kernel crash
- Oh, one other question....
Do you have anything running on the DSP while this is going on? Or is it still in IDLE / RESET?
- MW 08:32 PM Software Development: RE: mtdblock kernel crash
- 1. OK.
2. Fair enough, didn't catch that originally.
3. Sure, I'll get you something tomorrow.
Couple more questions, if you don't mind....
Do you happen to know what git revision you were using when life was good? Do you ha... - ZC 07:20 PM Software Development: RE: mtdblock kernel crash
- Thanks for the quick response!
1. Toolchain:
gcc version 4.5.1 (Sourcery G++ Lite 2010.09-50)
2. Root FS is in ram (NOT mtdblock0):
Kernel command line: mem=48M console=ttyS1,115200n8 root=/dev/ram0 rw initrd=0xc1180000,16M
3.... - MW 06:37 PM Software Development: RE: mtdblock kernel crash
- Can you try the same command without mounting /dev/mtdblock0 as the rootfs? (e.g., stay in your ram initrd filesystem)
It's a little weird that you're trolling around /dev/mtdblock0 NAND if you have it mounted as your root filesystem.... - ZC 06:34 PM Software Development: RE: mtdblock kernel crash
- Mike,
It was a clean copy. I've made changes only to make it buildable from Windows (Cygwin). But those changes were made for my previous kernel revision.
Btw "hexdump -C -n 64 /dev/mtdblock1" works fine.
Zoltan - MW 06:19 PM Software Development: RE: mtdblock kernel crash
- Hi Zoltan,
We'll need to try to reproduce this here. It may take a day to get to it.
When you rebuilt, did you do a make clean first? Or did you pull a clean copy of the kernel down?
-Mike
- ZC 05:35 PM Software Development: RE: mtdblock kernel crash
- This is what I did to crash the kernel:
2. echo Test > /dev/mtdblock9
- Hi,
I've got the latest linux kernel image, defconfig'd it, enabled SPI flashes, and nuilt the kernel.
1. If I access mtdblock0 (e.g. "hexdump -C -n 64 /dev/mtdblock0", gives me the following errors:
end_request: I/O error, dev ...
06/28/2011
- GG 05:00 PM Software Development: RE: Where can I get the files listed on the DSPLink Hello World wiki?
- Hi Marc,
I just sent you the additional files you need. Let us know if you run into any further issues.
Thanks,
\Greg - ML 10:48 AM Software Development: RE: Where can I get the files listed on the DSPLink Hello World wiki?
- Hi,
I am also having trouble finding the prerequisite files for the PC side (dsp_main.cpp, dspcore.lib, ect). I downloaded the latest tarball release but couldent find any of them in it.
-Marc