Re: Installation problems ...........

[RyanYee/叶晔]

just be more patient,cause copy files need many times,more than 10 minutes
^-^
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Are cmem.ko and dsplink.ko same in any applications?

[RyanYee/叶晔]

I just find in demos example,when you make install,just copy these two
ko from some directory to dest.I think these two modulor just be as
driver (/dev/cmem & /dev/dsplink)
and no need to compile from source code,just copy to exec
directory.maybe in different applications,modify some parameters in
loadmodules.sh.
Am I right or wrong

-- 
RyanYee
How many roads must a man walk down before
you can call him a Man?How many years can
 some people exist before They're allowed to
be free?the answer is Blowing in the wind...
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Re: DC5 output level?

[Matthias Welwarsky]

Most of the DaVinci I/O are 1.8V, the LCD interface is no exception (?).
You need to chose a display that can operate with these levels or add
level shifters.

regards,
matthias

Cochrane, Euan wrote:
> Well, surprise surprise it didn't work! everything looks fine on the scope 
> but it seems that the signal level is too low to be picked up properly by our 
> frame grabber. Hopefully this will be the last time I need to ask for help. 
> Is there any way to increase the output level of the signals on DC5? 
> currently they have an amplitude of only ~1.7v. I looked through the 
> registers for the VPBE and the closest I could find to what I'm looking for 
> was YCOLVL (Yout and Cout Level), originally it was set to 0x00 so I tried 
> setting it to 0xFF (it's maximum value for both Yout and Cout) but there was 
> no change in the output. does anyone know if/how I can increase the output 
> level of DC5? I am outputting 24bit RGB along with the pixel clock, hsync, 
> vsync and lcd_oe all of which have an output level of ~1.7v.
> Thanks,
> Euan
> ___
> Davinci-linux-open-source mailing list
> Davinci-linux-open-source@linux.davincidsp.com
> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
>   

-- 
* Matthias Welwarsky
Project Manager Software
Germany

*



This  email  and any  files  transmitted  with it are  confidential  and are
intended solely  for the use of the individual  or entity to which  they are
addressed.  Access to this e-mail by anyone else is unauthorised. If you are
not the  intended recipient,  any disclosure,  copying,  distribution or any
action taken or omitted to be taken in reliance on it, is prohibited. E-mail
messages are not necessarily secure.  Archos does not accept  responsibility
for any changes made to this message after it was sent.

___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

DC5 output level?

[Cochrane, Euan]

Well, surprise surprise it didn't work! everything looks fine on the scope but 
it seems that the signal level is too low to be picked up properly by our frame 
grabber. Hopefully this will be the last time I need to ask for help. Is there 
any way to increase the output level of the signals on DC5? currently they have 
an amplitude of only ~1.7v. I looked through the registers for the VPBE and the 
closest I could find to what I'm looking for was YCOLVL (Yout and Cout Level), 
originally it was set to 0x00 so I tried setting it to 0xFF (it's maximum value 
for both Yout and Cout) but there was no change in the output. does anyone know 
if/how I can increase the output level of DC5? I am outputting 24bit RGB along 
with the pixel clock, hsync, vsync and lcd_oe all of which have an output level 
of ~1.7v.
Thanks,
Euan
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Re: Buildroot on 6446EVM

[Philip Balister]

I've used OpenEmbedded to build images for the EVM before. I built glibc 
images, but it should be possible to create uclibc images also. 
Unfortunately, I do not have an EVM to test against so I do not keep a 
set of current images available for download.


Philip

Brian Niebuhr wrote:
Has anyone got buildroot to work on the 6446EVM?  


I am currently running the 2.6.23-davinci1 git kernel with a
Montavista-generated cramfs root filesystem and that is working fine.
However, adding just a couple of packages to create a minimal filesystem
makes the filesystem huge.  So I wanted to try buildroot to generate a
uClibc-based toolchain and filesystem.  I was able to get buildroot to
create a cramfs root filesystem and I used it to replace my Montavista
filesystem. However when the kernel gets to the point where it should
run init, it just apparently hangs (no output whatsoever).  I've tried
various init= kernel parameters, including just init=/bin/sh, and I
always get the same results.  It's as if busybox can't start running.

I assume that I just messed something up in the buildroot configuration,
but I'm not sure what.  If anyone has this working, could I get a copy
of your buildroot .config and/or any tips on how to make it work?

Thanks!

Brian


_
Brian Niebuhr
Senior Design Engineer
E.F. Johnson

___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source



smime.p7s
Description: S/MIME Cryptographic Signature
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

RE: DC5 output level?

[Cochrane, Euan]

This is the code for my 24bit RGB SVGA driver, as I haven't yet been able to 
see it yet I can't guarantee that it works but everything looks ok on the scope 
(~40MHz clock, ~37.8kHz Hsync, ~60Hz Vsync). Hope it's useful for someone, let 
me know if it works :P
Euan
 
void vpbe_davincifb_svga_prgb_config(void)

{

volatile unsigned int venc, lcdout;

venc = dispc_reg_in(VENC_VMOD) & VENC_VMOD_VENC;

lcdout = dispc_reg_in(VENC_LCDOUT);

vpbe_set_display_default();

/* Clear component and composite mode registers 

(applicable to Analog DACS) */

dispc_reg_out(VENC_CVBS, 0);

dispc_reg_out(VENC_CMPNT, 0);

/* Set PINMUX0 - RGB888 Enable */

dispc_reg_merge(PINMUX0, 1 << PINMUX0_RGB888_SHIFT,

PINMUX0_RGB888);

dispc_reg_merge(PINMUX0, 1 << PINMUX0_LOEEN_SHIFT,

PINMUX0_LOEEN);

/* dispc_reg_out(PINMUX1, 0x0); */

/* Set Base Pixel X and Base Pixel Y */

dispc_reg_out(OSD_BASEPX, dm->videomode.basepx);//0xC8);

dispc_reg_out(OSD_BASEPY, dm->videomode.basepy);//0x18);

/* Set VIDCTL to select VCLKE = 1, 

VCLKZ =1, SYDIR = 0 (set o/p), DOMD = 0 */

dispc_reg_merge(VENC_VIDCTL, 1 << VENC_VIDCTL_VCLKE_SHIFT,

VENC_VIDCTL_VCLKE);

dispc_reg_merge(VENC_VIDCTL, 0 << VENC_VIDCTL_VCLKZ_SHIFT,

VENC_VIDCTL_VCLKZ);

dispc_reg_merge(VENC_VIDCTL, 0 << VENC_VIDCTL_SYDIR_SHIFT,

VENC_VIDCTL_SYDIR);

dispc_reg_merge(VENC_VIDCTL, 0 << VENC_VIDCTL_YCDIR_SHIFT,

VENC_VIDCTL_YCDIR);

dispc_reg_merge(VENC_DCLKCTL,

1 << VENC_DCLKCTL_DCKEC_SHIFT,

VENC_DCLKCTL_DCKEC);

dispc_reg_out(VENC_DCLKPTN0, 0x1);

//vpbe_set_display_timing(&dm->videomode);

//***

dispc_reg_out(VENC_HSPLS, 0x80);// 128

dispc_reg_out(VENC_HSTART, 0x3C);// 60

dispc_reg_out(VENC_HVALID, 0x320);// 800

dispc_reg_out(VENC_HINT, 0x418);// 1048

dispc_reg_out(VENC_VSPLS, 0x4);// 4

dispc_reg_out(VENC_VSTART, 0xD);// 13

dispc_reg_out(VENC_VVALID, 0x258);// 600

dispc_reg_out(VENC_VINT, 0x276);// 630

//***

dispc_reg_out(VENC_SYNCCTL,

(VENC_SYNCCTL_SYEV |

VENC_SYNCCTL_SYEH | VENC_SYNCCTL_HPL

| VENC_SYNCCTL_VPL));

/* Set OSD clock and OSD Sync Adavance registers */

dispc_reg_out(VENC_OSDCLK0, 0);

dispc_reg_out(VENC_OSDCLK1, 1);

/* set VPSS clock */

dispc_reg_out(VPSS_CLKCTL, 0x09);

/* set PLL2 DIV1 to generate ~40MHz clock */

dispc_reg_out(VPSS_PLL2M, 0x0015); //multiply by 22

dispc_reg_out(VPSS_PLL2DIV1, 0x000E);//divde by 15

dispc_reg_out(VPSS_PLL2DIV1, 0x800E);//(27*22)/15=39.6 ~=40

/* Configure VMOD. No change in VENC bit */

dispc_reg_out(VENC_VMOD, 0x2010 | venc);

dispc_reg_out(VENC_LCDOUT, lcdout);

/* Change window parameters for progressive display */

change_win_param(FB_VMODE_NONINTERLACED);

}

-Original Message-
From: Albert Burbea [mailto:[EMAIL PROTECTED]
Sent: 14 December 2007 12:59
To: Cochrane, Euan
Subject: Re: DC5 output level?


Hi Euan, 
it would be very nice of you if you could publish your final source code for 
the VGA driver here
Thanks in advance 
Albert 

 
On 12/14/07, Cochrane, Euan < [EMAIL PROTECTED]  > 
wrote: 

Well, surprise surprise it didn't work! everything looks fine on the scope but 
it seems that the signal level is too low to be picked up properly by our frame 
grabber. Hopefully this will be the last time I need to ask for help. Is there 
any way to increase the output level of the signals on DC5? currently they have 
an amplitude of only ~1.7v. I looked through the registers for the VPBE and the 
closest I could find to what I'm looking for was YCOLVL (Yout and Cout Level), 
originally it was set to 0x00 so I tried setting it to 0xFF (it's maximum value 
for both Yout and Cout) but there was no change in the output. does anyone know 
if/how I can increase the output level of DC5? I am outputting 24bit RGB along 
with the pixel clock, hsync, vsync and lcd_oe all of which have an output level 
of ~1.7v. 
Thanks,
Euan
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com  
 
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source 
 





-- 
Albert Burbea 
Harishonim 8
Ramat Gan 52502, Israel
Tel/Fax + 972-3-7526016
Mobile: +972-52-3541842 

___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

warning: creating output section EXTERNAL_CONST without SECTIONS

[Faro Maza, Virginia]

Hi all,

 

I am trying to build a codec engine server with some codecs shipped to
us by TI.

 

When I add the MPEG4ENC codec to my server and application, I get the
following warning when the application links in the server:

 

>> warning: creating output section EXTERNAL_CONST without SECTIONS

Specification

 

When I add the JPEGENC codec to my server and application, I get the
same warning but for section ISRAM:

 

>> warning: creating output section ISRAM without SECTIONS specification

 

I believe I need to specify how those sections should be mapped into
memory in the codecs' link.xdt and package.xs files (see
http://www.mail-archive.com/[EMAIL PROTECTED]
om/msg02174.html), but I do not know which area of memory these sections
should be mapped to.

 

Any help would be much appreciated.

 

Best regards,

 

Virginia Faro-Maza

American Dynamics

Email: [EMAIL PROTECTED] 
 


Tyco Safety Products/CEM Systems Ltd.
Registered in Northern Ireland: NI 25728.  Registered Office: Unit 4 Ravenhill 
Business Park, Ravenhill Road, Belfast, BT6 8AW..
 
Please note that any views or opinions presented in this email are solely those 
of the author and do not necessarily represent those of the company. This email 
and any attachments are confidential and intended solely for the use of the 
individual or entity to whom they are addressed. If you have received this 
email in error please notify the sender immediately and delete any copies in 
your possession.
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Link errors on DM6446 application

[Hoskote, Satyajeet]

Hello,

I am building an application on DM6446 consisting of multiple source
files, and I have archived all my object files into a single .a library.
During the final link step, the linker throws the following errors:

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/lib/ce_debug.a470MV
(Engine.o470MV)(.text+0xbb8): In function `Engin
e_getLocalEngine':
/db/atree/library/trees/ce-d14x/src/ti/sdo/ce/Engine.c:373: undefined
reference to `Engine_config'
/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/lib/ce_debug.a470MV
(Engine.o470MV)(.text+0x1104): In function `Engi
ne_getRemoteVisa':
/db/atree/library/trees/ce-d14x/src/ti/sdo/ce/Engine.c:534: undefined
reference to `GT'
/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/lib/ce_debug.a470MV
(Engine.o470MV)(.text+0x1564): In function `Engi
ne_open':
/db/atree/library/trees/ce-d14x/src/ti/sdo/ce/Engine.c:652: undefined
reference to `Engine_config'
/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Comm_dsplink_linux.o470MV)(.text
+0x3b0): In function `Comm_locate':
Comm_dsplink_linux.c: undefined reference to `Comm_LOCATERETRIES'
/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Power_dsplink_linux.o470MV)(.tex
t+0x3c): In function `Power_init':
Power_dsplink_linux.c: undefined reference to `LPM_init'
/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Power_dsplink_linux.o470MV)(.tex
t+0xa0): In function `Power_on':
Power_dsplink_linux.c: undefined reference to `LPM_open'
/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Power_dsplink_linux.o470MV)(.tex
t+0xc0):Power_dsplink_linux.c: undefined reference to `LPM_on'
/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Power_dsplink_linux.o470MV)(.tex
t+0x188):Power_dsplink_linux.c: undefined reference to `LPM_on'
/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Power_dsplink_linux.o470MV)(.tex
t+0x24c): In function `Power_off':
Power_dsplink_linux.c: undefined reference to `LPM_off'
/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Power_dsplink_linux.o470MV)(.tex
t+0x270):Power_dsplink_linux.c: undefined reference to `LPM_close'
/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Power_dsplink_linux.o470MV)(.tex
t+0x3d0): In function `Power_connect':
Power_dsplink_linux.c: undefined reference to `LPM_connect'
/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Power_dsplink_linux.o470MV)(.tex
t+0x4d4): In function `Power_disconnect':
Power_dsplink_linux.c: undefined reference to `LPM_disconnect'
/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/trace/lib/gt.a470MV
(gt.o470MV)(.text+0x34): In function `error':
gt.c: undefined reference to `GT'
/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/trace/lib/gt.a470MV
(gt.o470MV)(.text+0x100): In function `addModNam
e':
gt.c: undefined reference to `GT'
/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/trace/lib/gt.a470MV
(gt.o470MV)(.text+0x29c): In function `GT_curTim
e':
gt.c: undefined reference to `GT'
/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/trace/lib/gt.a470MV
(gt.o470MV)(.text+0x2e4): In function `GT_disabl
e':
gt.c: undefined reference to `GT'
/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/trace/lib/gt.a470MV
(gt.o470MV)(.text+0x3a0): In function `GT_init':

