Forums

can you try this on a pure windows XP machine instead of a virtual image? We have built the DVSDK several times on the windows XP machine and have not been able to reproduce the problem.

-Madhvi

Also, is there a reason that you need c6accel component?

I am not sure if you are already aware of this: The c6accel component is a standalone component and has nothing to do with the other supplied WinCE DVSDK components like the video codecs (codecserver) and dshow filters (in short, existing video/audio playback DVSDK components).

-Madhvi

Sorry for so late reply.

Do you realy think the cause of the error:
"c6accelw.c(15) : fatal error C1083: Cannot open include file: 'xdc/std.h': No such file or directory"
may be a virtual machine? I'm not sure, but I think the probability of this is very little.

We need c6accel for signal processing and math operations with DSP.
Ultimately, for us there is no need for DVSDK in general, the only thing we need is c6accel.
Is it possible to obtain c6accel libraries to use in Windows CE without the DVSDK?

c6accel.log:

3872.c6accel.log

setpaths.bat:

8182.setpaths.bat.txt

Installed soft (apart from DVSDK):

C:\TI\bios_5_41_00_06

C:\TI\BSP_WINCE_ARM_A8_01_02_00

C:\TI\CGTools_6_1_9

C:\TI\xdctools_3_16_01_27

C:\Perl

I cannot say for sure if its the virtual environment causing this issue. Here are the 2 facts:

1. You are getting the error because c6accel build files cannot resolve the _WINCEROOT variable. All other DVSDK components have no issue but just c6accel files. I dont know the reason behind this.

2. We use only XP machines to build DVSDK (no VM) and we dont see the issue.

Since I cannot reproduce the issue - either you can try to fix issue pointed in fact#1 or try building on a XP machine and compare the 2 results.

-Madhvi

I try to compile the whole project on a vmware windows 7 x86 os, the result is ok without c6accel, but cause the same error when I select the c6accel. I conside ti should recompile the project with c6accel on a virtual machine to repeat the error and find the real problem!

So, I tried to build BSP with DVSDK(c6accel) on NON-virtual Windows XP (with using "DVSDK for Windows CE Software Setup" manual).

But now I have another error. 

My c6accel.log for this machine:

1768.c6accel.log

Also, for my vitual machine i have added next strings to setpaths.bat:

set _WINCEROOT=
set _WINCEROOT=C:\WINCE600

set C6X_C_DIR=
set C6X_C_DIR=C:\TI\CGTools_6_1_9\include;C:\TI\CGTools_6_1_9\lib

- then tried to rebuild BSP with subprojects. Now the error is different from the previous one.

c6accel.log for virtual machine:

2437.c6accel_vm.log

Can you please say what is the problem in these two cases?

If you need more information, please let me know.

Thank you.

Is there anyone alive? )

For the second issue, a quick look at the error and the makefile.wince shows that the env variable _TGTCPUFAMILY is missing. It should be set to ARM.

This (as well as _WINCEROOT) are standard WINCE build variables that should be already set if you are building from PB or building from a cmd window opened from PB->Build->"Open Release dir in build window".  You can try by just setting this variable but you may encounter more errors. I'm not sure why these don't show up in your environment.

Thank you for your answer.

What about first issue? Is it possible that the cause of the error is non-english (russian) Windows localization?

Hello,

I have the same issue as well while RE-building DVSDK, e.g.,
Error: Could not find file 'D:\Wince600_Zack_2_22\OSDesigns\EVM_3530\EVM_3530\RelDir\EVM_OMAP3530_ARMV4I_Release\c6accel_app.exe' on disk
c6accelw.c(15) : fatal error C1083: Cannot open include file: 'xdc/std.h': No such file or directory
configuring c6accelw using c6accelw.cfg
C:\Tools\xdctools_3_16_01_27/xs xdc.tools.configuro -c  \
              -o wince/omap3530 \
              -t microsoft.targets.arm.WinCE \
              -p ti.platforms.evm3530 \
              -b wince/config.bld \
              c6accelw.cfg

