NXP and NEC based CEMs

CEM Release Note

Option nv, Gaston Geenslaan 14, 3001 Leuven - Belgium - Tel +32 16 317 411 - Fax +32 16 207 164

NXP and NEC based CEMs, CEM Release Note

About this document

Confidentiality
All data and information contained or disclosed by this document is confidential and
proprietary of Option NV, and all rights therein are Expressly reserved. By accepting
this document, the recipient agrees that this information is held in confidence and in
trust and will not be used, copied, reproduced in whole or in part, nor its contents
revealed in any manner to others without prior and written permission of Option NV.

Version History
Date

Version

Author

Revision

Remarks

Dec 5, 2007
Dec 7, 2007

V001draft
V002draft

P. Vandeneede
P. Vandeneede

Not reviewed
J. Schrijvers

Dec 12, 2007

V003ext

P. Vandeneede

J. Schrijvers,
P. Hardwick

Initial version
Ch. 5.2.1 :
limitation added
Revision

Author:
Creation Date:
Option
Confidential:

Version: v003ext
P. Vandeneede
Page:
Dec 12, 2007
1 of 14
This document is Option Confidential - it may not be duplicated, neither distributed
externally without prior and written permission of Option NV.

NXP and NEC based CEMs, CEM Release Note

Table of contents
1

INTRODUCTION ............................................................................................................3

GENERAL CARDBUS TO EXPRESS SLOT CONVERSION INFORMATION ....4

2.1
2.2

OPTIONS CEM IMPLEMENTION ..............................................................................5

3.1
3.2

DATA CONVERSION.....................................................................................................4
POWER REQUIREMENTS ..............................................................................................5
CEMS BASED ON THE NXP USB HOST CONTROLLER. ...............................................6
CEM BASED ON NEC HOST CONTROLLER. ................................................................7

COMPATIBILITY...........................................................................................................8
4.1
DIFFERENCE BETWEEN EXPRESS CARDS ON CEM DETECTION LEVEL .......................8
4.1.1
Group 1: Fuji-ex 2.0 Etna-ex 1.0 .....................................................................8
4.1.2
Group 2: Fuji-Ex 3.0-3.1 Etna 2.0 4.2 .............................................................8
4.1.3
Group 3: Fuji-Ex 3.2 Etna-Ex 4.3....................................................................9
4.2
COMPATIBILITY WITH OLD HARDWARE AND FW RELEASES ......................................9

LIMITATIONS AND KNOWN ISSUES .....................................................................10

5.1
THROUGHPUT LIMITATIONS ......................................................................................10
5.2
KNOWN ISSUES .........................................................................................................11
5.2.1
Common issues.................................................................................................11
5.2.2
NXP-CEM ........................................................................................................12
5.2.3
NEC-CEM ........................................................................................................13

Author:
Creation Date:
Option
Confidential:

Version: v003ext
P. Vandeneede
Page:
Dec 12, 2007
2 of 14
This document is Option Confidential - it may not be duplicated, neither distributed
externally without prior and written permission of Option NV.

NXP and NEC based CEMs, CEM Release Note

INTRODUCTION

CEM is the engineering name of the Option device that converts a 32-bit Cardbus
slot of a laptop to an Express Card slot format. This device is made to allow our
customers to approve and supply one device that will serve both technologies while
the market transitions to universal Express Card slot availability.
This document has the intention to explain the working principles of the Option CEM,
the different types that exist and the possible limitation which can occur when using
an Express Card together with a CEM.

Figure 1: Picture of an Option CEM.

Author:
Creation Date:
Option
Confidential:

Version: v003ext
P. Vandeneede
Page:
Dec 12, 2007
3 of 14
This document is Option Confidential - it may not be duplicated, neither distributed
externally without prior and written permission of Option NV.

NXP and NEC based CEMs, CEM Release Note

GENERAL CARDBUS TO EXPRESS SLOT CONVERSION

INFORMATION

A device that converts the Cardbus format to Express slot format can be split up in 2
main functional blocks. It has to convert the data of the 32-bit Cardbus to the Express
Card slot data format and it has to adapt the power requirements from the Cardbus to
the Express Card slot requirements.

Figure 2: CEM Block diagram.

2.1

Data conversion

The data format has to be converted from the 32-bit Cardbus format to the Express
slot format and vice versa. This is done with a USB host controller as the Express
slot uses the USB data format. A number of USB host controllers do exist with all
their pros and cons. So far Option has used 2 different USB host controllers in their
CEM devices (more on this in chapter 3).
The Qualcomm chipset used in the Option Express Cards delivers and receives data
in USB 2.0 Full speed format. According to the USB specs this should give a
maximum bandwidth of 12 Mbit/s. This USB data is sent directly to the Express slot
connector. In other words, when the Express Card is used with a CEM then the CEM
receives this USB 2.0 data format and converts it to the 32-bit Cardbus format.

