-
哦 ，有可能你们说的是对的，我再好好看看。
-
是否跟LCD屏有关，自己定制的LCD屏。
显示模式：TN 正显
偏光片类型：反射
观察角度：6：00
驱动条件:1/4 DUTY,1/3 BIAS
工作电压:3.0V
连接方式:PIN
-
RVDSV2.2跟ADS1.2差不多,但他们跟RVDSV4.0都相差的很远.RVDSV4.0有一个WORKBENCH IDE.
-
需要添加哪个组件,还望明示。
-
学习一下。
-
其实我发这个帖子 无非是我打算修改LOGO 也就是吧LOGO放到NAND中 让系统去读：
现在问题又来了：
利用eboot下载LOGO.BIN文件，自己添加了下载的命令，并修改了EBOOT.BIN文件，但是在下载LOGO.BIN的时候
停留在：
Enter your selection: u
System ready!
Preparing for download...
Please send the Image through USB.
OCSR1.out_pkt_rdy = 0x1
Ep3Handler : downPtIndex = 0x32000040
Download BIN file information:
-----------------------------------------------------
[0]: Base Address=0x800a1000 Length=0x26400
-----------------------------------------------------
跟踪了下代码，应该接下去将要显示：
rom_offset=0x0.
ROMHDR at Address 。。
即没有执行这个函数：
E:\WINCE500\PUBLIC\COMMON\OAK\DRIVERS\ETHDBG\BLCOMMON\blcommon.c下的
// we're downloading a .bin file - download each .bin record in turn...
else
{
while (OEMReadData (sizeof (DWORD), (LPBYTE) &dwRecAddr) &&
OEMReadData (sizeof (DWORD), (LPBYTE) &dwRecLen) &&
OEMReadData (sizeof (DWORD), (LPBYTE) &dwRecChk))
{
// last record of .bin file uses sentinel values for address and checksum.
if (!dwRecAddr && !dwRecChk)
{
break;
}
// map the record address (FLASH data is cached, for example)
lpDest = OEMMapMemAddr (pCurDownloadFile->dwRegionStart, dwRecAddr);
// read data block
if (!OEMReadData (dwRecLen, lpDest))
{
EdbgOutputDebugString ("****** Data record %d corrupted, ABORT!!! ******\r\n", nPkgNum);
HALT (BLERR_CORRUPTED_DATA);
return (FALSE);
}
if (!VerifyChecksum (dwRecLen, lpDest, dwRecChk))
{
EdbgOutputDebugString ("****** Checksum failure on record %d, ABORT!!! ******\r\n", nPkgNum);
HALT (BLERR_CHECKSUM);
return (FALSE);
}
// Look for ROMHDR to compute ROM offset. NOTE: romimage guarantees that the record containing
// the TOC signature and pointer will always come before the record that contains the ROMHDR contents.
//
if (dwRecLen == sizeof(ROMHDR) && (*(LPDWORD) OEMMapMemAddr(pCurDownloadFile->dwRegionStart, pCurDownloadFile->dwRegionStart + ROM_SIGNATURE_OFFSET) == ROM_SIGNATURE))
{
DWORD dwTempOffset = (dwRecAddr - *(LPDWORD)OEMMapMemAddr(pCurDownloadFile->dwRegionStart, pCurDownloadFile->dwRegionStart + ROM_SIGNATURE_OFFSET + sizeof(ULONG)));
ROMHDR *pROMHdr = (ROMHDR *)lpDest;
// Check to make sure this record really contains the ROMHDR.
//
if ((pROMHdr->physfirst == (pCurDownloadFile->dwRegionStart - dwTempOffset)) &&
(pROMHdr->physlast == (pCurDownloadFile->dwRegionStart - dwTempOffset + pCurDownloadFile->dwRegionLength)) &&
(DWORD)(HIWORD(pROMHdr->dllfirst dllfirst
-
没有其他提示，看了下批处理。
这个文件preromimage.bat 的 if "%MAKEIMG_NEXT_CMD%" NEQ "" exit %ERRORLEVEL% 直接返回 1 ，产生了错误。但为什么 %ERRORLEVEL% 是 1 不清楚。 %ERRORLEVEL% 的值 是由于那就DOS 命名错误导致的该怎么查阿？另外，%ERRORLEVEL%得值怎么改成 0 阿？preromimage.bat 的完整内容如下：
@REM
@REM Copyright (c) Microsoft Corporation. All rights reserved.
@REM
@REM
@REM Use of this sample source code is subject to the terms of the Microsoft
@REM license agreement under which you licensed this sample source code. If
@REM you did not accept the terms of the license agreement, you are not
@REM authorized to use this sample source code. For the terms of the license,
@REM please see the license agreement between you and Microsoft or, if applicable,
@REM see the LICENSE.RTF on your install media or the root of your tools installation.
@REM THE SAMPLE SOURCE CODE IS PROVIDED "AS IS", WITH NO WARRANTIES.
@REM
@if not defined _echoon echo off
REM
REM PREROMIMAGE.BAT
REM This batch file gets called by romimage.exe before creating
REM the image.
REM
REM This batch file is the "meta" batch file, it will call
REM a batch file for each entry in the _DEPTREES variable
REM named -preri.bat
REM Plus the batch file %_TGTPLAT%-preri.bat gets called last.
REM
echo.
echo PREROMIMAGE processing...
echo.
pushd %_FLATRELEASEDIR%
for %%f in (%_DEPTREES%) do (
if exist %%f-preri.bat (
echo PREROMIMAGE calling %%f-preri.bat
call %%f-preri.bat
)
)
if exist %_TGTPLAT%-preri.bat (
echo PREROMIMAGE calling %_TGTPLAT%-preri.bat
call %_TGTPLAT%-preri.bat
)
@REM this line makes sure we're running as part of makeimg before closing the cmd window
@REM (makeimg actually spawns a new cmd window when it calls preromimage)
if "%MAKEIMG_NEXT_CMD%" NEQ "" exit %ERRORLEVEL%
echo.
popd
-
Thanks for opening it!!!!!!
-
工业以太网的稳定性肯定要高些，要求也高些
-
不容易,因为CE5.0下没有RIL
-
使用了MFC并不一定需要启动explorer.exe的，我用MFC开发的应用程序就可以在没有explorer.exe的情况下运行。因此，应用程序界面死了与explorer.exe无关
-
带os 的与不带os 的，跳转到的位置也不一样，很奇怪啊，
-
不是有链接嘛，2，3百快吧
-
up
-
引用 3 楼 great_bug 的回复:
不会是正巧你用了个坏的DM9000吧?
那可能是这批货是坏的。我换了三个都这样。
-
串口编程在kenrel的本质是文件系统层+串口芯片驱动层, 在kernel里面你可以看到其实所谓的open和close对应到串口芯片地驱动里面地代码只是把串口芯片地收发中断使能和关闭. 但是既然串口作为一个设备, 当然要遵从设备文件地基本属性, 看设备打开时用的参数. open后如果不关导致地后果你前面地写和后面地写会叠加输出. 前面的读和后面的读则会看输入数据进入串口接收buffer的时机.
-
引用 1 楼 lgy198612 的回复:
你只要给开板公司注明：覆满绿油
别人就帮你弄好。
额。。。就知道有这样的回复，之前是这么做的，现在想要在PROTEL99上改
-
请问用什么烧录软件？ 能具体说说名字或者用法吗？
-
看样子我得请韦伯大哥吃饭了！呵呵！再次感谢下！我现在跟到OEMLANCH发现个问题
+OEMLaunch.
+OEMLaunch+++baggio dwImageStart=-2145386496.
+OEMLaunch++ baggio dwImageLength=14967164.
+OEMLaunch+++baggio dwLaunchAddr=-2145199368.
+OEMLaunch+++baggio g_bDownloadImage=1.
+OEMLaunch+++baggio g_pBootCfg->ConfigFlags & TARGET_TYPE_NAND=0.
上面是调试信息
在oemlanch中有个判断
if (g_bDownloadImage && (g_pBootCfg->ConfigFlags & TARGET_TYPE_NAND))
我不知道这个判断的意思是什么？？但是我红色部分读出来是0 我不知道为什么是0？？这是那个宏
#define TARGET_TYPE_NAND 0x00000800 // NAND Flash
想问下韦伯兄 这是什么判断？？是干嘛的呢？？这里进不去 我就不能在下载nk时写入TOC 导致读出的都是0？？
-
分层还是流驱动？
嵌入式系统