Firmware Release Notes - BTM510/BTM511
Contents
1. Phone Test role of BTM51x Result Comment HTC Touchpro 2 Inquiry Pairing no serious issues windows mobile Era HFP HF no serious issues HSP HS incoming connection accepted by phone but no audio is initiated by phone when AT HSB was issued at BTM DUN DT no issues Sony Ericsson K800i Inquiry Pairing no issues ere HFP HF no issues HSP HS not supported by phone DUN DT no issues Nokia E71 BT 2 0 Inquiry Pairing BTM can be found by phone pairing can be initiated by phone La rd Firmware Release Notes _TECHNOLOGIES JD BTM510 BTM511 VO Doc No BTM510 511 v18 1 3 0 Page 7 of 30 HFP HF connection from BTM is accepted but released immediately by the phone HSP HS Not tested DUN DT Not tested La rd Firmware Release Notes _TECHNOLOGIES JD BTM510 BTM511 TOO Doc No BTM510 511 v18 1 3 0 Page 8 of 30 2 Firmware Version 14 1 1 1 engineering firmware 2 1 New Features compared to v14 1 1 0 e support for simultaneous A2DP HFP added e support for extended inquiry response EIR data enhanced enabling up to 240 Bytes of EIR data 2 2 New AT commands e AT APU suspend A2DP streaming but retain A2DP link e AT APR resume A2DP streaming e AT BTE clear EIR data from baseband e AT BTE query EIR data from baseband e AT BTE lt data gt write EIR data to RAM buffer and baseband e AT BTE delete EIR data from RAM buf2. La rd Firmware Release Notes BTM510 BTM511 TECHNOLOGIES gt Doc No BTM510 511 v18 1 3 0 Issue No 010 Date 30 Sep 11 Page i Author Sebastian Schillack Firmware Release Notes BTM510 BTM511 Prepared by Sebastian Schillack Authorised by Andrew Dobbing O 2011 Laird Technologies This document is issued by Laird Technologies Limited in confidence and is not to be reproduced in whole or in part without the prior written permission of Laird Technologies The information contained herein is the property of Laird Technologies and is to be used only for the purpose for which it is submitted and is not to be released in whole or in part without the prior written permission of Laird Technologies Change History fooe vente EIN pos wre E AN pos wre E poo wanes E aa Content 1 Firmware Version 14 1 1 0 4 Pedy A A A 4 1 2 Changes in AT command set compared to 14 0 0 11 0oooccoccccccnccccnnccanaccncnnncnonnnnannnnnnos 4 1 3 Bugs fixed compared to 14 00 Mes aaa 4 LE NOW ISSO iio 5 1 5 Interoperability tests with mobile phones o oooooocccnccccconoccccccnnnononananannnccnnnnnnnnanannncnnnos 6 2 Firmware Version 14 1 1 1 engineering firmware 8 2 1 New Features compared to v14 1 1 0 aii ee 8 2 2 New AT commands cerei ireira a ar aa rada 8 2 3 NewoSRegiSters iris Aa 8 2 4 New unsolicited messages ccooocoooccconcccconononononononnncnnnnnnnnnonnnnnnnnnnnnnnnnnnnnnrnnnnnnnnnnnnncnnnnnnn 9
3. e Deprecated undocumented usage of LED1 to indicate audio related states e g loopback Ref 1 24 e Module was not discoverable after releasing an SPP connection ATH while S512 4 Ref 1 25 This issue has been fixed 2 10 Known Issues e thas been observed that an A2DP source with an active SCO connection HFG will reject an incoming A2DP connection request if A2DP is not allowed to override SCO S355 In the same circumstance the A2DP source can initiate an outgoing A2DP connection but it will not initiate the start of the A2DP stream This is not really an issue but the different behaviour towards incoming and outgoing connections might not be expected as this e It has been observed that the audio related USMs for HFP and HSP e g HF AU1 HFG AU1 HS AU1 HSG AU1 can appear as AUDIO ON SCO or AUDIO ON eSCO This not intended and can happen if SPP is enabled along with HFP or HSP Workaround disable SPP in S102 if not needed Ref 1 26 La rd Firmware Release Notes _TECHNOLOGIES JD BTM510 BTM511 TOO Doc No BTM510 511 v18 1 3 0 Page 11 of 30 3 Firmware Version 14 1 1 2 engineering firmware 3 1 New Features compared to v14 1 1 1 e APTX codec for A2DP source fully and sink demo supported o analogue input and analogue output mode o decoder demo for 5 minutes encoder fully functional o See S Register 307 e Configure UART for high throughput or low latency
4. in command and connected mode of SPP and subsequently issuing ATO ERROR 04 was returned which was preventing the return to data and connected mode SPP This issue has been fixed Ref 2 26 La rd Firmware Release Notes _TECHNOLOGIES JD BTM510 BTM511 TOO Doc No BTM510 511 v18 1 3 0 Page 21 of 30 6 Firmware Version 18 1 2 2 engineering firmware This engineering release was a preview version for 18 1 2 3 and was not distributed widely Version 18 1 2 2 is identical with 18 1 2 3 from the feature s prospective However 18 1 2 2 contains a bug which blocks incoming audio in a SCO link if CVC is enabled This issue is fixed in v18 1 2 3 La rd Firmware Release Notes _TECHNOLOGIES JD BTM510 BTM511 TO Doc No BTM510 511 v18 1 3 0 Page 22 of 30 7 Firmware Version 18 1 2 3 engineering firmware 7 1 New Features compared to v14 1 2 1 e Clear Voice Capture CVC support configurable DSP algorithms for noise reduction and echo cancellation NREC provided by CSR o 5 generation of CVC o Applies to the Headset Hands free unit of a SCO connections e g HFP o HS1mic HS2mic HF1mic selectable o See also CVC on BTM5xx application note provided by Laird Technologies e New bluestack firmware o New version 23i o Build number 6530 ATI1 7 2 New AT commands e AT HFZ Disable NR EC in HFG AT NREC 0 sent on SLC Feature 14 4 24 of HFP1 5 spec only allowed if both
5. o See S Register 544 3 2 New ATI commands e ATI26 query active A2dp codec o Response if S333 1 verbose mode NONE SBC APTX o Response if S333 0 non verbose mode 0 1 2 whereby O None 1 SBC 2 APTX o Note S333 has been associated with HFP Hands free profile so far but now becomes more to a global verbose enable disable register e ATI27 query current scan state o 0 not discoverable and not connectable not scanning o 1 discoverable inquiry scanning o 2 connectable page scanning o 3 discoverable and connectable inquiry and page scanning 3 3 New S Registers e 307 optional A2DP codec enable 0 1 default 0 o 0 no optional codec o 1 aptX o Notes 1 aptX must be enabled on both ends If aptX is not enabled on both ends then SBC will be selected automatically on an A2DP connection Check with ATI26 which codec is actually in use 2 S307 is queried at boot time So after writing a new value issue AT amp W and ATZ for the new value to become effective 3 SBC is the mandatory codec and therefore not in the optional codec list e 308 Auto BTX on A2DP connection 0 3 default 3 La rd Firmware Release Notes _TECHNOLOGIES JD BTM510 BTM511 oc No Bs 10167 8130 Page 12 0F 30 o 0 do not change discoverable and connectable state when entering or exiting an A2DP connection o 1 make the module not discoverable and not connectable when
6. 0x38 Ref 0 6 e ATS690 has reported 215 215 This issue has been fixed Ref 0 7 e AT GIU and AT GOU went up to 23 but maximum value is 22 This is fixed now Ref 0 8 1 4 Known Issues e GPIOs not accessible by AT commands Ref 1 5 e In some cases General Bonding automated pairing during connection setup with legacy devices BT2 0 or earlier does not work It did not work when tested against a BISM2 However the issue did not appear when tested against a BTM510 that was converted to BT2 0 or when tested against a BTM430 BT2 0 This implies that this issue is likely to be caused by the remote device Ref 1 1 Workaround use AT BTW lt BdAdar gt to initiate dedicated bonding prior to connection establishment with a legacy devices e 324 is ignored SSP timeout is fixed to about 30 seconds probably error in CSR library Ref 1 3 e When the link key for a device is existing locally AT BTT or AT BTW but the link key is missing in the remote device e g it was deleted there creating a connection AT SPD lt BdAddr gt will result in NO CARRIER rather than new pairing This issue is caused by the underlying Bluetooth stack and can only be resolved with a future update The first number of the firmware version 14 here indicates the Bluetooth stack version in use So in every firmware version beginning with 14 this issue will be present Ref1 7 Workaround a recommended use AT BTW lt BdAddr gt to ini
7. 1 enable default e S314 A2DP audio interface select o O internal default 1 I2S master 2 12S slave e 315 SCO audio interface select La rd Firmware Release Notes _TECHNOLOGIES JD BTM510 BTM511 po DocNo Bs 10167 8130 Page 15 0F 30 o Osinternal default 1 I2S master 2 12S slave e 316 external codec sampling frequency capabilities for A2DP o Referenced only if S314 gt 0 and only for A2DP links o Register values values can be added for all sampling frequencies supported 1 48kHz 2 44 1kHz 4 32 kHz 8 24kHz 16 22 05kHZ 32 16kHz not supported by SBC nor APTX value is ignored e 650 GPIO pin state mask o 0 configuration field enabled 1 pin state mask for S651 S658 e 651 S658 GPIO configuration registers for details see below GPIO Configuration e 669 GPIO input strong bias enable bitmask o 1 enable strong internal pull up down if GPIO is an input o 0 enable weak internal pull up down if GPIO is an input e 670 read write pin states of all GPIOs in one step e 411 short press duration in ms granularity 200ms e 412 medium press duration in ms added to value of S411 granularity 500 ms e S413 long press duration ms added to values of S411 S412 granularity 500ms 4 5 New asynchronous messages e Current sampling frequency FSddddd lt interface gt whereby ddddd sampling frequency in Hz 4 or 5 digits lt interface gt INT internal codec 125_M
8. 12S master I2S_S 12S slave FS message can be disabled by S309 or S504 4 6 New Error Codes e 79 writing to modem control line is not permitted by GPIO S register e 80 attempting to write the pin state of a GPIO that is configured as input e 81 Maximum size of EIR data exceeded ATI29 4 7 General information All Features described for this firmware version v14 1 2 0 have been tested by automated regression tests to a reasonable level A number of bugs have been found and were fixed before releasing this firmware 4 8 How to use 125 125 signals are mapped to the PCM pins of BTM51x as outlined in this table 125 Signal BTM51x Signal BTM51x Mini devkit Comment name name module pin PCM Laird Firmware Release Notes TECHNOLOGIES JD BTM510 BTM511 Po Do No BTM510 511 v18 1 3 0 Page 16 of 30 no header J5 SD_IN PCM_IN 3 5 125 Serial data in SD_OUT PCM_OUT 4 7 125 Serial data out WS PCM_SYNC 5 6 125 Word select right left ch SCK PCM_CLK 6 4 128 clock GND1 2 3 4 9 22 13 47 10 GND Connect an 12S slave source as outlined in the following block diagram The SD_OUT connection is not needed for the example below 12S slave device SD_IN WS SCK PCM_IN BTM5xx 12S master A2DP source PCM_SYNC PCM_OUT analogue audio Stereo Audio Out BTM5xx A2DP sink A third BTM5xx can be utilised as an I2S s
9. 20 ING WATS and 9 20 NOW Error Codes iaa 9 24 1 108 2 40 2s eee Ro RD E en nt oe E a e e 9 2 8 General MOM aa 9 2 9 Bugs fixed compared to 14 1 Dioni sid 10 2 10 O 10 3 Firmware Version 14 1 1 2 engineering firmware 11 3 1 New Features compared to v14 1 1 1 dd ie Se eee ae 11 3 2 New ATi COMMBANGS sft da iaa 11 3 3 New S Registers cae AA AAA AA 11 AA tenn ryeecacs ets ee ew rece sack eetede sn veeceesGtecesnvere ecc Tanara e eaei 12 35 GONNA oa 12 3 6 How toenable APTA aaa 12 3 7 Bugs fixed compared to 14 1 1D ceecsde ac de odes oc Ad seacye tage eeauadapeege eeegesng Saute te aehly 13 358 A O OO 13 4 Firmware Version 14 1 2 0 production firmware 14 4 1 New Features compared to V14 1 1 2 ooooooococccccnncccnonocononcnonnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnns 14 4 2 New and enhanced ATOM 14 43 NewATicommandS ii E EREE 14 4 4 New S Registers coooooomcccccnnnnnnccnnnoncconcccnnnnnnnnnnncnnnnnnnnnnnnnnn cnn nn cnn nn nnnnnnn nen r nn nen nn rra ner nnnnnn 14 4 5 New asynchronous MESSAGES ececconcrocininnnoncec troceado reiteran ec ecedeieesavendveneudeedeskeneed 15 4 6 NOW Error Odesa te E RE A IE 15 4 7 CORSA MOMMANON ss ura a a a a i a i ieboes 15 4 8 How t use IS a 15 BO CAPO COMU a 17 4 10 Bugs fixed compared 10 141 iii a 18 4 11 Known SSUAS a aaa ia alo 18 5 Firmware Version 14 1 2 1 engineering firmware 20 5 General informal a ee ey 20 N P Es so 5 2 New AT COMMANAS ccooccccn
10. 3 0 Page 19 0F 30 player recorder no codec the I2S signals are sufficient and no HF synchronisation is required Ref 2 3 e Auto connection at boot time AT BTR only applies to SPP Ref 2 4 1 4 e 324 is ignored SSP timeout is fixed to about 30 seconds probably error in CSR library Ref 2 5 1 3 e When the link key for a device is existing locally AT BTT or AT BTW but the link key is missing in the remote device e g it was deleted there creating a connection AT SPD lt BdAddr gt will result in NO CARRIER rather than new pairing This issue is caused by the underlying Bluetooth stack and can only be resolved with a future update The first number of the firmware version 14 here indicates the Bluetooth stack version in use So in every firmware version beginning with 14 this issue will be present Ref 2 6 1 7 Workaround a recommended use AT BTW lt BdAddr gt to initiate new pairing to generate new link keys on both devices Workaround b the link key for the remote device can be deleted from the trusted device list AT BTD lt BdAddr gt or from cache AT BTDW A new connection attempt AT SPD lt BdAddr gt should initiate new pairing automatically However this might not work with some legacy BT2 0 and earlier devices Hence workaround a is recommended e thas been observed that the audio related USMs for HFP and HSP e g HF AU1 HFG AU1 HS AU1 HSG AU1 can appear
11. HF and HFG have declared NREC support in their HF HFG supported features see S581 HF and S596 HFG e AT HFF Query local HF and remote HFG supported features SF HFP SLC is required Response lt HF_SF gt lt HFG_SF gt 7 3 New ATI commands e ATI32 query CVC license key e ATI35 query list of available CVC images with SYSID security status technical name and SDK e ATI36 status of boot time CVC license check applies if S318 gt 0 e ATI57 query profile flags of current connections same format as S register 102 e ATI58 query number of current connections sum of ATI60 ATI67 e ATI59 returns 1 if a pre set PIN code by AT BTK is available returns 0 otherwise the PIN code itself is not displayed for security reasons 7 4 New S Registers e 318 Select CVC DSP image o 0 disable CVC DSP not used in a SCO link o 1 Headset 1 microphone hs462 SYSID B00A La rd Firmware Release Notes _TECHNOLOGIES JD BTM510 BTM511 AAA Doc No BTM510 511 v18 1 3 0 Page 23 of 30 o 2 Headset 2 microphones hs542 SYSID B107 o 3 Hands free 1 microphone hf441 SYSID A006 7 5 New asynchronous messages e When a CVC image is loaded on entering a SCO audio link CVCID xxxx whereby xxxx Sysld 4 hex digits e When the security check for a CVC image has failed invalid or no license key HF AU2 or HS AU2 ERROR 83 will be returned as well In this case the
12. SCO link will remain but no audio can be heard due to failed security check Make sure that a valid CVC license key exists and S318 contains the correct setting 7 6 CVC Limitations e Only the BCO5 on board codec is supported External audio interfaces like PCM I2S are not supported with this release e CVC only applies to SCO connections of the HF or HS instance CVC does not apply to the audio gateway role of neither HFP HFG nor HSP HSG e A license key is required for the CVC images For development purposes CSR provide free trial license keys This firmware provides all necessary means in order to allow CVC trial development and license key management in conjunction with CSR tools The application note CVC on BTM5xx describes the necessary details 7 7 New Error Codes e 82 no CVC license key stored or more than 5 words invalid length ATI32 e 83 CVC security failed on loading CVC image for a SCO connection e 84 85 86 87 f w internal CVC error codes should not occur with released firmware e 88 CVC SYSID request timeout can occur on ATI35 if UART baud rate is too low e 89 HF request to disable NREC in HFG failed because NREC feature is not supported by both ends Support for both ends can be checked with AT HFF NREC mask for HF 1 NREC mask for HFG 2 e 90 CVC boot time check failed occurs if S318 gt 0 at boot time and selected CVC image does not have a valid license key e 91 HF ERROR was rece
13. as AUDIO ON SCO or AUDIO ON eSCO This not intended and can happen if SPP is enabled along with HFP or HSP Workaround disable SPP in S102 if not needed Ref 2 7 1 26 e ATH and ATH111E do not work with HS instance Headset unit of HSP workaround use AT HSH instead Ref 2 10 e HFG call records There are currently no AT command available for the following purposes o Clear a waiting call Ref 2 11 1 16 o Make a held call active Ref 2 12 1 17 o Clear a held call Ref 2 13 1 18 e HFG AT HFGE lt ext_err_code gt an issue with extended error codes has been observed AT HFGE lt ext_err_code gt does not work as expected Workaround do not use extended error codes but simple error messages e AT HFGE without parameter Ref 2 14 1 10 e EIR after repeatedly issuing AT BTE or AT BTEW provided data is stored in the RAM and persistent buffer the commands stop working or only display a part of the buffered data lt was not possible to manually reproduce this issue consistently Ref 2 20 La rd Firmware Release Notes _TECHNOLOGIES JD BTM510 BTM511 TOO Doc No BTM510 511 v18 1 3 0 Page 20 of 30 5 Firmware Version 14 1 2 1 engineering firmware 5 1 General information This firmware is an engineering release for a particular project It contains a new feature for a HF to request creation of DTMF tones from a HFG e g mobile phone as well as a couple of bug fixes T
14. as well as fixed bugs to a reasonable level This aims to make sure that all AT commands and features function as described in the BTM51x user manual However given the huge amount of possible combinations of Bluetooth profiles roles and S Register settings there may be untested use cases left This firmware is qualified for production The BTM51x user manual is updated with this release as well 10 3 Bugs fixed compared to 18 1 2 5 e ATI57 response for AVRCP flag was wrong 0x80 is now fixed 0x100 e HFP in the first SCO link audio after a module reset the audio signal was not routed to the ADC DAC this has been fixed e Auto SCO release on CVC security fail when a SCO connection audio is established with CVC enabled S318 gt 0 and the CVC security check fails ERROR 83 then the module automatically releases the SCO connection The failed security check would block any audio signal to be routed through the ADC DAC so the auto release just cleans up this exceptional scenario With properly configured CVC the security check should always pass However during the development phase this issue can occur easily 10 4 Changed S Register defaults e 332 1 in factory default setting was O before This allows ATH1108 and ATH for the HS instance 10 5 Limitations e The maximum length for extended inquiry data is 112 Bytes The Bluetooth specification allows up to 240 Bytes but this cannot be achieved on BTM510 511 due to
15. entering an A2DP connection Bit1 o 2 restore discoverable connectable state according to S512 when exiting an A2DP connection Bit 2 o 3 combination of 1 and 2 o Notes 1 Inquiry scanning and page scanning discoverable and connectable state consume bandwidth which and cause insufficient bandwidth for the audio stream If both ends are discoverable and connectable then dropouts in the audio stream can be expected Bit 1 of this S Register has the same effect as issuing AT BTX after an A2DP link has been established That is why it has been named Auto BTX 2 AT BTG Q P will work normal when issued while in an A2DP connection However if Bit2 is enabled the changed scan state may be overridden by the settings of S512 when exiting the A2DP connection 3 The current scan state can be checked by new ATI27 e 544 configure UART for high throughput or low latency default 1 high throughput o 0 low latency o 1 high throughput default o Anew setting needs subsequent AT amp W store value and ATZ reset before it becomes effective 3 4 Other changes e Maximum number of trusted devices changed back from 9 to 10 ATI6 3 5 General information This release v14 1 1 2 is engineering firmware and must be used for development only The new features of this release are not covered yet by automated regression tests There have been manual sanity checks but there might still be bugs and untested use cases lef
16. sampling rate mismatch HF s102 510 HFG s102 40 SPP SCO HS s102 2 HSG s102 8 AT BTAx CVC Internal Codec s315 0 Y Y Y disabled PCM s315 3 Y Y Y s318 0 12S s315 1 2 WY 8kHz Y 8kHz Ww 8kHz SPDIF 0 1 O 1 CVC Internal Codec s315 0 Y Y Y enabled PCM s315 3 O 2 O 2 O 2 peter ol 12S s315 1 2 Y 8kHz Y 8kHz V 8kHz SPDIF O O O 1 SPDIF not supported currently but seems to be feasible 2 Seems to be a data format issue CVC creates expects data in a format for the internal audio codec not PCM CSR support required 3 Internal Codec analogue all other interfaces are digital external audio interfaces The PCM interface and the 12S interface may require further configuration which can only be achieved by PS Keys Please refer to the CSR BCO5 EXT data sheet chapter 10 PS Keys can be modified by PSTool exe provided by CSR via SPI or UART BCSP mode Alternativeley PsUpdate bat a tool provided by Laird Technologies allows modification of the following PSKeys via UART PSKEY_PCM_CONFIG32 amp 01B3 PSKEY_PCM_FORMAT amp 01B6 PSKEY_DIGITAL_AUDIO_CONFIG 01D9 The values for these keys are passed to PsUpdate bat in a psr file La rd Firmware Release Notes _TECHNOLOGIES JD BTM510 BTM511 DocNo BTM510 511 v18 1 3 0 Page 28 of 30 9 8 SCO input output channel If SCO which is mono is routed over an audio interface whi
17. 5 4 3 2 1 0 function mapping code av_operation_id reserved FMS NEN INV DIR PS Default 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Field Description O PS I O Pin State returns the current state of the I O pin 0 1 when read A write affects the 1 0 pin directly if DIR 1 and FME 0 1 DIR Direction controls if the I O pin is an input or an output 0 input 1 output 2 INV Inversion controls if the I O pin is inverted or not Applies to both pin directions read and write 0 not inverted 1 inverted 3 NEN Notification enable sends a notification to the host via UART on each status change if the GPIO is an input AT amp W and ATZ is required for a new setting to become effective Notification format ANNGPIOx yin x GPIO index 1 8 y new pin state 0 1 with INV flag applied 0 disable notification 1 enable notification 4 FMS Function Mapping Select Selects modem control function AVRCP operation id or Function Mapping Code 0 FMS_NONE function mapping disabled 1 FMS_MODEMCTRL use GPIO as modem control line 2 FMS_AVRCP_OP bits 8 15 specify AVRCP operation ID 3FMS_MAPCODE bits 8 15 specify Function Mapping Code 5 7 Reserved A Function Mapping Code or an av_operation_id is set in this bit field The pin is 8 15 mapped to a profile specific function A2DP HFP or to an AVRCP remote control function mapping code operation and will carry out the assigned operation A mapped functi
18. OA Doc No BTM510 511 v18 1 3 0 Page 6 of 30 e HFG ATH displays NO CARRIER but does not release the SLC Workaround use AT HFGH instead Ref 1 12 e HFG call records There are currently no AT command available for the following purposes o Clear a waiting call Ref 1 16 o Make a held call active Ref 1 17 o Clear a held call Ref 1 18 e Multiple profiles The usage of multiple profiles at the same time other than A2DP and AVRCP has not been tested and might cause issues Only the profile s which is are used shall be enabled If too many profiles are enabled the module can become instable and reboot due to lack of memory Ref 1 21 e Multiple profiles A2DP SNK AVRCP CT HF this scenario would require additional AT commands and S registers which are not available with this firmware e A2DP SNK when connected to an A2DP source and streaming audio sometimes gaps in the audio stream have been observed This was due to the module still being in discoverable and connectable state after A2DP has connected The problem could be solved by issuing AT BTX make module not discoverable and not connectable Ref 1 23 e Undocumented usage of LED1 to indicate audio related states e g loopback can disturb normal operation of LED1 Ref 1 24 e Module is not discoverable after releasing an SPP connection ATH while S512 4 Ref 1 25 1 5 Interoperability tests with mobile phones
19. ccccnnccnnnncncnnccnonancnnncnnnnancnnnannnnarcnnnanonnarnnnnnnnnnarannnanonnarcnnnacananins 20 5 3 Bugs fixed Compared to 14 12 Didi 20 Firmware Version 18 1 2 2 engineering firmware 21 Firmware Version 18 1 2 3 engineering firmware 22 7 1 New Features compared to V14 1 2 1 oooooocccccnnccccconoooccncncnnnnnnnnanancnnnnnnnnnnnnnnnnnnnncnnnnnnns 22 7 2 NOW AT COMMANAS a aii 22 3 NE WA Eoaea O e Ee E ETET dates 22 FAC A Seeon pena e e E E EAR TE 22 7 5 New asynchronous Mess ages io Ai 23 ATM SL A 23 TATAE E Aoi oT e eE EA E EEEE EA id 23 7 8 Bugs fixed compared A a 23 7 9 Bugs fixed compared to 181 22 sacas loteo 24 7 10 KNOWNISSUCS mata da tad a tdt 24 7 11 General infOrmMatiOnexc c eo eee Ae da dd eae ele ad dt dine 24 Firmware Version 18 1 2 4 engineering firmware 25 8 17 NGW AF COMMAS sires cree cece cee cece cd exteceeceatacav oentctomncyeacseeavteteseus Gavin esseetuaers seceeeeveodaaweneaste 25 8 2 Bugs fixed compared to 18 Taiana aa eii 25 8 3 General inforMati0N ccooncccnncccnnncnnnncccnnancnnnanonononononnnonanononanonnncno narco narannnanonnarcnnnaccnnanas 25 Firmware Version 18 1 2 5 engineering firmware 26 9 1 New Features compared to V18 1 2 4 ccccccccceceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 26 92 Extended S ROGISUGIS customers eeaeee aaps Edea aeret aae sn erresu Yieee aai 26 9 3 NOW ATI COMMANGS tico in a lid ad e EdE 26 9 4 New Error COdES cooccccnccccnccccnncnconaccnnncno
20. ch normally supports stereo the left channel is selected for the input signal Input Channel SCO Output Channel SCO Internal Codec A left A and B left and right 125 Left Left and Right Note on the BTM51x mini dev kit the stereo input connector left and right channels are swapped tip right ring left sleeve ground This is a known issue and will be fixed with the next revision of the dev kit The correct assignment for the jack is tip left ring right sleeve ground 9 9 Bugs fixed compared to 18 1 2 4 e HFP HSP SCO request when SPP enabled When one of HF HFG HS HSG was enabled along with SPP and an incoming SCO request occurred the message AUDIO ON SCO was printed to the UART but actually something like HF AU1 would be expected A subsequent status mismatch was caused too This issue has been fixed Ref 2 7 9 10 General information This release is engineering firmware and must be used for development purposes only La rd Firmware Release Notes _TECHNOLOGIES JD BTM510 BTM511 TO Doc No BTM510 511 v18 1 3 0 Page 29 of 30 10 Firmware Version 18 1 3 0 production firmware 10 1 Features This release does not contain new features compared to 18 1 2 5 All features which have been added by engineering releases since v14 1 2 0 are part of this release 10 2 Regression Testing Automated regression tests have been executed to cover all implemented features
21. connection is initiated from the PC then DCD is asserted as expected Ref 2 34 7 11 General information The first part of the firmware version number has changed from 14 to 18 This reflects the transition from bluestack firmware 23e to 23i The change was required in order to support the 5 generation of CVC ATI1 now returns the new bluestack build number 6530 La rd Firmware Release Notes _TECHNOLOGIES JD BTM510 BTM511 TEO Doc No BTM510 511 v18 1 3 0 Page 25 of 30 8 Firmware Version 18 1 2 4 engineering firmware 8 1 New AT commands e AT HFFN Query local HF and remote HFG NREC flag of HF HFG supported features An HFP SLC is required Response lt HF_NREC gt lt HFG_NREC gt Range 0 1 8 2 Bugs fixed compared to 18 1 2 3 e PC DCD issue SPP this issue Ref 2 30 was only fixed if the connection was initiated from the PC side But if the connection was initiated from BTM51x the DCD line was not asserted on the PC s virtual COM port can be detected with EzurioTerminal exe This second issue has been fixed now as well Ref 2 34 e A2DP reconnection issue after closing down an A2DP connection in an unclean way e g by switching off Bluetooth at the peer device during streaming the BTM51x made an automatic reset panic on entering the next A2DP connection This issue has been fixed now Ref 2 33 8 3 General information This release is engineering firmware and must be used for dev
22. cure simple pairing SSP e Extended inquiry response EIR e CSR Bluestack build 5365 native mode 56bit encryption 23e e Bluetooth approval listed under QDID B016227 e Tested by regression tests 1 2 Changes in AT command set compared to 14 0 0 11 e New feature Call Records AT HFGC query call records e New S register S354 enable disable verbose mode for call record presentation e New command AT HFGBO0 1 disable enable in band ringing when SLC connected e HF state ATI65 enhanced by 5 call setup SLC and 6 call setup audio e AT HFGP returns ERROR 63 when issued during a call setup state ATI66 5 or 6 e AT HFGA and AT HFGP return ERROR 63 when issued during a call setup state ATI66 5 or 6 1 3 Bugs fixed compared to 14 0 0 11 e AVRCP a BTM410 411 has refused incoming AVRCP connections observed in CT and TG role this has been fixed Ref 0 2 0 3 e AVRCP company ID was incorrect in AVUR response to AT AVU this has been fixed Ref 0 4 e AVRCP operation ID previous channel 0x32 missing in documentation Operation IDs 0x32 0x37 wrong by one in documentation has been corrected in documentation and La rd Firmware Release Notes _TECHNOLOGIES JD BTM510 BTM511 A Doc No BTM510 511 v18 1 3 0 Page 5 of 30 updated in firmware The previously wrong operation IDs have been shifted by one to be correct e g page down corresponds to
23. ed a redundant HSG AU1 is being sent between HSG B and CVCID Ref 3 12 e AVRCP direction indicator missing AVRCP does not display a direction indicator incoming lt or outgoing gt when a connection is established Compared to all other profiles this is inconsistent Ref 3 13 e EIR when filling up the RAM buffer with gt 112 bytes of EIR data AT BTE and writing the buffer to the baseband AT BTE a module panic occurs reset The length of EIR data is limited to lt 112 bytes with this release Ref 3 14
24. elopment purposes only La rd Firmware Release Notes TECHNOLOGIES gt BTM510 BTM511 Doo Doc No BTM510 511 v18 1 3 0 Page 26 of 30 9 Firmware Version 18 1 2 5 engineering firmware 9 1 New Features compared to v18 1 2 4 e AAC codec support for A2DP sink subject to licensing see section 9 6 e PCM interface now supported e Additional audio features for SBC encoder A2DP sink configurable with CSR s UFE Universal Parameter Manager via SPI interface o Parametric equalizer o 3D stereo enhancement o Compander e CVC support added for HSG HFG and SPP SCO was limited to HS and HF in 18 1 2 4 9 2 Extended S Registers e 307 enable optional A2DP codec o Bit O 1 APTX source encoder or sink decoder o Bit 1 2 AAC sink decoder only e 315 SCO audio interface select o 0O internal default 1 I2S master 2 12S slave 3 PCM 9 3 New ATI commands e ATI37 SPP SCO link type o O unknown 1 SCO 2 eSCO o Replaces the SCO eSCO part of the previous AUDIO ON OFF message SPP SCO AT BTAx see 9 5 9 4 New Error codes e 92 AT BTAx not permitted occurs if one of HF HFG HS HSG and SPP is connected to one peer device Reason a SCO link is part of the HFP HSP specification Requesting SPP SCO AT BTAx would cause confusion in this scenario 9 5 Messages changed e SPP SCO AT BTAx o AUDIO ON e SCO gt SPP AU1 o AUDIO OFF gt SPP AUO o The in
25. fer and baseband e AT BTE lt data gt append EIR data to RAM buffer e AT BTE copy EIR data from RAM buffer to baseband e AT BTE query EIR RAM buffer e AT BTE clear EIR RAM buffer e AT BTEW copy EIR RAM buffer to persistent store e AT BTED delete EIR data from persistent store e AT BTEW query EIR data from persistent store note the content of the persistent EIR data storage is copied to the baseband at boot time 2 3 New S Registers e 355 audio resource override 0 3 default 1 o O0 no override allowed o 1 incoming outgoing SCO request will be accepted while A2DP is streaming The module will initiate A2DP suspend automatically default o 2 incoming outgoing A2DP start resume request will be accepted while SCO is active The module will release the SCO link automatically o 3 combination of 1 and 2 e 356 enable restoring of last gain used for SCO 0 3 default 3 o 0 Disable gain restoring for SCO o 1 Enable output gain restoring for SCO o 2 Enable input gain restoring for SCO o 3 Enable input and output gain restoring for SCO e 357 enable restoring of last gain used for A2DP 0 3 default 3 La rd Firmware Release Notes _TECHNOLOGIES JD BTM510 BTM511 AAA Doc No BTM510 511 v18 1 3 0 Page 9 of 30 o 0 Disable gain restoring for A2DP o 1 Enable output gain restoring for A2DP o 2 Enable input gain restoring for A2DP o 3 Enable input and output gain restoring
26. for A2DP 2 4 New unsolicited messages e APSTR lt streaming started initiated remotely e APSTR gt streaming started initiated locally e APSUS lt streaming suspended initiated remotely e APSUS gt streaming suspended initiated locally 2 5 New ATls e ATI61 o 0 A2DP not connected o 1 A2DP connected and streaming o 2 A2DP in suspended state connected but not streaming e ATI21 SCO token index of the profile instance owning an active SCO connection O none 1 HS 2 HSG 3 HF 4 HFG 5 SPP_BTA e ATI22 last SCO output gain e ATI23 last SCO input gain e ATI24 last A2DP output gain e ATI25 last A2DP input gain 2 6 New Error Codes e 76 memory allocation attempt was unsuccessful e 77 incorrect A2DP state see ATI61 e 78 request rejected due to priority related to S355 settings 2 7 Other changes e Maximum number of trusted devices changed from 10 to 9 ATI6 o Direction indication incoming lt outgoing gt for A2DP CONNECT messages 2 8 General information This release v14 1 1 1 is engineering firmware and must be used for development only The new features of this release are not covered yet by automated regression tests There have been plenty of manual sanity checks but there might still be bugs and untested use cases left La rd Firmware Release Notes _TECHNOLOGIES JD BTM510 BTM511 po Do No BTM510 511v18 13 0_ Page 10 of 30_ 2 9 Bugs fixed compared to 14 1 1 0
27. formation about the current SPP SCO link type SCO or eSCO can be queried by ATI37 La rd Firmware Release Notes _TECHNOLOGIES J BTM510 BTM511 oo 63603 DocNo BTM510 511 v18 1 3 0 Page 27 of 30 9 6 AAC Licensing This firmware contains AAC technology which incorporates intellectual property owned by numerous third parties Supply of this product does not convey a license under the relevant intellectual property of those third parties nor imply any right to use this product in any finished end user or ready to use final product An independent license for such use is required For details please visit http www vialicensing com 9 7 SCO audio internal external audio interfaces The matrix below gives an overview of combinations of profiles and audio interfaces that are currently supported SCO audio refers to bidirectional mono audio for transmission of speech with 8 kHz sampling rate The PCM pins of the BTM51x share support for PCM 125 and SPDIF S315 selects one of these interfaces or the internal codec internal codec refers to the on board audio ADC DAC clock generator and antialiasing filters hence the on board analogue interface PCM in combination with CVC doesn t work well 2 SPDIF is currently not supported but seems to be feasible 1 For 125 normally used for stereo audio make sure the sampling rate is configured to 8kHz if used with SCO otherwise it will sound very strange due to the
28. gt or from cache AT BTDW A new connection attempt e g AT SPD lt BdAdadr gt should initiate new pairing automatically e HF ATH111E and ATH for HF do not respond with OK but with NO CARRIER only Ref 3 5 e HFG call records There are currently no AT command available for the following purposes o Clear a waiting call Ref 3 6 o Make a held call active Ref 3 7 e HFG AT HFGE lt ext_err_code gt an issue with extended error codes has been observed AT HFGE lt ext_err_code gt does not work as expected Workaround do not use extended error codes but simple error messages e AT HFGE without parameter Ref 3 8 e EIR after repeatedly issuing AT BTE or AT BTEW provided data is stored in the RAM and persistent buffer the commands stop working or only display a part of the buffered data lt has been observed that this issue occurs after in the regression tests after the 42 repetition of the test sequence Ref 3 9 e HF order of HF AUO 1 messages it has been observed that the position of HF AUO or HF AU1 can vary within the asynchronous message sequence during a call or a call setup Ref 3 10 e HSG the asynchronous message FS8000 INT is sent prior to HSG B which is not correct From a the logical sequence point of view one would expect HSG B first and FS8000 INT thereafter However the content of these messages is correct Ref 3 11 e HSG CVC enabl
29. his release is engineering firmware and must be used for development only The new features of this release are not covered yet by automated regression tests There have been manual sanity checks but there might still be bugs and untested use cases left 5 2 New AT commands e AT HFM lt x gt with lt x gt 0 9 A D request a DTMF tone to be created by a connected HFG e g mobile phone The command AT VTS lt x gt is sent on the SLC Refer to HFP 1 5 specification feature 17 section 4 27 Has been tested with an iPhone COD S515 200404 and a Samsung E250 5 3 Bugs fixed compared to 14 1 2 0 e Secure Simple Pairing SSP leading zeroes were not displayed in the SSP passkey of the following asynchronous messages PAIR lt BdAdadr gt lt friendlyname gt lt Passkey gt PASSKEY N lt BdAddr gt lt friendlyname gt lt Passkey gt Therefore it was possible that passkey contained less than 6 digits This has been fixed now Leading zeroes will be inserted so that a 6 digit passkey will be guaranteed in any case Ref 2 25 e Serial Port Profile SPP On the hang up attempt of the 7th SPP connect disconnect cycles the module went through a reset automatically This could possibly lead to issues because this behaviour is probably not expected by the host controller However this issue has been fixed now Ref 2 21 e Serial Port Profile SPP When issuing AT BTX disable discoverable and connectable
30. internal memory limitations Ref 3 1 e External audio codec I2S master clock in addition to the 12S signals SD_IN SD_OUT WS SCK external audio CODECS often require a high frequency synchronisation clock from one master clock source in the system This master clock would typically be created by the BTM51x and the clock frequency would be 12MHz or 24MHz BTM51x has no means of providing this master clock to an external 12S device If a 12MHz or 24MHz master clock is required then BTM52x should be used instead of BTM51x If master clock synchronisation is missing then artefacts will be audible in periodic intervals In the use case of a wave file player recorder no codec the 12S signals are sufficient and no master clock synchronisation is required Ref 3 2 La rd Firmware Release Notes _TECHNOLOGIES JD BTM510 BTM511 O D OSOS Doc No BTM510 511 v18 1 3 0 Page 30 of 30 10 6 Known issues e A connection attempt of any profile fails NO CARRIER if the peer s device BD address is stored in the local list of trusted devices AT BTT or AT BTW but for any reason the local device s BD address is not stored in the peer s device trusted device list any longer link key missing Ref 3 3 Workaround a recommended use AT BTW lt BdAdadr gt to initiate new pairing to generate new link keys on both ends Workaround b the link key for the remote device can be deleted from the trusted device list AT BTD lt BdAddr
31. ived from the HFG on a DTMF request AT HFMi on UART AT VTS i on SLC 7 8 Bugs fixed compared to 14 1 2 1 e A2DP 48kHz issue when the module was configured as A2DP sink and the remote device sets up a DAC sampling frequency of 48kHz the module has rebooted This issue La rd Firmware Release Notes _TECHNOLOGIES JD BTM510 BTM511 oe Nos Bs 10167 VI8 3 0 Page 24 oF 30 has occurred for example with the Broadcom Bluetooth stack and a couple of mobile phones It was a bug in the module s firmware and has been fixed Ref 2 31 e 555 3 On expiration of the post reset time window see S554 the module reverts to not discoverable not connectable ATI27 0 instead of connectable only ATI27 2 This has been fixed Ref 2 27 e PC DCD issue when connecting to a PC via SPP the DCD line was not asserted can be seen on e g Ezurio Terminal during the connection This has been fixed Ref 2 30 e When a remote device enables Sniff Sub Rating the Bluetooth device address of that device was printed to the UART unexpectedly This has been fixed now Ref 2 29 7 9 Bugs fixed compared to 18 1 2 2 e Incoming audio in a SCO link was blocked when a CVC image was selected This issue has been fixed 7 10 Known issues e When initiating an SPP connection from a BTM5xx to a PC with Microsoft Bluetooth stack DCD is not asserted on the PC end This can be detected by a terminal program e g Ezurio Terminal If the
32. lave device This third BTM5xx is configured for 12S cross loopback mode by AT BTL4 It then acts as analogue to I2S converter bees SD_IN analogue audio in _ Soe PCM_IN audio 7 audio out ePCM_OUT SD QUT 12S digital BTM5xx in 128 ws audio cross loopback PCM_SYNC mode slave SCK AT BTL4 Pow AIS The following table lists all AT commands required for this scenario Analogue to A2DP Source A2DP Sink with Comment I2S converter with 125 input analogue output 1 AT amp F AT amp F AT amp F Restore factory default settings AT BTL4 Configure 12S slave source 1 ATS314 1 Select 12S master interface at A2DP source ATS300 2 Enable Source role ATS512 4 Make connectable and discoverable La rd Firmware Release Notes TECHNOLOGIES gt BTM510 BTM511 VO e Doc No BTM510 511 v18 1 3 0 Page 17 of 30 AT amp W AT amp W Store S Register configuration ATZ ATZ Reset AT APD lt Bluetooth Initiate connection Get Bluetooth address of Address Source gt other end by ATI4 on other end or by inquiry AT BTI 1 for demonstration purposes or if no other 12S source is available a 3 BTM5xx can be used as analogue to 125 converter in 12S cross loopback mode 4 9 GPIO configuration A GPIO pin is configured by S651 S658 according to the following bit mapping Bit 15 14 13 12 11 10 9 8 7 6
33. nnncnnnnnnnnnanonnnnnonnnnnnnaronnnannnnnrnnnnrnnnnanonnnncnnnnccnnanes 26 9 5 Messages changed isnin cet cba Sete sa cetera oh aa alee sears a asin 26 9 6 A A Ans ce aed Ata 27 9 7 SCO audio internal external audio interfaces ccoooonccnncconnncnnnnnononnnonanonnnononononcnnnnnnnns 27 9 8 SCO input output channel ceci sect ack cea cdetoran dl il ida 28 9 9 Bugs fixed compared to 13 1 24 a vet cident ieee ee eae OR Eetoaees 28 9 10 General IOMA 28 Firmware Version 18 1 3 0 production firmware 29 10 1 Features 325 coh coc idiota bdo dete ads ideas 29 10 2 REOTESSION TESIS oe ae aie ae le et ar E 29 10 3 Bugs fixed compared to 18 ls nit Bae eee 29 10 4 Changed S Register defaults ocoononnocccccnnnnncncnnonccnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnos 29 10 5 IMITATIONS A A oidedeiass 29 10 6 KROWNNSSUCS o ainia 30 La rd Firmware Release Notes _TECHNOLOGIES JD BTM510 BTM511 IS E Doc No BTM510 511 v18 1 3 0 1 Firmware Version 14 1 1 0 1 1 Features e Bluetooth 2 1 2 1 EDR e Supported Profiles o Serial port profile SPP o Advanced Audio Distribution Profile A2DP Source Sink o Audio Video Remote Control Profile AVRCP Control Target o Hands free Profile HFP Hands free unit and Audio Gateway o Headset Profile HSP Headset and Audio Gateway o Dial up Network Profile DUN Dial Terminal e SCO eSCO audio connection e Sniff mode e Standard non standard UART baud rates configurable e Se
34. on does not av_operation_id affect any other flag of the GPIO configuration register So e g DIR and INV must be set manually according to the selected function and hardware requirements Valid only if FMS gt 2 FMS selects function mapping code or av_operation_id La rd Firmware Release Notes TECHNOLOGIES gt BTM510 BTM511 AN Doc No BTM510 511 v18 1 3 0 Page 18 of 30 Value Function Mapping Code Input 0x00 Cable Replacement TX 0x01 RFC_RTC_TX 0x02 RFC_RTR_TX 0x03 RFC_IC_TX 0x04 RFC_DV_TX 0x05 Volume down single step 0x06 Volume up single step 0x07 Volume down multiple after short press 0x08 Volume up multiple after short press 0x09 Volume down multiple after medium press Ox0A Volume up multiple after medium press 0x0B Headset Button 0x0C HF green button Ox0D HF red button Value Function Mapping Code Output 0x00 Cable Replacement RX 0x01 RFC_RTC_RX 0x02 RFC_RTR_RX 0x03 RFC_IC_RX 0x04 RFC_DV_RX 4 10 Bugs fixed compared to 14 1 1 2 e The implementation of the EIR commands AT BTE family have shown a number of instabilities in previous f w versions Many of these issue have been resolved and the EIR implementation can be regarded as much more stable with this version It was also found that the maximum EIR data length is limited to 160 Bytes due to internal memory limitations Ref 1 28 e When in
35. quiring with friendly name e g AT BTIN and a remote device was discoverable but not connectable this remote device was not listed in the inquiry results though discoverable This has been fixed now If the friendly name cannot be retrieved e g due to not connectable then a will be displayed instead of the friendly name Ref 1 29 e Range of S102 limited to 0 1FF was 0 7FF 4 11 Known Issues e The maximum length for extended inquiry data is 160 Bytes The Bluetooth specification allows up to 240 Bytes but this cannot be achieved on BTM510 511 due to internal memory limitations Ref 2 1 e 4 out of the 8 GPIO lines are bound to modem control line functionality DTR DSR DCD Rl Hence only the 4 remaining GPIO lines are real GPIOs Ref 2 2 e External audio codec sync in addition to the 12S signals SD_IN SD_OUT WS SCK external audio CODECS often require a high frequency synchronisation clock from one master clock source in the system This master clock would typically be the BTM51x and the clock frequency would be in the range of 12MHz or 24 MHz or similar BTM51x cannot provide this clock to an external 125 device BTM52x possibly can but confirmation an tests are still outstanding If this high frequency clock synchronisation is missing artefacts will be audible in periodic intervals In the use case of a wave file La rd Firmware Release Notes _TECHNOLOGIES JD BTM510 BTM511 oe Nos BTS 10167 VI8
36. t 3 6 How to enable APTX Source Sink Comment AT amp F AT amp F Restore factory default settings ATS307 1 ATS307 1 Enable APTX ATS300 2 Enable Source role ATS512 4 Make connectable and discoverable AT amp W AT amp W Store S Register configuration ATZ ATZ Reset AT APD lt Bluetooth Initiate connection Get Bluetooth La rd Firmware Release Notes TECHNOLOGIES gt BTM510 BTM511 Doo D Doc No BTM510 511 v18 1 3 0 Page 13 of 30 Address Source gt address of other end by AT14 on other end or by inquiry AT BTI Verify codec in use APTX SBC Note the APTX decoder sink role will mute after about 5 minutes This is due to APTX licensing If your are interested in getting a full decoder license please contact Laird Technologies The APTX encoder source role is fully functional ATI26 ATI26 3 7 Bugs fixed compared to 14 1 1 1 If S504 1 silent operation enable the CONNECT message was not suppressed on ATO this has been fixed Ref 1 27 New S308 is automating the workaround of AT BTX after creation of A2DP connection Ref 1 23 3 8 Known Issues e See section 2 10 La rd Firmware Release Notes _TECHNOLOGIES JD BTM510 BTM511 TOO Doc No BTM510 511 v18 1 3 0 Page 14 of 30 4 Firmware Version 14 1 2 0 production firmware 4 1 New Features compared to v14 1 1 2 e 12S digital stereo audio in
37. terface support o Enabling use of external codecs or wave file player recorder o Master or slave role selectable o Test mode 12S cross loopback internal codec bidirectional audio o Sampling frequencies supported by external codec configurable by S316 e GPIOs general purpose input output support o 4freely usable GPIOs available o Function mapping e g volume up down headset button etc o AVRCP operation id mapping e g Play Stop Pause etc e Full APTX license for all modules from production not for field upgrade e EIR extended inquiry response data improved maximum data length 160 Bytes e Tested by regression tests e All features of previous production and engineering firmware v14 1 1 0 v14 1 1 1 v14 1 1 2 4 2 New and enhanced AT commands e AT BTL32 12S cross loopback mode 12S master sampling rate defined by S419 e AT BTL4 12S cross loopback mode 12S slave sampling rate defined by S419 4 3 New ATI commands e ATI28 query current audio sampling rate displayed for input and output e ATI29 query maximum data length for EIR data e ATI30 query current RAM buffer length EIR e ATI31 query current baseband buffer length EIR e ATI411 short press duration time in ms e ATI412 medium press duration absolute time in ms S411 S412 e ATI413 long press duration absolute time in ms S411 S412 S413 4 4 New S Registers e 309 Enable asynchronous FS message currently used sampling frequency o O disable
38. tiate new pairing to generate new link keys on both devices Workaround b the link key for the remote device can be deleted from the trusted device list AT BTD lt BdAddr gt or from cache AT BTDW A new connection attempt AT SPD lt BdAddr gt should initiate new pairing automatically However this might not work with some legacy BT2 0 and earlier devices Hence workaround a is recommended e All profiles It has been observed that after profile disconnection NO CARRIER a delay of at least 200ms is required before the module can initiate a connection again successfully Ref 1 8 e AVRCP It has been observed that on a link between two BTM510 511 one end configured as target TG the other end configured as control CT a value of Bad profile in S311 AVRCP response type at the target side is causing a timeout response AVPTC 4 lt Opld gt 0 to AT AVC lt Opld gt issued at the CT side It has not been clarified if this issue is caused by either TG or CT Ref 1 9 e HFG AT HFGE lt ext_err_code gt an issue with extended error codes has been observed AT HFGE lt ext_err_code gt does not work as expected Workaround do not use extended error codes but simple error messages i e AT HFGE without parameter Ref 1 10 e HFG ATH11F does not release SLC but returns ERROR 56 Workaround use AT HFGH instead Ref 1 11 La rd Firmware Release Notes _TECHNOLOGIES JD BTM510 BTM511 T
Download Pdf Manuals
Related Search