Author |
Topic |
|
Consultpinnacle
29 Posts |
Posted - 22 Sep 2004 : 07:15:06
|
Hi
We are experiencing some issues in the field with our AGX units.
Currently when we receive the AGX boards from yourselves we carry out the following process:
1. Load up debug console and erase flash fx disk. 2. Restart unit and load our custom win ce build from a compact flash card. 3. Once the OS has been installed we copy our application using active-sync onto the AGX board. 4. We test the software and carry out a q/a procedure which involves restarts of the AGX. 5. The unit is then deployed to the customer.
We are now receiving faulty units back from the customer, which seem to have reverted back to a version of wince that was on the board when shipped from ADS and our application also does not exist on the unit anymore.
Could you please communicate what could be the cause of this as it seems that the AGX is completely re-setting itself and removing the software and OS that we have loaded.
Regards
Graham Libaert |
|
akidder
1519 Posts |
Posted - 22 Sep 2004 : 07:52:21
|
Wow! I haven't heard of this one before! While we've considered an architecture that includes a "backup" CE image, this is not a feature that we have implemented. The only way a CE image can get changed is either using a CF card or by programming the flash directly from your application.
As for the application, am I guessing correctly that you install the exe to the flashfx disk\startup folder? If something happens to the flash disk, your application won't start up. The first thing you might do is to check how the flash disk looks.
Do you leave a CF card inserted in the system when you boot? How are the DIP switches set when you ship your systems? Both of these could affect the CE image and launch of your application.
It may be that part of your QA test procedure should be to confirm that the right version of CE is loaded. My bet is that the new version was not ever loaded (a trick often used by magicians, as well).
Let us know what you find! |
|
|
Consultpinnacle
29 Posts |
Posted - 23 Sep 2004 : 04:10:11
|
Hi Drew
We have use two folders for our application.
1. Startup 2. Tracking
The startup folder contains an .exe that controls all the applications under the Tracking folder. We can also validate our OS has been loaded initially, because we have a custom dialup connection as part of the build - and the application would not work without it.
S1 is set to the following to load our OS:
Selector Position Selector 1 1 Selector 2 2 Selector 3 0 Selector 4 4
S1 is then set to the following once we have loaded our OS:
Selector Position Selector 1 0 Selector 2 2 Selector 3 0 Selector 4 4
Below is the jumper configuration we are using:
Jumper Connect Pins JP1 (1 - 2) JP2 (1 - 2) JP3 (1 - 2) JP4 (1 - 2), (3 - 4), (7 - 8), (9 - 10), (11 - 12), (15 - 16), (17 - 18) JP5 No Jumper JP6 No Jumper JP7 No Jumper JP9 (1 - 2) JP10 (2 - 3) JP11 (2 - 3) JP12 (2 - 3) JP13 (2 - 3) JP14 (2 - 3) JP36 No Jumper JP37 No Jumper
Thanks
Graham
|
|
|
|
Topic |
|
|
|