2019-04-18 02:26 AM
Hi!
UM2399 User manual ST Teseo III binary image on page 276 says:
"If a specific configuration is required (see RF front-end reference manual for details about registers) it can be achieved by setting in the proper way the configuration parameters in the range from 140 to 189."
I would like to find an information about RF front-end registers of the device (8089F) to increase RF front-end attenuation by 10 dB. We substitute 8088 by 8089 which has LNA and amplification is too hi for our input signal. I find it out by adding external attenuator - works fine CNO is 40-45. Without it works bad i think because of signal clipping.
Thank you in advance!
2019-04-29 01:53 AM
Hi
We do not provide the complete RF front-end registers description but in this case:
Internal RN-LNA gain can be tuned setting some specific CDB-ID in the firmware configuration.
In your case you have to set:
CDB-140 @ 0x0A
CDB-141 @ 40
if it helps, you can also tests different vales for CDB-141 (140 is mandatory @ 0x0A)
Hope this helps
Regards
Francesco
2019-04-29 06:38 AM
Hi, Francesco!
Thank you for the reply! I suppose to check it soon.
By the way I suspect that there is no range check for parameter number. And I think that with RF front end registers we have the same picture.
With different SW versions you have various parameters qty in parameters groups. I need to read version number and adjust pars qty to prevent range problem. Otherwise changing par in one group with command can cause changing parameters in other group. Or it can brick the module. I tried to write wrong front-end register and it also caused death (no uart communicaton at all). Is there the way to bring it back to life? I tried powercycle, reset and so on - no effect.
Thank you one more time!
Regards
Ruslan
2019-04-29 06:46 AM
Hi
> Is there the way to bring it back to life? I tried powercycle, reset and so on - no effect.
with the standard booting configuration (SQI mode) You can
1. perform a Firmware-update operation (using an UPG file) with:
Or
2. reprogram the Teseo3-IC from zero (booting from UART and using a BOOT file)
Hope this helps
Regards
Francesco
2019-04-30 06:39 AM
Hi, Francesco!
Tried
CDB-140 @ 0x0A
CDB-141 @ 40
Results are partially successful. Module still alive :) . Signal value still the same :(
(with external 10dB attenuator). My understanding it should be less with additional attenuation with frontend register
evidences:
$PSTMVER,GNSSLIB_8.4.12.19_ARM*4E
$PSTMVER,OS20LIB_4.3.0_ARM*47
$PSTMVER,GPSAPP_2.6.0_ARM*18
$PSTMVER,BINIMG_4.5.10_ARM*2F
$PSTMVER,SWCFG_8104531d*30
$PSTMVER,STAGPSLIB_5.1.1_ARM*59
$PSTMVER,STA8090_622bc043*6F
$GPTXT,(C)2000-2011 ST Microelectronics*20
$GPTXT,Navia 8.4.12.19 196MHz FP for all 2012 m*1A
$PSTMSWCONFIG,1,0,11,00010a01050a0a0a0e0d0c0b0a090608070203630e070c04110c0155030100500f00000f0714000a0a28ffffffffffffffffffffffffffffffffffffffffffff*1D
$GNGSA,A,3,25,29,02,31,12,06,05,26,23,,,,1.2,0.6,1.0*21
$GNGSA,A,3,82,80,81,73,79,65,83,72,,,,,1.2,0.6,1.0*24
$GNGSV,5,1,17,82,74,220,46,25,69,164,47,80,67,217,45,29,67,237,46*64
$GNGSV,5,2,17,81,50,053,48,02,47,070,46,31,42,283,46,12,34,131,47*6F
$GNGSV,5,3,17,73,32,319,47,79,22,164,47,65,22,027,46,83,22,227,38*67
$GNGSV,5,4,17,06,16,042,41,05,16,112,47,72,14,342,46,26,10,301,41*64
$GNGSV,5,5,17,23,10,359,45,,,,,,,,,,,,*5F
$PSTMFEDATA,ff,ff,3c,6f,9d,78,b7,90,00,00,08,9a,a8,f0,3f,30,80,1a,28,e0,7f,30,40,3a,39*2B
For some reason reg 0x0a == 08? strange...
Also tried
CDB-140 @ 0x0A
CDB-141 @ 0x41
$PSTMVER,GNSSLIB_8.4.12.19_ARM*4E
$PSTMVER,OS20LIB_4.3.0_ARM*47
$PSTMVER,GPSAPP_2.6.0_ARM*18
$PSTMVER,BINIMG_4.5.10_ARM*2F
$PSTMVER,SWCFG_8104531d*30
$PSTMVER,STAGPSLIB_5.1.1_ARM*59
$PSTMVER,STA8090_622bc043*6F
$GPTXT,(C)2000-2011 ST Microelectronics*20
$GPTXT,Navia 8.4.12.19 196MHz FP for all 2012 m*1A
$PSTMSWCONFIG,1,0,11,00010a01050a0a0a0e0d0c0b0a090608070203630e070c04110c0155030100500f00000f0714000a0a41ffffffffffffffffffffffffffffffffffffffffffff*12
$GNGSA,A,3,25,29,02,31,12,06,05,23,26,,,,1.1,0.6,0.9*2A
$GNGSA,A,3,80,82,81,79,73,65,72,83,88,,,,1.1,0.6,0.9*2F
$GNGSV,5,1,18,82,72,220,47,25,71,167,44,80,69,223,45,29,65,237,46*6E
$GNGSV,5,2,18,81,52,053,49,02,48,071,46,31,42,286,46,12,36,130,48*64
$GNGSV,5,3,18,73,30,320,46,79,25,164,48,65,22,029,47,83,20,226,38*65
$GNGSV,5,4,18,06,17,042,46,72,16,344,46,05,14,113,46,23,09,000,45*60
$GNGSV,5,5,18,26,08,300,42,88,06,049,44,,,,,,,,*6C
$PSTMFEDATA,ff,ff,3c,6f,9d,78,b7,90,00,00,41,9a,a8,f0,3f,30,80,1a,28,e0,7f,30,40,31,33*7C
Here reg 0x0a == 0x41 as I think
The same signal level :(
Did not tried recovery yet.
Best regards
Ruslan
2019-05-08 01:23 AM
Hi, Francesco!
It seems that this:
>In your case you have to set:
>CDB-140 @ 0x0A
>CDB-141 @ 40
>if it helps, you can also tests different vales for CDB-141 (140 is mandatory @ 0x0A)
does not work. :(
I tried more values for CDB-141:
$PSTMFEDATA,ff,ff,3c,6f,9d,78,b7,90,00,00,08,9a,a8,f0,3f,30,80,1a,28,e0,7f,30,40,3a,39*2B
$PSTMFEDATA,ff,ff,3c,6f,9d,78,b7,90,00,00,00,9a,a8,f0,3f,30,80,1a,28,e0,7f,30,40,3d,39*26
$PSTMFEDATA,ff,ff,3c,6f,9d,78,b7,90,00,00,41,9a,a8,f0,3f,30,80,1a,28,e0,7f,30,40,31,33*7C
$PSTMFEDATA,ff,ff,3c,6f,9d,78,b7,90,00,00,57,9a,a8,f0,3f,30,80,1a,28,e0,7f,30,40,36,34*7B
$PSTMFEDATA,ff,ff,3c,6f,9d,78,b7,90,00,00,5f,9a,a8,f0,3f,30,80,1a,28,e0,7f,30,40,34,34*28
$PSTMFEDATA,ff,ff,3c,6f,9d,78,b7,90,00,00,5f,9a,a8,f0,3f,30,80,1a,28,e0,7f,30,40,34,34*28
$PSTMFEDATA,ff,ff,3c,6f,9d,78,b7,90,00,00,5f,9a,a8,f0,3f,30,80,1a,28,e0,7f,30,40,34,34*28
$PSTMFEDATA,ff,ff,3c,6f,9d,78,b7,90,00,00,1f,9a,a8,f0,3f,30,80,1a,28,e0,7f,30,40,3c,39*76
$PSTMFEDATA,ff,ff,3c,6f,9d,78,b7,90,00,00,40,9a,a8,f0,3f,30,80,1a,28,e0,7f,30,40,35,35*7F
$PSTMFEDATA,ff,ff,3c,6f,9d,78,b7,90,00,00,40,9a,a8,f0,3f,30,80,1a,28,e0,7f,30,40,35,34*7E
nothing changed. Signal value stil the same. Bit 0x20 can't be set. regs 0x17 and 0x18 changed without my intention - I changed just reg 0x0A.
Could you suggest other experiment?
This attenuation is little bit critical for us...
Thank you in advance
Ruslan