| Author |
Topic |
|
|
Susan
123 Posts |
 Posted - 10 Dec 2007 : 08:02:09
|
Similar to the problem reported at Topic 900, I'm getting the same message box now with the BitsyXb. Adding the HWT entry specified at Topic 828 not only did not help (that was as mistake), but appears to have put my BitsyXb board in a state that is in need of being JTAGged.
Do I require a 'no-CF' build, or a different HWT entry than is specified at Topic 828?
|
|
|
Susan
123 Posts |
Posted - 09 Mar 2009 : 10:44:00
|
This project was passed on to a co-worker. He is nearing completion, and I come to find that this question/issue has never been answered.
BitsyXB, ROM 2.1, CE Image 5.00.32 Pro, there is no Personality Board attached.
When the desktop is displayed, a message box appears titled "Unidentified PCCard Adapter". The message box contains a control in which you are supposed to enter the "Driver Name:". Above this control is the phrase "Enter the name of the driver for this PC Card." The control reads (by default) "Unknown card in Socket 2".
We use the compact flash interface for data collection. There must be someone remaining at ADS (besides Drew) who is familiar with our system.
Referring to Topic 828, NoCF is obsolete. Therefore, also refering to Topic 828, Drew Kidder's response on 05Mar2003, 18:41:18, what is the corresponding HWT entry for the BitsyXB so that the following is fulfilled "This entry defines how many sockets the boot code should check when set up to load from PCMCIA/CF. The CE image also uses this information to determine if a CF card or the Ethernet personality board is installed."
2 : Bitsy CF or Ethernet personality board.
Boot code and CE image detects Ethernet automatically.
1 : No ADS CF or Ethernet personality board.
Bitsy Plus will have only the PCMCIA slot for updates.
Use this value for custom personality boards that don't
use the ADS CompactFlash or Ethernet designs.
0 : Reserved for backward compatibility.
The following line apparently does not work.
0xC0000F18 0x00000000 ; number of PCMCIA/CF sockets
Nor does
0xC0000F18 0x00000001 ; number of PCMCIA/CF sockets
I am guessing that 0xC0000F18 needs a Tag. What is that Tag?
Thank you.
|
 |
|
|
cbadr
154 Posts |
Posted - 12 Mar 2009 : 18:05:19
|
| Would it be possible to test your system with the latest OS image and bootloader and see if the problem persists? You can download them from topics 2100 and 2101 respectively. Let us know the results. |
|
|
|
Susan
123 Posts |
Posted - 17 Mar 2009 : 08:42:36
|
| The problem persists with Rom 2.12, 5.00.49 Core and 5.00.47 Pro |
|
|
|
grenierm
133 Posts |
Posted - 18 Mar 2009 : 13:57:26
|
Hi Susan,
Thanks for your question and the excellent overview.
You are correct that for the BitsyXb HWT, we use Tags to represent the addresses. For your case specifically, the tag should be the following format:
NumberOfPCSockets 0x0000001; number of PCMCIA/CF sockets
If you have any further BitsyX to BitsyXb HWT migration questions, please take a look Eurotech Forum Topic 2452 [which you are particularly familiar with :)]or feel free to drop us a line directly at support.us@eurotech.com |
|
|
|
Susan
123 Posts |
Posted - 19 Mar 2009 : 11:04:08
|
Matt,
Using Rom 2.12, image 5.00.39 Pro, and adding the specified TAG to the HWT did not clear up the problem.
The TAGS section of our HWT reads as follows:
;---------------------------------------------------------------------
; The TAGS section defines values for hardware table members by
; specifying a table member descriptor and then its value.
; Tags are case-insensitive (NOT case-sensitive).
;---------------------------------------------------------------------
[TAGS]
MouseDetect 0x00
DebugPort 0x03
;StopDebugMsg 0x01
BootLogo 0x00000000 ; Boot logo: 0x00=none, 0x01=ADS logo(b/w)
;BootLogo 0x00000002 ; Boot logo: 0x00=none, 0x01=ADS logo(b/w)
; 0x02=adsload.bmp
LogoBckGround 0x00003B74 ; Background color: 0x00=black, 0xFF=white
; @16bpp, 0x3B74=CE.NET background color
; 07Oct2004 SMR One socket
;-----------------------------------------------------
; SMR 0xA1E30014 0x0000002 ; Number of PCMCIA Sockets
; SMR 18Mar090xA1E30014 0x0000001 ; Number of PCMCIA Sockets
NumberOfPCSockets 0x0000001; number of PCMCIA/CF sockets
Please advise.
Thank you. |
|
|
|
beitman
63 Posts |
Posted - 24 Mar 2009 : 15:14:05
|
Susan:
I do not have a way to test this, because it works with our connector boards. Could you try this in your ADSLoad.reg:
[HKEY_LOCAL_MACHINE\Comm\LAN9000]
"ImagePath"="NOLOAD_LAN91C111.DLL"
[HKEY_LOCAL_MACHINE\Comm\LAN90001]
"ImagePath"="NOLOAD_LAN91C111.DLL"
I beleive that the absense of an Ethernet controller causes the NumberOfPCSockets to be set to 2, which causes the problem that you see. This will disable the Ethernet driver and leave NumberOfPCSockets set to 1.
If that doesn't work, this will:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PCCARD1]
"Flags"=dword:4
That will prevent the PCCard driver from running for the CF socket.
Both would actually make sense for your system.
Bruce |
|
|
|
Susan
123 Posts |
Posted - 25 Mar 2009 : 11:41:44
|
Good Morning Bruce,
Thank you for the information. I am out of the office due to a family member's illness. I may or may not be able to test this before tomorrow. I will keep you informed.
Thanks, Susan |
|
|
|
beitman
63 Posts |
Posted - 27 Mar 2009 : 14:47:21
|
All:
I worked with Susan yesterday on this issue. The registry settings do work to disable the BitsyXb compact flash slot.
One note: The "Flags"=dword:4 setting takes a second boot to take affect. This is becuase the device manager has already read the value from the registry before the ADSLoad.reg file is parsed. If this is a problem for your system, I recommend the following:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PCCARD1]
"Flags"=dword:4
"Dll"="NOLOAD_<PCCard Driver Name>.dll"
Where <PCCard Driver Name> is the name that already exists in your registry. You could use any invalid driver name here, but this leaves a cookie crumb behind in case you want to undo the change.
Bruce |
Edited by - beitman on 27 Mar 2009 14:53:58 |
|
|
| |
Topic |
|
|
|
All Forums
Microsoft Windows CE
BitsyXb, Unidentified PCCard Adapter
Forum Locked
Send Topic to a Friend
Printer Friendly