gt.c: undefined reference to `GT'
/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/trace/lib/gt.a470MV
(gt.o470MV)(.text+0xa68):gt.c: more undefined re
ferences to `GT' follow
collect2: ld returned 1 exit status
make: *** [all] Error 1

My link command is

gcc -o app.out -L$(MYLIBRARYPATH) -lmylibrary `cat $(XDC_OFILE)`
-lpthread

Where my $(XDC_OFILE) contains the following:

 
/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/image/lib/image_deb
ug.a470MV
 
/home/shoskote/OVReadyWin/contrib/DaVinci/analytics/ovanalytics/lib/ovan
alytics.a470MV
 
/home/shoskote/OVReadyWin/contrib/DaVinci/extensions/vidanalytics/lib/vi
danalytics_debug.a470MV
 
/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/lib/ce_debug.a470MV
 
/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/node/lib/node_debug
.a470MV
 
/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV
 
/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/alg/lib/alg.a4
70MV
 
/opt/dvevm_1_10/dsplink_1_30_08_02/packages/dsplink/gpp/export/BIN/Linux
/Davinci/DEBUG/dsplink.lib
 
/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/trace/lib/gt.a470MV
 
/opt/dvevm_1_10/cmem_1_01/packages/ti/sdo/linuxutils/cmem/lib/cmemd.a

