We've built a design based around the CC1101 and are powering it with 2.1V and transmitting a CW tone at 395 MHz. Our issue is that a large subset of PATABLE values produce the same final output power, whereas you would expect the output power to vary based on different PATABLE values. It seems that PATABLE setting that start with 0x8 or 0x6 function correctly and allow us to adjust the output power, but the other PATABLE settings do not (with the exception of 0x00).
Here are some examples of our measured output powers vs PATABLE:
|
PATABLE Setting |
Measured Output Power |
|
0x00 |
-63 dBm |
|
0x01 |
-38.4 dBm |
|
0x06 |
-38.4 dBm |
|
0x1d |
-38.4 dBm |
|
0x30 |
-38.4 dBm |
|
0x34 |
-38.4 dBm |
|
0x60 |
3.5 dBm |
|
0x62 |
2.1 dBm |
|
0x6a |
-3 dBm |
|
0x6f |
-11.9 dBm |
|
0x85 |
7.6 dBm |
|
0x86 |
6.9 dBm |
|
0x8b |
2.7 dBm |
|
0x8e |
-.8 dBm |
|
0x8f |
-7.5 dBm |
I understand that PATABLE isn't monotonic and somewhat complicated in how it is mapped to output power, but for all values that don't start with 0x8 or 0x6, we're seeing an output power of -38.4 dBm (other than 0x00).
Using the same code to configure the CC1101 dev kit, which is powered by a higher voltage, causes the PATABLE setting to control the output power as you would expect (there is no -38.4 dBm "dead zone").
Is it possible that certain PATABLE values aren't compatible with 2.1V?