Author:
Creation Date:
Option
Confidential:

Version: v003ext
P. Vandeneede
Page:
Dec 12, 2007
4 of 14
This document is Option Confidential - it may not be duplicated, neither distributed
externally without prior and written permission of Option NV.

NXP and NEC based CEMs, CEM Release Note

2.2

Power requirements

The Express Card slot contains a 3.3V power rail and a 1.5V power rail. The problem
is that the 32-bit Cardbus only has a 3.3V power rail so the CEM has to make a 1.5V
power rail by itself.
Current consumption is another power requirement that has to be controlled. The
Express slot is able to deliver 1.3A on the 3.3V power rail while the 32bit Cardbus
can only deliver 1A on the 3.3V power rail. Therefore a current limiter has to be used
to make sure that no more then 1A is taken from the 32-bit Cardbus.
Next is a list of Power requirements of both card slots:
Express Card slot

3.3V power rail available

This power rail can deliver 1.3A
1.5V power rail available

32-Bit Cardbus

3,3V power rail available

This power rail can only deliver 1A
No 1.5V power rail

OPTIONS CEM IMPLEMENTION

Currently Option has 2 different CEM versions. One version based on the NXP USB
host controller and a second version based on the NEC USB host controller.
Differences between the 2 USB host controllers:
NXP USB host controller

Very good throughput

Some instability problems with W2000 and Vista.
Instability issues reported on MAC

NEC USB host controller

Author:
Creation Date:
Option
Confidential:

Throughput is a bit less then with NXP

Good stability on W2000, XP and Vista.
Minor problems seen on MAC OS.

Version: v003ext
P. Vandeneede
Page:
Dec 12, 2007
5 of 14
This document is Option Confidential - it may not be duplicated, neither distributed
externally without prior and written permission of Option NV.

NXP and NEC based CEMs, CEM Release Note

3.1

CEMs based on the NXP USB host controller.

CEMs based on the NXP host controller have the following properties:

Based on NXP USB host controller.

Has a built in 3.3V to 3.6V step-up converter. This is done to increase system
stability.
Has a built in 1A current limiter, which can be controlled from the Express
Card.
Has large buffer capacitors that can deliver the current to support the Express
Card while the current limiter is active.
In the device manager of the Windows Operating System the NXP based
CEM will be seen as 2 separate devices, a Standard Enhanced PCI to USB
host controller and a Standard OpenHCD USB host controller. These devices
can be assigned names by the driver. Refer to the driver release note to find
out the exact name used in a specific driver version. (In the example below
its renamed to Mobile Bus Converter.)

Figure 3: NXP CEM view in device manager.

Author:
Creation Date:
Option
Confidential:

Version: v003ext
P. Vandeneede
Page:
Dec 12, 2007
6 of 14
This document is Option Confidential - it may not be duplicated, neither distributed
externally without prior and written permission of Option NV.

NXP and NEC based CEMs, CEM Release Note

3.2

CEMs based on NEC host controller.

CEMs based on the NEC host controller have the following properties:

Based on NEC USB host controller.

Has no build in 3.3V to 3.6V step up converter. This step up conversion is
done on our latest Express Card hardware
Has no build in current limiter. Current limiting has to be done on the Express
Card.
No buffer capacitors. The current has to be delivered by the capacitors on the
Express Card.
In the device manager of the Windows Operating System the NEC based
CEM will be seen as 2 separate devices, a Standard Enhanced PCI to USB
host controller and a NEC PCI to USB host controller. The driver cant change
these names.

Figure 4: NEC CEM view in device manager.

Author:
Creation Date:
Option
Confidential:

Version: v003ext
P. Vandeneede
Page:
Dec 12, 2007
7 of 14
This document is Option Confidential - it may not be duplicated, neither distributed
externally without prior and written permission of Option NV.

NXP and NEC based CEMs, CEM Release Note

COMPATIBILITY

The firmware on the Express Card has the ability to detect if its used with a CEM
and with which type of CEM (NXP based CEM or NEC based CEM). This is
important, as the Express Card has to know if the card is used with a CEM or not. If
an NXP based CEM is used the firmware has to enable the 1A current limiter to
protect the 32-bit Cardbus for over current. In case of the NEC based CEM the
firmware knows that this CEM has no current limiter on board and the firmware will
decide to enable the current limiter of the Express Card itself. This current limiter is
only available on the latest hardware.
As you can see CEM detection is dependant on the hardware and firmware used.
The next chapters give an overview of the hardware and firmware compatibility.
4.1

Difference between Express Cards on CEM detection level

Express Cards have the ability to detect if they are used together with a CEM or not.
According to the CEM version the Express Card detects the current limiter will be
enabled or not.
Different hardware versions have different abilities to detect the CEM version. The
Express Card hardware versions can be split up in three groups of CEM detection
ability.

