DaVinci™ Video Processors

Browse by Tags

DaVinci™ Video Processors

Welcome to the DaVinci™ Video Processors Section of the TI E2E Support Community. Ask questions, share knowledge, explore ideas, and help solve problems with fellow engineers. To post a question, click on the forum tab then "New Post".

Tags
You have subscribed to this tag. To view or manage your tag subscriptions, click here.   Close
You have unsubscribed from this tag. To view or manage your tag subscriptions, click here.   Close
You are currently viewing:
dm6446
Related Posts

  • Forum Post: Re: DaVinci Module Configuration Registers

    Bernie Thompson TI
    I believe these are actually meant to be marked as reserved (someone can correct me if I am wrong here), so I think you may have found a bug in the DM644x datasheet, you should not need to use these MDCFG registers to use the device.
    on May 15, 2008

  • Forum Post: I get resizer errors when I try to run the demos included with the DVSDK

    Juan Gonzales
    When using DVSDK 1.20 on DM6446 EVM, please note that by default the Linux kernel (uImage) has resizer driver (used by demos) disabled. To enable resizer driver, launch menuconfig using the following command host $ make ARCH=arm CROSS_COMPILE=arm_v5t_le- menuconfig Then navigate to 'Device Drivers...
    on Jun 4, 2008

  • Forum Post: Re: Loading U-Boot

    Juan Gonzales
    I assume by DaVinci EVM, you mean DM644X EVM (DaVinci represents family of processors: DM355, DM644X, DM6467, DM643X...). If so, can you confirm the CS2 jumper is set to FLASH and S3 settings are 1011111110 (1=ON, 0=OFF). If the switch settings are correct, as soon as you power on the board (with,...
    on Jul 8, 2008

  • Forum Post: Re: Loading U-Boot

    SJackson
    What address is the BOOTCFG register at? The datasheet for TMS320DM6446 states that it is at 0x01C4 000A (section 3.3.1.1) while the "TMS320DM644x DMSoC ARM Subsystem Reference Guide" (SPRUE14A) indicates that BOOTCFG should be at 0x01C40014 (section 10.9). If the datasheet is right, then...
    on Jul 8, 2008

  • Forum Post: Re: Loading U-Boot

    Juan Gonzales
    0x01C40014 is correct. Actually, this value is also found in table 3-1 on the data-sheet; you seemed to have found a typo in section 3.3.1.1 of the data-sheet. I will make sure this gets corrected. Did you check the GEL file?
    on Jul 8, 2008

  • Forum Post: Re: Which IDE should I select to develop ARM side of 6446 in Linux system?

    Juan Gonzales
    Eclipse is a software platform, not necessarily a development tool; there are many eclipse-based IDE tools out there. Only the most recent version of DevRocket (v 5.0) supports Eclipse, not the version used in the App Note suggested in this thread. DDD is not a Eclipse based development tool, therefore...
    on Jul 14, 2008

  • Forum Post: My DaVinci EVM board is not behaving properly; how to I exchange it?

    Juan Gonzales
    Many of our DaVinci (DM355, DM6467, DM644X) boards are built by Spectrum Digital(SD). Therefore, if you suspect there is a problem with the EVM, you should do due digleence to try and verify the suspected problem area (there are normally board level tests posted on SD Website). If you still feel there...
    on Jul 18, 2008

  • Forum Post: I added the #define DEBUG and it worked in ccdc_davinci.c but not in davinci_vpfe.c can you tell me why?

    Juan Gonzales
    This post pertains to the Linux kernel found on DM355 and DM644x DVSDKs 1.30 and newer (and potentially other davinci platforms) Please note that '#define DEBUG" has to be added to the corresponding file before "linux/device.h" header file is included. CAUTION: Please note that...
    on Jul 23, 2008

  • Forum Post: In DM6446 DDR2 Controllers Guide sprue22c.pdf describes ‘VTP Buffer IO Calibration’, where is this taking place in the source code?

    Juan Gonzales
    VTP calibration is normally done once after power up; the source code is included in u-boot under "board/davinci".
    on Jul 25, 2008

  • Forum Post: Re: Linux Kernel Source Tree and Patches

    Juan Gonzales
    You should be able to see that option with DVSDK 1.20 as well.
    on Jul 28, 2008

  • Forum Post: Re: Linux Kernel Source Tree and Patches

    SJackson
    I figured out what I was doing that caused the Resizer driver to be unavailable. I had disabled the TI DaVinci EVM option under System Type and Featues -> TI DaVinci Implementations since it says it's for use on EVM boards, whereas I'm using a custom board. Enabling this caused the Resizer...
    on Jul 29, 2008

  • Forum Post: Re: Linux Kernel Source Tree and Patches

    Juan Gonzales
    The kernel build tree is made up of a hierarchy of build scripts which I will not attempt to describe here; but one aspect of this hierarchy is various Kconfig files that appear throughout the source tree, such as the one found in .../drivers/char If you look at ../driver/char/Kconfig file, you will...
    on Jul 29, 2008

  • Forum Post: Re: About EncodeDecode Demo

    Juan Gonzales
    1) Memory_getPhysicalAdress is an osal (OS abstraction layer) function; this means that it maps to a corresponding BIOS, Linux, WinCe... call depending on what target you are building for. It is part of codec engine and hence if you do not need to use codec engine at all, you can write your application...
    on Jul 30, 2008

  • Forum Post: Re: Using DAT_copy/DAT_wait and CACHE_ APIs on DM6437/DM648 processors

    Bernie Thompson TI
    I am not the most familiar with the DMAN3, but I believe you can use it with just framework components as opposed to the entire codec engine. The document below goes into some detail about using the DMA with framework components (including DMAN3), which may be of some help in this case as it also discusses...
    on Aug 5, 2008

  • Forum Post: Re: Using the Resizer

    Juan Gonzales
    Actually, now that you mention it; there is a hardware requirement that a video line be 32-byte aligned. Since YUV422 pixels are two bytes each, this means line lengths need to be multiples of 16 pixels (equals 32-bytes). 360 is not a multiple of 16, but 368 and 720 are; this is probably why the calcoeff...
    on Aug 13, 2008

  • Forum Post: Re: 6446 memory bandwidth DDR2

    Juan Gonzales
    Please note that DDR2 access (read and write) is always done in bursts of 32 bytes; this means that accessing 1 byte takes the same amount of time as accessing 32-bytes. Hopefully this helps explain some of the numbers you are seeing. We have measured throughput numbers of ~95% of theoretical 1296 MB...
    on Aug 19, 2008

  • Forum Post: Re: 6446 memory bandwidth DDR2

    Juan Gonzales
    The ~95% throughput was achieved using EDMA from DDR2 ->DSP L1D and DSP L1D -> DDR2. I do not have details on the testing environment (software or hardware setup), but will try to get some more details.
    on Aug 19, 2008

  • Forum Post: Re: Thermal Considerations

    SJackson
    I'm using a DM6446. Is it safe to say that this part runs cooler than the DM6467 and thus won't need any heat sinking?
    on Aug 22, 2008

  • Forum Post: Re: How do I put DM6446 EMIF bus in high-Z mode?

    Juan Gonzales
    I just checked with our hardware team; it appears you will need to use an external bus switch.
    on Aug 25, 2008

  • Forum Post: DM6446 EVM Encode Demo - Altering Frame Rates

    Jon4269
    Hi DSP Community, Regarding your encoder demo that comes with the DM6446 EVM, I cannot seem to determine what is setting the written file's frame rate. Also, how do the macros FBIOPAN_DISPLAY and FBIO_WAITFORVSYNC relate to the method calls in the code? (I assume that those macros are defined in...
    on Aug 27, 2008

  • Forum Post: Re: DM6446 EVM Encode Demo - Altering Frame Rates

    Juan Gonzales
    Jon, 1) The FBIO "macros" are really defines which identify the set of requests a Linux user application can send to the FBDev driver (a.k.a frame buffer driver). As you can guess, these driver requests are defined at the driver level in corresponding header files. The user application (e...
    on Aug 27, 2008

  • Forum Post: Re: DM6446 EVM Encode Demo - Altering Frame Rates

    HyperGalaxy
    Juan, Regarding the file playback rate, do you have some links to the appropriate MPEG standards (in particular the parts of the standard that define how to create the header information)? You would not happen to have an application that creates that header information, already, would you? (In my last...
    on Aug 27, 2008

  • Forum Post: Re: DM6446 EVM Encode Demo - Altering Frame Rates

    HyperGalaxy
    Juan, BTW, O'Reilly does not document anything related to the Linux framebuffer driver, but thanks for the link. If you do have any documentation on T.I.'s framebuffer implementation, macros, etc. that would be greatly appreciated, since there is very little documention on the framebuffer ioctl...
    on Aug 27, 2008

  • Forum Post: Re: DM6446 EVM Encode Demo - Altering Frame Rates

    Juan Gonzales
    I do not have access to MPEG standards, but have worked with them before. These can be quite complex and are made up of many documents. At the PES level, I believe they have a header that defines resolution, frame rate...; at the transport level it also has PTS and PCR information to help you keep audio...
    on Aug 27, 2008

  • Forum Post: EDMA3 TC0 register

    Sulaiman Sadiq
    I'm using the DM6446 XDS560 Emulator. The problem is that the value of the Error Status Register (ERRSTAT) is by default 0x000000008, which signifies that the MMR address error has occurred . According to sprue23d to clear a bit in the ERRSTAT you must write to the corresponding bit in the Error...
    on Apr 26, 2012
12345»

All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.

Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms of Use of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms of Use of this site. TI, its suppliers and providers of content reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.

TI Worldwide | Contact Us | my.TI Login | Site Map | Corporate Citizenship | mobile m.ti.com (Mobile Version)

TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs and
embedded processors, along with software, tools and the industry’s largest sales/support staff.

© Copyright 1995-2013 Texas Instruments Incorporated. All rights reserved.
Trademarks | Privacy Policy | Terms of Use