This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DSP/BIOS problem

Other Parts Discussed in Thread: CCSTUDIO

Hi all,

I'm using c64x+ cycle accurate simulator on CCS 3.3.

When i am trying to create a new DSP/BIOS configuration from File->New, i get a dialog box titled
ScriptPane and message Unable to Create BIOS Config Server.

what could be the problem?

waiting for your replies,

 regards,

Sandeep

 


 

  • This has been known to come up with some versions of DSP/BIOS and CCS, in the past we found that this could be caused if the BIOSConfigSvr.dll file from C:/CCStudio_x.x/plugins/bios was not properly registered with windows, so one possible solution is to re register this dll using the regsvr32 command from a windows command prompt, for example:

    >> cd C:\CCStudio_3.3\plugins\bios
    >> regsvr32 /u BIOSConfigSvr.dll
    >> regsvr32 BIOSConfigSvr.dll

    If this is not possible or does not fix it you may want to reinstall CCS or reinstall/upgrade BIOS. Note that you can get newer versions of DSP/BIOS from the update advisor site available from under the help menu of CCS. Once you have another version of BIOS installed you can switch between them using the component manager of CCS available under the help->about menu, chances are that installing a newer BIOS version, even a single version step, will fix any broken DLL links and resolve this type of problem.

    Note that CCS does require administrative privelages on the host machine to operate properly, both during installation and usage.

  • I have this same problem. I don't have this DLL you mentioned. These are all the DLLs with "bios" in the name:

    $ find -name "bios*.dll"
    ./bios_5_31_02/packages/ti/bios/config/gconf/bin/bioscfg.dll
    ./bios_5_31_02/packages/ti/bios/config/gconf/bin/biosres.dll
    ./cc/bin/biosvers.dll

    If I try to run regsvr32 on any of them, I get a mystery error:

    "xxxxxx.dll was loaded but the DllRegisterServer entry point was not found. This file caqn not be registered."

    I am running Windows XP, and I am an administrator. I have CC Studio 3.3. What is the problem here?

    Edit: I tried re-installing CC Studio (being careful to shut down every other running program first). It didn't make any difference. During the install, I got a mystery warning about not having Active State Perl installed, so I'm installing that, but I don't expect it to help.

  • That is quite strange, particularly for the regsvr32 to fail on all of the dll files, based on a Microsoft KB article it sounds like this error should only happen if the dll file is not a dll file, is not exportable, or is otherwise corrupted, but for it to fail on all of the dll files seems unlikely. This being said, my first suspicion would be that your regsvr32 exe may be corrupted, or some virus/malware is preventing you from registering dll files, however this is just a guess. Can you run regsvr32 successfully on any dll in your system?

    As to the Perl, you do not really need that for most CCS functionality (and it should be entirely unrelated to BIOS DLL files), you would only need Perl if you were doing any CCS scripting.

  • I can register other dlls in the system using regsvr32. But I can't register the TI dlls.  

  • Perhaps there is something corrupted in the installation media? In this case, you may want to try using another/newer version of BIOS you can download from here after logging into my.ti. If you still cannot register the dll files from another freshly downloaded version than I am just about out of ideas, as that should take out any strangely corrupted file issues.

  • Fixed.

    I installed DSP/BIOS 5.33.04, then went to help->about and selected the new version for every selection that gave me a choice. That solved it.

    The weird thing is, CC Studio 3.3 ships with DSP/BIOS 5.31.02, so you would expect it to work. How is it possible that an install disk that is not self-consistent is being shipped?

  • I am glad to hear you got it working, and I can say that CCS 3.3. with BIOS 5.31.02 does generally work, I am not sure why it stopped working for your particular case, you see these sort of issues from time to time, but usually only when something else installed with CCS (like a plugin or component upgrade) breaks things meaning a reinstall would fix it. This is the first such issue I have seen where a uninstall/reinstall of CCS did not fix the dll files properly (not counting OS issues like administrative privelages).

  • So it's probably the reinstall that fixed things, not the upgrade per se. That's plausible because CCS popped a "found new components" dialog the first time I ran it after the DSP/BIOS upgrade. Anyhoo, thanks for your help. I think I'm up & running now.

  • Hi all

    i'm trying to run my h264 decoder on DM6467.

    I got a pretty big numbers of MCPS while running the code in EVM. I thought that it may be becoz of loading data from external

    memory. so i'm trying now to enable caching. for that from the threads i came to know that i need to create DSP/BIOS configuration

    tcf file. so i installed dsp/bios_5_32_04 with my ccs 3.3. now i'm trying to open file->new->dsp/bios configuration. but i'm getting nothing...not even some error message.

    i tried uninstalling the earlier version of bios that i had along with ccs 3.3 and reinstalling the new bios version. nothing helped.

    so what may be issue...

    any help will be greatly appreciated

    thanks n regards

    Gomathi

  • Gomathi,

    Are you bypassing the codec engine framework included with the DM6467 DVSDK software?  If you are incorporating your h.264 codec into the codec engine framework, the framework will take care of caching for you. 

    If you are bypassing codec engine framework, then someone else may be able to chime in and help as this is outside my area of expertise.

  • Hi Juan,

     Thanks for the reply

    I’m not using codec engine framework.jus want to have a standalone decoder exploiting hdvicp accelerators

  • After the update make sure you go to the component manager and select your newly installed version of  BIOS for your corresponding ISA (in your case 64XX).  Then restart CCS, double-check that it shows up under help -> about and you should be all set.

    If that's not working then I suspect that something on your computer is interfering with the installation, i.e. some kind of firewall, anti-virus, etc.

    Brad

  • thanks for the suggestions..

    but i'm now trying to enable the cache without using bios since it looks pretty straight forward for me

    i did like the one below

    /* i'm setting the regs here (all my settings are for DM6467)*/

    #define MAR128 *((volatile unsigned int *)(0x01848200))
    #define MAR129 *((volatile unsigned int *)(MAR128 + 0x04))
    #define L2CFG  *((volatile unsigned int *)(0x01840000))
    #define L1PCFG *((volatile unsigned int *)(L2CFG + 0x20))
    #define L1DCFG *((volatile unsigned int *)(L2CFG + 0x40))

    /* enabling them with 32k, 32k, 128k respectively for L1D, L1P, L2*/

     MAR128 = MAR128 | 0x01; /* enable caching for external memeory*/
       MAR129 = MAR129 | 0x01;
     *((unsigned int *) L2CFG)  = 4;
     *((unsigned int *) L1PCFG) = 4;
     *((unsigned int *) L1DCFG) = 4;

    /* my cmd looks like this */

         IRAM               : origin = 0x11818000,  len = 0x10000
        CACHE_L2    : origin = 0x11828000,  len = 0x10000

        L1PSRAM        : origin = 0x11e00000,  len = 0x6000
        CACHE_L1P   : origin = 0x11e06000,  len = 0x2000
     
        L1DSRAM         : origin = 0x11f00000,  len = 0x2000 
        CACHE_L1D   : origin = 0x11f02000,  len = 0x6000

        DDR2                : origin = 0x80000000,  len = 0x10000000

    /**************************/

    anything else need to be done here, becoz i didn't get much difference in my mcps (got 200 less) after enabling cache.

    how to make sure whether it is enabled or not ?

    thanks in advance

    regards

    Gomathi

  • Gomathi said:

    #define MAR128 *((volatile unsigned int *)(0x01848200))
    #define MAR129 *((volatile unsigned int *)(MAR128 + 0x04))
    #define L2CFG  *((volatile unsigned int *)(0x01840000))
    #define L1PCFG *((volatile unsigned int *)(L2CFG + 0x20))
    #define L1DCFG *((volatile unsigned int *)(L2CFG + 0x40))

    Since you are dereferencing your pointers you cannot use them inside the definitions of other pointers.  You need to rewrite as

    #define MAR128 *((volatile unsigned int *)(0x01848200))
    #define MAR129 *((volatile unsigned int *)(0x01848204))
    #define L2CFG  *((volatile unsigned int *)(0x01840000))
    #define L1PCFG *((volatile unsigned int *)(0x01840020))
    #define L1DCFG *((volatile unsigned int *)(0x01840040))

    Gomathi said:

    /* enabling them with 32k, 32k, 128k respectively for L1D, L1P, L2*/

     MAR128 = MAR128 | 0x01; /* enable caching for external memeory*/
       MAR129 = MAR129 | 0x01;
     *((unsigned int *) L2CFG)  = 4;
     *((unsigned int *) L1PCFG) = 4;
     *((unsigned int *) L1DCFG) = 4;

    Your L2 configuration is for 256k, though you rcomment says 128k.  Also, your pointers need to be volatile.

    Gomathi said:

    /* my cmd looks like this */

         IRAM               : origin = 0x11818000,  len = 0x10000
        CACHE_L2    : origin = 0x11828000,  len = 0x10000

    Your L2 cache size is 64k, but you are configuring 256k as cache.

    Gomathi said:

        L1PSRAM        : origin = 0x11e00000,  len = 0x6000

        CACHE_L1P   : origin = 0x11e06000,  len = 0x2000

     


    Your L1P cache definition is 8KB yet you have configured for 32KB of cache.

    Gomathi said:

       L1DSRAM         : origin = 0x11f00000,  len = 0x2000 
        CACHE_L1D   : origin = 0x11f02000,  len = 0x6000

    24KB of L1D cache???

    Gomathi said:

        DDR2                : origin = 0x80000000,  len = 0x10000000

    You show 256MB of DDR2, yet you are only setting 2 MAR bits.  That means you're only making the first 32MB cacheable.

    Gomathi said:

    anything else need to be done here, becoz i didn't get much difference in my mcps (got 200 less) after enabling cache.

    Check the *CFG registers and the MAR registers through a memory window to verify they are all set to the appropriate values.  Also, you might want to look at your data buffers in a memory window.  There is color highlighting in the memory window to indicate when something is actually cached.