Any ideas on how I can get rid of these errors ? It seems to me like all
the required libraries are present in the linker path, so could this
just be an ordering issue ?

Thanks
Satyajeet.
This electronic message tra

Re: Buildroot on 6446EVM

[Dirk Behme]

Brian Niebuhr wrote:

Buildroot is good at building all together, but not good at cleaning.
Since your console is working and even init=/bin/sh is not working I
suspected EABI/OABI stuff. Moreover, I read some warnings 
some time ago

on the buildroot mailing list about this issue.



Caglar - 


You were correct.  After getting a brand new copy of buildroot and
configuring it for OABI, /sbin/getty now runs.  Unfortunately it hasn't
gotten me much further because a shell still won't run.  Once I log in,
a shell never starts and getty just respawns.  Using init=/bin/sh or
init=/bin/ash just hangs like it did before with no output.  I compiled
a hello world program with the uclibc toolchain, and using that for init
works just fine.  So there's something about the busybox shell that
isn't working right.


One independent thing to try:

Check make menuconfig of your kernel if any floating point emulation 
is enabled:


Floating point emulation  ---> [*] NWFPE math emulation

Regards

Dirk


___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Re: Has anyone used Windows CE on Davinci (specifically the DM355)

[Diego Dompe]

Howy,

As far I know TI codecs for DM355 (JPEG and MPEG4) are available only  
on Linux at this point, and albeit they can be ported to WinCE I think  
you will have to deal with it by yourself.


