Promblem:
The developing board cannot find the Ethernet contgroller LAN91C11 on debug board, so they cannot connect each other.
Solution:
The CPLD code have to burn again.
what's happen to CPLD?
what changes CPLD's code?
7.30.2008
While I'm modifying the file, this file was changed already on Source Safe.
How can I do?
one way can do, to merge code before check in.
How can I do?
one way can do, to merge code before check in.
If my code base is too old from the code on Source Safe. How can I make sure that the code I merage won't affect to other people's, which causes complileing error.
- to update my code base
- get the lasest code on Source Safe and make sure it can be builded through the end
- merge my code which im developoing to the new code base and make sure it can be builded through the end
- check out the code what I want to merge
- merge 2 to my new code base and make sure it can be builded throough the end
- check in
7.22.2008
Build code hanging
to Build All the code, the builder stoped and poped the results as below:
the problem is cuased from UltraEdit. It sets the Script file for UltraEdit using and change the seting of builder.
Solution is from Sammy.
Understanding Makefile is useful.
"Microsoft (R) Program Maintenance Utility Version Test Version
Copyright
(C) Microsoft Corporation. All rights reserved.
Windows CE Version
(Release) (Built on Mar 1 2004 21:46:39)
makefile.def: Invoked with
predefined settings:
TARGETNAME: dummy
TARGETTYPE: dummy
RELEASETYPE:
TARGETLIBS:
SOURCELIBS:
makefile.def: Including
D:\WM612_AKU1.2_19958\public\common\oak\misc\Sources.default
makefile.def:
BUILDROOT is D:\WM612_AKU1.2_19958\public\ossvcs\cesysgen
0 Please add
_COMMONPUBROOT and __PROJROOT to your tree's cesysgen\sources file.
makefile.def: Including .\sources.
makefile.def: Including
D:\WM612_AKU1.2_19958\public\common\oak\misc\Sources.CE
makefile.def:
Including D:\WM612_AKU1.2_19958public\wpc\oak\misc\makefile.inc
Directory:
D:\WM612_AKU1.2_19958\PUBLIC\OSSVCS\CESYSGEN
TARGETNAME: dummy
RELEASETYPE is not defined. Using DEFAULT.
makefile.def: Including
D:\WM612_AKU1.2_19958\public\common\oak\misc\sources.ReleaseType_DEFAULT
輸入錯誤: 副檔名".js" 沒有對應的 Script 引擎。
NMAKE : fatal error U1077: 'cscript' :
return code '0x1'
Stop."
the problem is cuased from UltraEdit. It sets the Script file for UltraEdit using and change the seting of builder.
Solution is from Sammy.
Understanding Makefile is useful.
Image Update Device Side Features
*When started IPL(Initial Program Loader)->(check) Switch/Button & falg ->kenel image (normal boot) OR ->ULDR(Update Loader)
*Normal boot kernel starts&loads OS components to located in the kernel partition to point(OS can read from the system partition) At this point: nothing is located in the kernel partition until the run-time image is booted.
*Device update IPL knows where the master boot record(MBR). active partition is stored in the MBR. IPL loads the contents of active partition(kernel partition) to RAM(NAND,NOR), or jumps to startup address if the artition is NOR XIP kernel.
*Normal boot kernel starts&loads OS components to located in the kernel partition to point(OS can read from the system partition) At this point: nothing is located in the kernel partition until the run-time image is booted.
*Device update IPL knows where the master boot record(MBR). active partition is stored in the MBR. IPL loads the contents of active partition(kernel partition) to RAM(NAND,NOR), or jumps to startup address if the artition is NOR XIP kernel.
*during an update to the kernel partition to system partitionpackage mechanism donwloads (update packages) to (device's persistent user store)
UpdateBin- checks signature on the packages,
- validates the package contents,
- verifies versions,
- sets a flash update flag(update is available)
- rebbots the system. at reboot, IPL notes the flag and invokes ULDR.
*when ULDR is booted and runing from RAM, ULDR searches the validated packages in the user store (contains file system drivers).
begins update process one package at a time package information is recorded in the file system for useing by Update Validator on future updates. the update progress is tracked to allow for roll-forward updates in case a power failure occurs during the update.
*when all package contents have been applied and complete, the package can be removed from the user store or marked as completed. the flash update flag is cleared the device is rebooted.
Image Download Application
*provides the following functionality:
1. downloading the new disk image to device replacing the existing disk image.
2. downloading packages to the device in the Update Loader context. packages can be applied to the image by the ULDR.
*when a device boots, IPL jumps to the ULDR
the primary run-time image(pressing a switch/ software flag is set(packages need to be applied).
*when IPL jumps to the ULDR, ULDR run an update application to apply the available updates to the image , reboot the device, and updating the image
*because Image Download Application can downlade packages in the ULDR context, it is useful for the development enviroment or for failsafe image recovery.
*because the Impage Update model replaces the old boot loader model,
1. downloading the new disk image to device replacing the existing disk image.
2. downloading packages to the device in the Update Loader context. packages can be applied to the image by the ULDR.
*when a device boots, IPL jumps to the ULDR
the primary run-time image(pressing a switch/ software flag is set(packages need to be applied).
*when IPL jumps to the ULDR, ULDR run an update application to apply the available updates to the image , reboot the device, and updating the image
*because Image Download Application can downlade packages in the ULDR context, it is useful for the development enviroment or for failsafe image recovery.
*because the Impage Update model replaces the old boot loader model,
Subscribe to:
Posts (Atom)