| Author |
Topic |
|
|
Susan
123 Posts |
 Posted - 07 Sep 2007 : 10:13:49
|
The HWT that I use for the BitsyX has considerably more entries than the default for the BitsyXB. I need to know which entries are no longer needed for the BitsyXB. I also need to know when the format of the entry has changed. I mention this because the entry for the specification of the DebugPort is different.
BitsyX:
0xA1E30044 0x0000003 ; Debug Port
BitsyXB:
[TAGS]
DebugPort 0x03
The are the entries that I am questioning...
1.
;-----------------------------------------------------
; BootSwitch,
; 9: Load CE files from ATA card if available, then Start CE.
; 5: Read CE image from Flash and Star CE
; 4: Load CE files from ATA card if available, then Start Menu on Debug Port
; 2: Start CE from ATA card if available.
; Menu on Debug port : Other cases and Failed from above
;-----------------------------------------------------
0xA1E30000 0x00000009 ; BootSwitch
This is in my BitsyX HWT. Under what circumstances, if any, would I need this entry? If I do require it, would it now fall under [TAGS] and be formatted as BootSwitch 0x00000009?
2.
0xA1E30014 0x0000001 ; Number of PCMCIA Sockets
This is also in my BitsyX HWT. Do I need this for the BitsyXB? If so, how is it formatted and under which section should the data be placed?
3.
;Optrex DMF-50961NF-SFW VGA Mono LCD
0x44000000 0x0030187E ; LCCR0
0x44000004 0x06040E7F ; LCCR1
0x44000008 0x010101DF ; LCCR2
0x4400000C 0x0340FF09 ; LCCR3
These are my monochrome display entries. For the BitsyXB should these now be placed under [TAGS], as follows?
[TAGS]
LCCR0 0x0030187E
LCCR1 0x06040E7F
LCCR2 0x010101DF
LCCR3 0x0340FF09
4. I also have the following entries in the BitsyX HWT.
;Memory Controller
;-----------------------------------------------------
0x48000000 0x00001BC9 ;MDCNFG, 64MB, DSA1111_0 Enabled
;0x48000000 0x00001BA9 ;MDCNFG, 32MB, DSA1111_0 Enabled
0x48000004 0x00018013 ;MDREFR
0x48000008 0x2DD02DD0 ;MSC0
0x4800000C 0x3FF41AA1 ;MSC1 (SA1111|CPLD)
0x48000010 0x02AC24AC ;MSC2_ADDR
0x48000014 0x00000000 ;MECR
0x48000018 0x00000000 ;SXLCR
0x4800001C 0x00000000 ;SXCNFG
0x48000020 0x01FE01FE ;FLYCNFG, Not Used
0x48000024 0x00000000 ;SXMRS
0x48000028 0x0000C084 ;MCMEM0
0x4800002C 0x0000C084 ;MCMEM1
0x48000030 0x0000C284 ;MCATT0
0x48000034 0x0000C284 ;MCATT1
0x48000038 0x0000C288 ;MCIO0
0x4800003C 0x0000C288 ;MCIO1
0x48000040 0x00000000 ;MDMRS
Are these no longer needed for the BitsyXB HWT?
Thank you...
|
|
|
grenierm
133 Posts |
Posted - 07 Sep 2007 : 16:44:40
|
Hi Susan, thanks for your questions.
1. The adsload.hwt uses a concept of default values, and therefore, it is necessary to have this key displayed in the event that you intend to modify the virtual switch setting, sometime in the future.
Also, BootSwitch 0x00000009 is correct for your current setting.
2. Again, like the virtual switch setting, it is only necessary in the event that you intend to modify it later. For instance, the BitsyXb has the capability of 1 or 2 PCMCIA slots if you were to add a CF personality board.
Also, NumberOfPCSockets 0x0000001 is correct for your current setting.
3. Your monochrome display entries are converted correctly.
4. As for the Memory controller, I will look into this further.
|
 |
|
|
grenierm
133 Posts |
Posted - 10 Sep 2007 : 10:17:03
|
| In regards to the Memory Controller tags, these should be defaulted in the BitsyXb and therefore, aren't necessary to include, unless you're modifying them. |
|
|
| |
Topic |
|
|
|
All Forums
Microsoft Windows CE
Migrating HWT entries from BitsyX to BitsyXB
Forum Locked
Send Topic to a Friend
Printer Friendly