Diego

On Dec 14, 2007, at 12:23 PM, Howy Stark wrote:

I am researching weather to use Linux or WinCE as the OS for a DM355  
based product.
After 10 years I finally got comfortable with Code Composer Studio  
and DSP BIOS.  After receiving my DM355 board yesterday I found I  
need to use Linux based SDK tools to develop on TI's ARM processors.
Having to learn everything Linux from scratch is a daunting task for  
someone my age, but it seems I would be in the minority if I chose  
the WinCE route.
Does anyone have any happy/horror stories regarding Win CE and  
Davinci?

-howy


___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source


___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

RE: Link errors on DM6446 application

[Tivy, Robert]

Satyajeet,
 
Shouldn't you have "-l" in front of every line in your $XDC_OFILE?
 
Regards,
 
- Rob




From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Hoskote, Satyajeet
Sent: Friday, December 14, 2007 6:45 AM
To: davinci-linux-open-source@linux.davincidsp.com
Subject: Link errors on DM6446 application



Hello, 

I am building an application on DM6446 consisting of multiple
source files, and I have archived all my object files into a single .a
library. During the final link step, the linker throws the following
errors:


/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/lib/ce_debug.a470MV
(Engine.o470MV)(.text+0xbb8): In function `Engin

e_getLocalEngine': 
/db/atree/library/trees/ce-d14x/src/ti/sdo/ce/Engine.c:373:
undefined reference to `Engine_config' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/lib/ce_debug.a470MV
(Engine.o470MV)(.text+0x1104): In function `Engi

ne_getRemoteVisa': 
/db/atree/library/trees/ce-d14x/src/ti/sdo/ce/Engine.c:534:
undefined reference to `GT' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/lib/ce_debug.a470MV
(Engine.o470MV)(.text+0x1564): In function `Engi

ne_open': 
/db/atree/library/trees/ce-d14x/src/ti/sdo/ce/Engine.c:652:
undefined reference to `Engine_config' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Comm_dsplink_linux.o470MV)(.text