Group 1
Group 2
Group 3

4.1.1

4.1.2

Author:
Creation Date:
Option
Confidential:

Fuji-Ex hardware version

2.0
3.0 3.1
3.2 and later

Etna-Ex hardware version

1.0
2.0-4.2
4.3 and later

Group 1: Fuji-ex 2.0 Etna-ex 1.0

No CEM detection! These Express Cards cant detect if they are used
together with a CEM or not.
By default the current limiter for all CEM versions is bypassed! As these cards
cant detect the use of a CEM, the current limiter of the CEM will always be
bypassed.
Current limiter on the Express Card is 1.3A

Group 2: Fuji-Ex 3.0-3.1 Etna 2.0 4.2

NXP CEM detection but cant detect NEC CEM
When used with a NEC CEM it will assume that its used without a CEM.
Current limiter on the Express Card is 1.3A

Version: v003ext
P. Vandeneede
Page:
Dec 12, 2007
8 of 14
This document is Option Confidential - it may not be duplicated, neither distributed
externally without prior and written permission of Option NV.

NXP and NEC based CEMs, CEM Release Note

4.1.3

4.2

Group 3: Fuji-Ex 3.2 Etna-Ex 4.3

CEM detection, can detect the difference between the NXP CEM and the
NEC CEM.
Express Card can be set to 1.0A current limiter, 1.3A current limiter or the
current limiter can be bypassed.
Compatibility with old hardware and FW releases

CEM type used

NXP-CEM

Group 1: Fuji-Ex 2.0/Etna-Ex1.0

Cards are not able to detect CEM
CEM current limiter = bypassed
Card current limiter = 1,3A

Remarks
No current protection!
In some rare conditions
the card could consume
more power then
allowed.

NEC-CEM

Cards are not able to detect CEM

CEM has no current limiter
Card current limiter = 1,3A

No CEM

Card current limiter = 1,3 A

OK

Group 2: Fuji-Ex3.0-3.1/Etna-Ex2.0-4.2

Remarks

CEM type used?

NXP-CEM

Will detect CEM

CEM current limiter = 1A
Card current limiter = bypassed

NEC-CEM

Does not detect CEM

CEM has no current limiter
Card current limiter =1,3A

No current protection!
In some rare conditions
the card could consume
more power then
allowed.

No CEM

Card current limiter = 1,3 A

OK

Group 3: Fuji-Ex3.2/ Etna-ex4.3

Remarks

CEM type used?

NXP-CEM

Will detect CEM

CEM current limiter = Bypass
Card current limiter = 1A

NEC-CEM

Will detect CEM (*)

CEM has no current limiter
Card current limiter = 1A

No CEM

Card current limiter = 1,3 A

OK

OK

(*)Only from the next firmware versions onwards the NEC CEM will be
detected
Card type
Fuji-Ex
Etna-Ex

Author:
Creation Date:
Option
Confidential:

FW version
2.4.0
2.8.0

Version: v003ext
P. Vandeneede
Page:
Dec 12, 2007
9 of 14
This document is Option Confidential - it may not be duplicated, neither distributed
externally without prior and written permission of Option NV.

NXP and NEC based CEMs, CEM Release Note

LIMITATIONS AND KNOWN ISSUES

5.1

Throughput limitations

The different versions of CEM have a different behavior in throughput. The used USB
host controller does slow down the throughput and the NEC USB host controller has
more impact on the throughput compared to the NXP USB host controller.
Below a chart is shown that indicates the maximum throughput figures that can be
expected per USB host controller, per used driver and per connection type.

Express card throughput per CEM type

8
7
6

Mbit/s

5
4
3
2
1
0
No CEM

NXP CEM

4.0.0.18 Ndis

4.0.0.18 dial up

3.3.1.3 dial up

NEC CEM
3.2.1.3 Ndis

Figure 5: CEM throughput figures.

Author:
Creation Date:
Option
Confidential:

Version: v003ext
P. Vandeneede
Page:
Dec 12, 2007
10 of 14
This document is Option Confidential - it may not be duplicated, neither distributed
externally without prior and written permission of Option NV.

NXP and NEC based CEMs, CEM Release Note

5.2 Known issues

Each USB host controller his limitations, for that the list of limitations is split up per
CEM type.
5.2.1

Common issues

Limitation 1:
o Description: An Unsafe Remove of an Express Card product with CEM
is not always allowed by Windows. A user should always request the
system for a Safe Removal and wait on the system approval before
removing the product.
Depending on the operating system used, the following problems will
be observed after an Unsafe removal:

Windows 2000: Always, a BSOD (Blue Screen Of Death).

Windows XP (32 and 64 bit): Very rarely, a BSOD.