I tried to re-install the DVSDK, dvsdk_wince_01_11_00_03_patch_01_setup.exe, again with a clean/working BSP. The build still failed even with all DVSDK components disabled in setbuild.bat. In this case, how do I get the error?

Have anyboday figured out why:
"1. You are getting the error because c6accel build files cannot resolve the _WINCEROOT variable. All other DVSDK components have no issue but just c6accel files. I dont know the reason behind this." per Madhvi on 12-29-2011? My goal is to have a good baseline before recompiling or changing any DVSDK components.

Please help. Thanks,

Ying

Hello,

We'll start investigating the DVSDK issue over the next week starting on Monday, Feb 28 and expect to have an update by the end of the week.

If there is any new information on the problem please let us know.

Regards,

Adeneo Embedded Support

I was able to get a build in the Platform Builder last Friday. 4 build variables are not recognized by c6accel: _WINCEROOT, _PROJECTROOT, _TGTCPUFAMILY, and _TGTCPU in 2 makefile.wince files in folders dvsdk_wince_01_11_00_03_patch_01\src\c6accel_1_01_00_02\soc\c6accelw and \soc\app. My workaround was to re-define _WINCEROOT and _PROJECTROOT with the path and use_tgtcpufamily and _tgtcpu. How come they are also case sensitive?

Hi,

What is the news about DVSDK issue?

Adeneo Embedded support team

Hello,

We'll start investigating the DVSDK issue over the next week starting on Monday, Feb 28 and expect to have an update by the end of the week.

If there is any new information on the problem please let us know.

Regards,

Adeneo Embedded Support

I notice the following in prelink.bat for DSPLink (e.g., dvsdk_wince_01_11_00_03_patch_01\src\dsplink_1_65_00_03\dsplink\etc\host\projects\WinCE\DSPLink\prelink.bat):

@rem *************************************************************************************************
@rem * For some unknown reason, PB converts all environment variable names from mixed case to lower case
@rem * So this a simple batch trick to convert them (only relevant to dsplink) back to desired mixed case
@rem * which gmake expects
@rem *************************************************************************************************

@rem create the list of variable names. The desired mixed case format name followed by the lower case format name
@set VAR_NAMES_SET=_WINCEROOT _winceroot _PROJECTROOT _projectroot _TGTCPU _tgtcpu _TARGETPLATROOT _targetplatroot
@set VAR_NAMES_SET=%VAR_NAMES_SET% _FLATRELEASEDIR _flatreleasedir WINCEDEBUG wincedebug ComSpec comspec TEMP temp
@set VAR_NAMES_SET=%VAR_NAMES_SET% TI_TOOLS_BASE_DIR ti_tools_base_dir XDC_INSTALL_DIR xdc_install_dir PATH path

@set VAR_NAMES_SET=%VAR_NAMES_SET% BIOS_INSTALL_DIR bios_install_dir BASE_PERL base_perl CODEGEN_INSTALL_DIR codegen_install_dir
@call :Loop4 %VAR_NAMES_SET%
@goto start_build

@rem this loop just processes the variables in VAR_NAMES_SET one set (pair) at a time

:Loop4
@if [%1]==[] goto:EOF
@call set my_temp=%%%2%%
@set %2=
@set %1=%my_temp%
@shift
@shift
@goto Loop4

:start_build
@set VAR_NAMES_SET=
@set my_temp=

Looks like a similar approach may be needed for c6accel.

Adeneo Embedded Support team:

Is it what you found out?

Ying

I was able to get a build in the Platform Builder last Friday. 4 build variables are not recognized by c6accel: _WINCEROOT, _PROJECTROOT, _TGTCPUFAMILY, and _TGTCPU in 2 makefile.wince files in folders dvsdk_wince_01_11_00_03_patch_01\src\c6accel_1_01_00_02\soc\c6accelw and \soc\app. My workaround was to re-define _WINCEROOT and _PROJECTROOT with the path and use_tgtcpufamily and _tgtcpu. How come they are also case sensitive?

This is what i need. Thank you very much.