+0x3b0): In function `Comm_locate': 
Comm_dsplink_linux.c: undefined reference to
`Comm_LOCATERETRIES' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Power_dsplink_linux.o470MV)(.tex

t+0x3c): In function `Power_init': 
Power_dsplink_linux.c: undefined reference to `LPM_init' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Power_dsplink_linux.o470MV)(.tex

t+0xa0): In function `Power_on': 
Power_dsplink_linux.c: undefined reference to `LPM_open' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Power_dsplink_linux.o470MV)(.tex

t+0xc0):Power_dsplink_linux.c: undefined reference to `LPM_on' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Power_dsplink_linux.o470MV)(.tex

t+0x188):Power_dsplink_linux.c: undefined reference to `LPM_on' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Power_dsplink_linux.o470MV)(.tex

t+0x24c): In function `Power_off': 
Power_dsplink_linux.c: undefined reference to `LPM_off' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Power_dsplink_linux.o470MV)(.tex

t+0x270):Power_dsplink_linux.c: undefined reference to
`LPM_close' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Power_dsplink_linux.o470MV)(.tex

t+0x3d0): In function `Power_connect': 
Power_dsplink_linux.c: undefined reference to `LPM_connect' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Power_dsplink_linux.o470MV)(.tex

t+0x4d4): In function `Power_disconnect': 
Power_dsplink_linux.c: undefined reference to `LPM_disconnect' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/trace/lib/gt.a470MV
(gt.o470MV)(.text+0x34): In function `error': 
gt.c: undefined reference to `GT' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/trace/lib/gt.a470MV
(gt.o470MV)(.text+0x100): In function `addModNam