Windows Vista (32 and 64 bit): Sometimes, a BSOD or other
problems.
See http://support.microsoft.com/?id=933938.
o Analysis: Windows requires removable devices to be safely removed.
A user is simply not allowed to do a surprise removal.
A surprise removal of a Cardbus data card (CEM) actually means to
Windows that a USB Host Controller got removed from the PCI bus.
This can cause BSODs. The frequency of BSODs depends on the
Windows version used.
o Workaround: Before removing a product, request a Safe Removal
from the system and wait for its approval before removing.

Limitation 2:
o Description: When performing a Safe Remove of an Express Card
product with CEM (both NXP and NEC) in Windows, you must remove
both the CEM and Express Card product together. In case you only
remove the Express Card product and not the CEM, you are not able
to use the Express Card product after re-inserting it.
o Analysis: When requesting a Safe Remove, it is actually the USB host
controller in the CEM that is requested to be removed. The drivers for
all devices (including Express Card product devices) are unloaded.
When removing and re-inserting the Fuji-Ex/Etna-Ex, their drivers will
not load because the USB host controller in the CEM has still its
drivers unloaded. Only when re-inserting the CEM, its drivers will be
loaded after they were unloaded before through a Safe Remove.
o Workaround: Always remove the Fuji-Ex/Etna-Ex together with the
CEM.

Author:
Creation Date:
Option
Confidential:

Version: v003ext
P. Vandeneede
Page:
Dec 12, 2007
11 of 14
This document is Option Confidential - it may not be duplicated, neither distributed
externally without prior and written permission of Option NV.

NXP and NEC based CEMs, CEM Release Note

5.2.2

NXP-CEM

Limitation 1:
o Description: When inserting an Express Card product together with an
NXP-CEM for the first time on a Windows 2000 system, i.e. before its
drivers are installed, you must first insert the NXP-CEM without
Express Card product. When all devices of the NXP-CEM have their
drivers installed, the Express Card product can be inserted in the
NXP-CEM. If one would insert the NXP-CEM and Express Card
product together the first time, the drivers will not be installed properly
and the product will not be usable afterwards.
After the drivers are installed, the NXP-CEM can be inserted together
with the Express Card product without problems.
On Windows XP and Windows Vista systems, the NXP-CEM can be
inserted together with the Express Card product for the first time
without problems.
o Analysis: Windows 2000 has problems during the installation of the
NXP USB Host Controller inside the CEM when a USB device
(Express Card product) is connected to one of its USB ports.
o Workaround: Insert the NXP-CEM without Express Card product. After
the NXP-CEM drivers are installed, insert the Express Card product.

Limitation 2:
o Description: When the drivers for an Express Card together with an
NXP-CEM are loaded (during installation, insertion, Resume) on a
Windows system, it can happen that the drivers will not be loaded
properly. The severity of this problem depends on the operating
system used:

Windows 2000: the problem occurs regularly

Window XP (32 and 64 bit): the problem occurs very rarely

Windows Vista (32 and 64 bit): the problem occurs from time to
time.
o Analysis: The interaction between W2000 and the NXP USB host
controller is not optimal. Other USB host controllers dont show this
behavior.
o Workaround: None.

Limitation 3:
o Description: On MAC PowerBook systems, an Express Card product
used with an NXP CEM could show some instability problem.
o Analysis: The interaction between the NXP USB host controllers and
MAC is not optimal.
o Workaround: None

Author:
Creation Date:
Option
Confidential:

Version: v003ext
P. Vandeneede
Page:
Dec 12, 2007
12 of 14
This document is Option Confidential - it may not be duplicated, neither distributed
externally without prior and written permission of Option NV.

NXP and NEC based CEMs, CEM Release Note

5.2.3

Author:
Creation Date:
Option
Confidential:

NEC-CEM
Limitation 1:
o Description: On MAC PowerBook systems, an error message may
occur when an Express Card product is used with a NEC-CEM after
the Powerbook returns from sleep mode.
o Analysis: NEC USB host controllers work as expected on MAC but
occasionally after returning from sleep mode the drivers are not
loaded as they should.
o Workaround: Remove and re-insert the NEC-CEM together with the
Express Card product.

Version: v003ext
P. Vandeneede
Page:
Dec 12, 2007
13 of 14
This document is Option Confidential - it may not be duplicated, neither distributed
externally without prior and written permission of Option NV.

NXP and NEC based CEMs, CEM Release Note

References
Ref
1

Author:
Creation Date:
Option
Confidential:

Document
FUJ-SPQ-UM-Fuji_Quick_Install_Manual-V02-F1.pdf

Option

Version: v003ext
P. Vandeneede
Page:
Dec 12, 2007
14 of 14
This document is Option Confidential - it may not be duplicated, neither distributed
externally without prior and written permission of Option NV.