Hi :

I  test the TMX320DM365 for  h264 encode/decode demo by TI TMX320DM365 DVEVM 
kit.

Running the Demos from the Command Line:
Target $ cd /opt/dvsdk/dm365
Target $ ./loadmodules_hd.sh

A issue occur as follows:

Target $ cmemk: no version for "struct_module" found: kernel tainted.
CMEMK Error: CMEM phys_start (0x85000000) overlaps kernel (0x81000000 -> 
0x85c00000)
insmod: error inserting 'cmemk.ko': -1 Invalid parameters

Can anybody please let me know, what I am missing here with DVEVM kit? How to 
solve this issue.
Thanks!

-------------------------------------------------------------------------
"If A is success in life, then A equals x plus y plus z. Work is x; y is play; 
and z is keeping your mouth shut." 
Albert Einstein (1879 - 1955)
----- Original Message ----- 
From: <davinci-linux-open-source-requ...@linux.davincidsp.com>
To: <davinci-linux-open-source@linux.davincidsp.com>
Sent: Tuesday, April 28, 2009 10:39 AM
Subject: Davinci-linux-open-source Digest, Vol 40, Issue 180


> Send Davinci-linux-open-source mailing list submissions to
> davinci-linux-open-source@linux.davincidsp.com
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
> 
> or, via email, send a message with subject or body 'help' to
> davinci-linux-open-source-requ...@linux.davincidsp.com
> 
> You can reach the person managing the list at
> davinci-linux-open-source-ow...@linux.davincidsp.com
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Davinci-linux-open-source digest..."
> 
> 
> Today's Topics:
> 
>   1. Re: [PATCH 3/3 v4] ARM: da830 - Add support for
>      DA830/OMAP-L137 EVM (Mark A. Greer)
>   2. RE: Problem about DSP server config of DM6446 (Tivy, Robert)
>   3. Re: when port a software , bus error (zhenfeng ren)
>   4. Re: THS8200 Module and DM6446EVM Initial Setup (Carl Renaud)
>   5. Re: is there any LCD Kits for DM355 DVEVM board (Carl Renaud)
>   6. RE: Changing Machine ID (Manjunatha AM)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Mon, 27 Apr 2009 14:28:42 -0700
> From: "Mark A. Greer" <mgr...@mvista.com>
> Subject: Re: [PATCH 3/3 v4] ARM: da830 - Add support for
> DA830/OMAP-L137 EVM
> To: David Brownell <davi...@pacbell.net>
> Cc: davinci-linux-open-source@linux.davincidsp.com
> Message-ID: <20090427212842.ga19...@mag.az.mvista.com>
> Content-Type: text/plain; charset=iso-8859-1
> 
> On Mon, Apr 27, 2009 at 12:49:54PM -0700, David Brownell wrote:
>> On Monday 27 April 2009, Mark A. Greer wrote:
>> > > --- a/arch/arm/mach-davinci/include/mach/debug-macro.S
>> > > +++ b/arch/arm/mach-davinci/include/mach/debug-macro.S
>> > > @@ -24,7 +24,14 @@
>> > > tst \rx, #1 @ MMU enabled?
>> > > moveq \rx, #0x01000000 @ physical base address
>> > > movne \rx, #0xfe000000 @ virtual base
>> > > +#if defined(CONFIG_ARCH_DAVINCI_DA830_EVM) && 
>> > > defined(CONFIG_ARCH_DAVINCI_DMx)
>> > ^^^^
>> > 
>> > This should be 'CONFIG_MACH_DAVINCI_DA830_EVM'.
>> 
>> You man it wouldn't be applicable to DA830 boards other
>> than that EVM??
> 
> Maybe, maybe not.
> 
>> Same comment in a few other places.  From what you've said,
>> these are chip-specific issues, not board-specific ones...
> 
> Well, there are lots of pinmux conflicts on the da830.  For devices
> that aren't used all of the time, it makes sense to allow the driver
> and the resources it requires to come and go on demand--maybe even the
> console if there is a graphic console.
> 
> Either way, what uart is used for the serial console is determined by
> the board not the chip.
> 
> Mark
> --
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Mon, 27 Apr 2009 17:36:25 -0500
> From: "Tivy, Robert" <rt...@ti.com>
> Subject: RE: Problem about DSP server config of DM6446
> To: "chensu.main" <chensu.m...@263.net>, davinci-linux-open-source
> <davinci-linux-open-source@linux.davincidsp.com>
> Message-ID:
> <6b8224e84039b140aa662f0bb0361643324d6...@dlee04.ent.ti.com>
> Content-Type: text/plain; charset="us-ascii"
> 
> I'm not sure about a document, but the number of algorithm objects that you 
> can create depends on the size of the memory block from which the stacks are 
> allocated.  As you've seen, cutting the stack size down allows you to create 
> more.  You might be able to find a formula, but the real answer is "as many 
> as you have memory for".
> 
> - Rob
> 
> ________________________________
> From: davinci-linux-open-source-boun...@linux.davincidsp.com 
> [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of 
> chensu.main
> Sent: Monday, April 27, 2009 8:03 AM
> To: davinci-linux-open-source
> Subject: Problem about DSP server config of DM6446
> 
> Hi all ,
> 
> In my application , I have to create one algorithm many times .
> 
> Fistly I config DSP server's CFG file and set stack size to 16384 in 
> Server.algs {} , but app can only create 7 instances of my algorithm . Then I 
> fix stack to  4096 and I can create more .
> 
> My question is How many algorithm objects can I create . Which document 
> describe it indetail ?
> 
> 
> 2009-04-27
> ________________________________
> chensu.main
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/20090427/a4475722/attachment-0001.htm
> 
> ------------------------------
> 
> Message: 3
> Date: Tue, 28 Apr 2009 08:43:45 +0800
> From: zhenfeng ren <1985re...@gmail.com>
> Subject: Re: when port a software , bus error
> To: "Balagopalakrishnan, Anand" <ana...@ti.com>
> Cc: "davinci-linux-open-source@linux.davincidsp.com"
> <davinci-linux-open-source@linux.davincidsp.com>, "Heroor, Siddharth"
> <her...@ti.com>
> Message-ID:
> <cdf4ec730904271743j36fc2c0em7627ba02ce321...@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> hi,
>   Thanks for your answers.
>   Now, I have changed the member variable in struct to make sure that
> the alignment is correct.
> 
> 
> -- 
> Thanks,
> Zhenfeng Ren
> 
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Mon, 27 Apr 2009 22:03:29 -0400
> From: Carl Renaud <carl.ren...@gmail.com>
> Subject: Re: THS8200 Module and DM6446EVM Initial Setup
> To: Jerry Johns <jerry.jo...@nuvation.com>
> Cc: davinci-linux-open-source@linux.davincidsp.com
> Message-ID:
> <5f9ee3fc0904271903s3371c93ex3be0bba4dc1a5...@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-2022-JP
> 
> Hmmm...  Just to let you know that the EVMDM6446 and the THS8200
> daughter card CAN work together to output VESA compliant signals (in
> VESA slave mode).  I modified the THS8200 drivers (CDC949 pixel clock,
> VPBE and THS8200 registers) to support RGB output of 1024x768 at 60
> fps, with refresh rate of 65 Mhz and it worked fine.  I can hook up
> the daugther card to any LCD monitor...
> 
> I had answered another reader a few months ago who wanted to interface
> the THS8200 from a DM355.  I had forgotten to post the reply to the
> group.  Anyway, here goes, I hope this helps:
> 
> From: Carl Renaud
> Sent: 2008-12-16  22:12:02
> To: zuowenping
> Cc:
> Subject: Re: How can i use VGA(480p) format output to ths8200 in dm355 
> platform
> 
> I just went through the process of supporting 1024x768 VGA on the
> THS8200 evm (with a dm6446, but should be the same on dm355).
> 1) You will need to modify the files:
>    ths8200_encoder.h
>    ths8200_encoder.c  (for THS8200, CDCE949 and THS7303 reprogramming)
>    davinci_platform.c  (for VPBE VENC reprogramming)
>    vid_encoder_types.h
>    These files are located under:
>        workdir/lsp/ti-davinci/include/media/davinci
>        workdir/lsp/ti-davinci/drivers/media/video/davinci
> 2) Search for COMPONENT1 and VID_ENC_STD_720P_60.  Anywhere these are
> used, you will need to add something for 640x480 support.
> 3) You will need to set timings for front and back porch, sync length
> and data valid (I did not knew about these 2 weeks ago).  To get the
> right timings, check the site
> www.tkk.fi/Misc/Electronics/faq/vga2rgb/calc.html.  Note that the
> timings depend on the pixel rate clock (and thus the refresh rate).
> For example, 640x480 at 60 Hz requires a pixel clock of 25.17 MHz,
> horizontal: front porch 16 pixels, sync 96 pixels, back 48
> pixels...etc.  These values will need to be programmed in the VPBE
> VENC AND the THS8200.
> 4) First you need to program the pixel clock(vpbe_clk) which will be
> fed to the DM355 VBPE VENC.  For example, in 640x480 at 60 Hz you need
> 25.17 MHz.  This is done by the CDCE949 (on the THS8200 daughter
> card).  You need to read document SCAS844A.pdf (on TI site).  You will
> also need the TI clock pro application (on the CDCE949 part web page)
> to get the register settings.  Note that the clock pro application is
> not reliable.  I needed a 65MHz clock and the register config it gave
> me generated a jittery 65MHz clock.  I did the N and M computation by
> hand and then let the TI clock pro software populate the registers.
> You will need to experiment...
> 5) I do not know about the DM355 evm, but on the DM6446, we needed to
> add a wire on the DM6446 evm to route the vpbe_clk (check the
> schematics).
> 6) You will need to read and understand all registers of the:
>        VPBE VENC.
>        THS8200
>    Get the documents and a lot of coffee ;-)
> 7) I did not make any changes to the THS7303 configuration
> 8) VERY IMPORTANT:
>    You will want to configure the THS8200 using:
>          VESA slave
>          input 16 bits RGB 4:4:4
>    You will need to configure the VPBE VENC using:
>          output Parallel RGB 888
>    However note that not all Parallel RGB 888 lines are routed to the
> THS8200 daughter card.  It ends up being RGB565, and thus,  the color
> resolution is reduced (But it is more than OK for testing.  I've been
> playing videos and it is more than fair).
> 9)  Expect a few days of reading/testing to get it to work.  I suggest
> you write a user level application to play with the
> registers/configuration.  Once you get it right, port these settings
> to the driver...
> 
> Good luck
> 
> 
> 
> ------------------------------
> 
> Message: 5
> Date: Mon, 27 Apr 2009 22:07:10 -0400
> From: Carl Renaud <carl.ren...@gmail.com>
> Subject: Re: is there any LCD Kits for DM355 DVEVM board
> To: weixinl...@yahoo.com
> Cc: davinci-linux-open-source@linux.davincidsp.com
> Message-ID:
> <5f9ee3fc0904271907pabdb986xeb4f6e85f6687...@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> You can use the THS8200 daughter card (sold by Spectrum), but will
> need to modify the drivers to support RGB output to an LCD monitor
> (not a trivial task).
> 
> On Fri, Apr 24, 2009 at 10:02 PM, weixin Li <weixinl...@yahoo.com> wrote:
>> Hello
>>
>> I have a DM355 EVM board and want to connect an LCD. Is there any available
>> LCD module can be used? Is there daughter board available with the mating
>> connector to connect directly to the EVM board?
>>
>> Thanks,
>> Wayne
>> _______________________________________________
>> Davinci-linux-open-source mailing list
>> Davinci-linux-open-source@linux.davincidsp.com
>> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
>>
>>
> 
> 
> 
> ------------------------------
> 
> Message: 6
> Date: Tue, 28 Apr 2009 08:09:18 +0530
> From: "Manjunatha AM" <manjunat...@tataelxsi.co.in>
> Subject: RE: Changing Machine ID
> To: "'David Brownell'" <davi...@pacbell.net>,
> <davinci-linux-open-source@linux.davincidsp.com>
> Message-ID: <001201c9c7aa$88020010$37043...@telxsi.com>
> Content-Type: text/plain; charset="us-ascii"
> 
> Hi David,
> 
> Thanks for your reply, I have changed "/arch/arm/tools/mach-types" as per
> suggestion and kernel started booting...I have some problem in mounting
> filesystem..
> 
> Thanks
> 
> Manjuntah.AM
> 
> -----Original Message-----
> From: David Brownell [mailto:davi...@pacbell.net]
> Sent: Monday, April 27, 2009 11:41 AM
> To: davinci-linux-open-source@linux.davincidsp.com;
> manjunat...@tataelxsi.co.in
> Subject: Re: Changing Machine ID
> 
> 
> On Sunday 26 April 2009, Manjunatha AM wrote:
>>
>> Hi
>>
>> I downloaded latest OS (linux-davinci-2.6-historic )from source.mvsta.com
>> and compiled it for Davinci DM6446 EVM with low level debug option
> selected.
> 
> You have a pretty old version of U-Boot there ...
> 
> 
>> When I boot the board it gives below error;
>>
>> *****
>> Starting kernel ...
>>
>> Uncompressing
>>
> Linux.......................................................................
>> ......................... done, booting the kernel.
>>
>> Error: unrecognized/unsupported machine ID (r1 = 0x00000356).
>>
>> Available machine support:
>>
>> ID (hex)        NAME
>> 00000385        DaVinci DM644x EVM
>>
>> Please check your kernel config and/or bootloader.
>>
>> ******
>> I dont have latest Bootloader source
> 
> http://www.denx.de/wiki/U-Boot ... 2009.03 should work.
> Though if you're using 1.1 silicion, I'd be paranoid
> and stick with that bootloader.
> 
> 
>> and hence I need to change the kernel
>> source to boot with same machine ID(passed by present bootloader..)which
>> file I need to change??
> 
> ---
> arch/arm/tools/mach-types |    5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
> 
> --- a/arch/arm/tools/mach-types
> +++ b/arch/arm/tools/mach-types
> @@ -862,7 +862,7 @@ magpie MACH_MAGPIE MAGPIE 850
> mx21ads MACH_MX21ADS MX21ADS 851
> mb87m3400 MACH_MB87M3400 MB87M3400 852
> mguard_delta MACH_MGUARD_DELTA MGUARD_DELTA 853
> -davinci_dvdp MACH_DAVINCI_DVDP DAVINCI_DVDP 854
> +#davinci_dvdp MACH_DAVINCI_DVDP DAVINCI_DVDP 854
> htcuniversal MACH_HTCUNIVERSAL HTCUNIVERSAL 855
> tpad MACH_TPAD TPAD 856
> roverp3 MACH_ROVERP3 ROVERP3 857
> @@ -908,7 +908,8 @@ nadia2vb MACH_NADIA2VB NADIA2VB 897
> r1000 MACH_R1000 R1000 898
> hw90250 MACH_HW90250 HW90250 899
> omap_2430sdp MACH_OMAP_2430SDP OMAP_2430SDP 900
> -davinci_evm MACH_DAVINCI_EVM DAVINCI_EVM 901
> +#davinci_evm MACH_DAVINCI_EVM DAVINCI_EVM 901
> +davinci_evm MACH_DAVINCI_EVM DAVINCI_EVM 854
> omap_tornado MACH_OMAP_TORNADO OMAP_TORNADO 902
> olocreek MACH_OLOCREEK OLOCREEK 903
> palmz72 MACH_PALMZ72 PALMZ72 904
> 
> 
> The information contained in this electronic message and any attachments to 
> this message are intended for the exclusive 
> use of the addressee(s) and may contain proprietary, confidential or 
> privileged information. If you are not the intended
> recipient, you should not disseminate, distribute or copy this e-mail. Please 
> notify the sender immediately and destroy
> all copies of this message and any attachments contained in it.
> 
> 
> 
> 
> 
> ------------------------------
> 
> _______________________________________________
> Davinci-linux-open-source mailing list
> Davinci-linux-open-source@linux.davincidsp.com
> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
> 
> 
> End of Davinci-linux-open-source Digest, Vol 40, Issue 180
> **********************************************************
_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Reply via email to