e': 
gt.c: undefined reference to `GT' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/trace/lib/gt.a470MV
(gt.o470MV)(.text+0x29c): In function `GT_curTim

e': 
gt.c: undefined reference to `GT' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/trace/lib/gt.a470MV
(gt.o470MV)(.text+0x2e4): In function `GT_disabl

e': 
gt.c: undefined reference to `GT' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/trace/lib/gt.a470MV
(gt.o470MV)(.text+0x3a0): In function `GT_init':

gt.c: undefined reference to `GT' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/trace/lib/gt.a470MV
(gt.o470MV)(.text+0xa68):gt.c: more undefined re

ferences to `GT' follow 
collect2: ld returned 1 exit status 
make: *** [all] Error 1 

My link command is 

gcc -o app.out -L$(MYLIBRARYPATH) -lmylibrary `cat $(XDC_OFILE)`
-lpthread 

Where my $(XDC_OFILE) contains the following: 


/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/image/lib/image_deb
ug.a470MV 

/home/shoskote/OVReadyWin/contrib/DaVinci/analytics/ov

Video lockup

[Will Tucker]

Hi,
 
We have noticed when connected to a 480p display that the dsp will lock up if a 
Ethernet chip is not present.  By lockup we mean that when playing a video the 
process will hang in the VIDDEC_process() call, the arm still runs but the DSP 
won't respond. It will also occur if we disable the EMAC clock and disable EMAC 
in PINMUX0. We have disabled the Ethernet in menuconfig and modified the rcx.d 
but this doesn't seem to solve the issue. 
 
Any Ideas?
 
Will


  

Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Has anyone used Windows CE on Davinci (specifically the DM355)

[Howy Stark]

I am researching weather to use Linux or WinCE as the OS for a DM355 
based product.
After 10 years I finally got comfortable with Code Composer Studio and 
DSP BIOS.  After receiving my DM355 board yesterday I found I need to 
use Linux based SDK tools to develop on TI's ARM processors.
Having to learn everything Linux from scratch is a daunting task for 
someone my age, but it seems I would be in the minority if I chose the 
WinCE route.

Does anyone have any happy/horror stories regarding Win CE and Davinci?
-howy


___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

RE: Buildroot on 6446EVM

[Brian Niebuhr]

> One independent thing to try:
> 
> Check make menuconfig of your kernel if any floating point emulation 
> is enabled:
> 
> Floating point emulation  ---> [*] NWFPE math emulation

Dirk - 

Thanks for this suggestion - I would never have figured that one out.  I
had a different floating point emulation implementation selected, and
when I switched to NWFPE things started working.  Can I ask why you
suspected floating point emulation? 

Brian

___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

FW: SPI on Davinci

[Joshua Hintze]

Hey guys,

 

Have any of you interfaced to the SPI port on the Davinci 6446. I got the
i2c working pretty easy using the i2c-dev character driver but there is no
such thing as spidev until linux kernel 2.6.22.

 

 

So I'm wondering how others are doing it. Are you writing your own kernel
drivers or is there still a way to do it from user space?

 

Thanks in advance,

 

Josh

 

___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Re: Buildroot on 6446EVM

[Dirk Behme]

Brian Niebuhr wrote:

One independent thing to try:

Check make menuconfig of your kernel if any floating point emulation 
is enabled:


Floating point emulation  ---> [*] NWFPE math emulation



Dirk - 


Thanks for this suggestion - I would never have figured that one out.  I
had a different floating point emulation implementation selected, and
when I switched to NWFPE things started working.


:)


Can I ask why you
suspected floating point emulation? 


Had a similiar issue some weeks ago ;) The switch from kernel (no 
floating point at all) to user space (heavily using floating point, 
depending on toolchain & library) is always a tricky thing cause you 
get *no* debugging output. Things simply do not work :( I think to 
remember that default kernel config of git kernel has no floating 
point emulation enabled at all.


That an other FPE don't work is new to me, never tried others ;) Maybe 
you like to ask on arm-linux list regarding this. Would be an 
interesting question.


Regards

Dirk

___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

RE: Link errors on DM6446 application

[Hoskote, Satyajeet]

Thanks for your response Robert. I figured out what was wrong - I did
not have the $(XDC_OFILE) as an input to the linker.
 
Thanks
Satyajeet.



From: Tivy, Robert [mailto:[EMAIL PROTECTED] 
Sent: Friday, December 14, 2007 12:53 PM
To: Hoskote, Satyajeet; davinci-linux-open-source@linux.davincidsp.com
Subject: RE: Link errors on DM6446 application


Satyajeet,
 
Shouldn't you have "-l" in front of every line in your $XDC_OFILE?
 
Regards,
 
- Rob




From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Hoskote, Satyajeet
Sent: Friday, December 14, 2007 6:45 AM
To: davinci-linux-open-source@linux.davincidsp.com
Subject: Link errors on DM6446 application



Hello, 

I am building an application on DM6446 consisting of multiple
source files, and I have archived all my object files into a single .a
library. During the final link step, the linker throws the following
errors:


/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/lib/ce_debug.a470MV
(Engine.o470MV)(.text+0xbb8): In function `Engin

e_getLocalEngine': 
/db/atree/library/trees/ce-d14x/src/ti/sdo/ce/Engine.c:373:
undefined reference to `Engine_config' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/lib/ce_debug.a470MV
(Engine.o470MV)(.text+0x1104): In function `Engi

ne_getRemoteVisa': 
/db/atree/library/trees/ce-d14x/src/ti/sdo/ce/Engine.c:534:
undefined reference to `GT' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/lib/ce_debug.a470MV
(Engine.o470MV)(.text+0x1564): In function `Engi

ne_open': 
/db/atree/library/trees/ce-d14x/src/ti/sdo/ce/Engine.c:652:
undefined reference to `Engine_config' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Comm_dsplink_linux.o470MV)(.text

+0x3b0): In function `Comm_locate': 
Comm_dsplink_linux.c: undefined reference to
`Comm_LOCATERETRIES' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Power_dsplink_linux.o470MV)(.tex

t+0x3c): In function `Power_init': 
Power_dsplink_linux.c: undefined reference to `LPM_init' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Power_dsplink_linux.o470MV)(.tex

t+0xa0): In function `Power_on': 
Power_dsplink_linux.c: undefined reference to `LPM_open' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Power_dsplink_linux.o470MV)(.tex

t+0xc0):Power_dsplink_linux.c: undefined reference to `LPM_on' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Power_dsplink_linux.o470MV)(.tex

t+0x188):Power_dsplink_linux.c: undefined reference to `LPM_on' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Power_dsplink_linux.o470MV)(.tex

t+0x24c): In function `Power_off': 
Power_dsplink_linux.c: undefined reference to `LPM_off' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Power_dsplink_linux.o470MV)(.tex

t+0x270):Power_dsplink_linux.c: undefined reference to
`LPM_close' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Power_dsplink_linux.o470MV)(.tex

t+0x3d0): In function `Power_connect': 
Power_dsplink_linux.c: undefined reference to `LPM_connect' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/osal/lib/osal_dspli
nk_linux.a470MV(Power_dsplink_linux.o470MV)(.tex

t+0x4d4): In function `Power_disconnect': 
Power_dsplink_linux.c: undefined reference to `LPM_disconnect' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/trace/lib/gt.a470MV
(gt.o470MV)(.text+0x34): In function `error': 
gt.c: undefined reference to `GT' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/trace/lib/gt.a470MV
(gt.o470MV)(.text+0x100): In function `addModNam

e': 
gt.c: undefined reference to `GT' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/trace/lib/gt.a470MV
(gt.o470MV)(.text+0x29c): In function `GT_curTim

e': 
gt.c: undefined reference to `GT' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/trace/lib/gt.a470MV
(gt.o470MV)(.text+0x2e4): In function `GT_disabl

e': 
gt.c: undefined reference to `GT' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/trace/lib/gt.a470MV
(gt.o470MV)(.text+0x3a0): In function `GT_init':

gt.c: undefined reference to `GT' 

/opt/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/trace/lib/gt.a470MV
(gt.o470MV)(.text+0xa68):gt.c: more undefined re

ferences to `GT' follow 
collect2: ld