hello
i have tried the dsps example on the dialog 14580 dk basic and it works ok but when i burn the same
example to a murata module (to a flash memory i connected via spi, using smart snippets), the dsps application on my iphone detects it for a second and than the app doesnt detects it anymore.
the app detects the module for a second only after a power reset of the module.
i thought maybe the program enters a sleep mode for some reason (although in the DK it doesnt)
is there an external sleep pin that needs to be high or something?
could it be that the sram gets deleted maybe?
what can be the reason ?
tnx
roi
Device:
Hi roinovi,
Since you burn the DSPS application in the SPI the 580 needs a reset in order to boot. Please check if without extended sleep mode the device is operating normally (undefine the CFG_EXT_SLEEP in the da14580_config), if it does then it should be the clock settings of your application. Please check in the da14580_config.h file the if the CFG_USE_DEFAULT_XTAL16M_TRIM_VALUE_IF_NOT_CALIBRATED is defined also try to change the low power clock from XTAL32 to the RCX20. Since your device advertises only for a while and stops as soon as it enters sleep it should be a clock issue.
Thanks MT_dialog
嗨
i have undefined the "CFG_EXT_SLEEP" and the dsps app detects the module only after the module reset (if the app detected the module after the module reset it will keep detecting it even if i keep pressing "search again" in the dsps app, but if i reset the module and presse "search" in the app after a few seconds the app will never detect the module even if i press "search again" a few times).
once detected, the signal is very low (one bar at the maximum even in very close proximity)
is it a software or hardware issue?
regarding the post above: i saw in the code that the CFG_USE_DEFAULT_XTAL16M_TRIM_VALUE_IF_NOT_CALIBRATED is defined, should it be?
where should i change the " low power clock from XTAL32 to the RCX20" and what does it do?
tnx
Hi roinovi,
Since you burn the flash the device needs a reset after burning in order to run the bootloader and run the fw from the flash. The dsps android application doesn't scan constantly, it scans only for a few seconds and then in order to perform a new scan sequence you have to press scan again. So if i undestand correctly when you press the first time reset the module boots as it should and the second time it doesn't boot from the SPI ? Has the murata module that you are using a power measurement feature in order to connect it to smart snippets and check if it advertises or not ? We haven't seen these kind of behaviour in dialog's kits.
Yes the CFG_USE_DEFAULT_XTAL_TRIM_VALUE_IF_NOT_CALIBRATED should be defined in order for the fw to load the default trimming value for the XTAL16. I am not aware of the murata module that you are using, the configuration i 've mentioned above changes the low power clock source between XTAL32 and the RCX or to read the configuration from OTP.
Thanks MT_dialog
嗨
in regards for the detection. what you described is not the case, its not that in the second module reset the dsps app doesnt detects,
我只有一次复位模块,如果我按“search" in the dsps app immidiately after the module reset, the app detects the module and will keep detecting it even when i press "search again" a few times after the initial detection
but if i wait a few seconds after the module reset and then press "search" it doest detecs the module
situation is like this (2 possibillities):
1)module reset->immidiately press "search" in the iphone app->detection but low signal (0-1 bar)->press "search again"->detection low signal->press "search again"->detection etc.
2)module reset->wait a few seconds and then press "search" in the iphone app->no detection ->press "search again" ->no detection->press "search again"->no detection etc.
so now, "CFG_EXT_SLEEP" is undefined and CFG_USE_DEFAULT_XTAL_TRIM_VALUE_IF_NOT_CALIBRATED is defined.
a few questions, please explain or refrence to a knowledge source:
1)what could be the reason for the low signal? could it be a clock issue or some kind of hardware issue?
2)what is "trimming value for the XTAL16", what is XTAL16? trimm what?
3)whats the difference between XTAL32 and the RCX? what is the low power clock?
4) where\in how many places do i need to change the XTAL32 to RCX?
i am not using OTP so what did you mean in your last line above?
tnx
roi
Hi roinovi,
1) What is the murata dev kit you are using ? i havesome testson the P2ML3656 , seems to be working ok (RSSI -35 db with a generic app almost identical with the basic kit both dev kits next to the phone). If you are experiencing these kind of trouble and since there are is no such issues when running the code on the basic kit i would assume that it most probably is a hardware issue.
2) The XTAL16 is the crystal that povides the 580 the proper clocks in order for the proccessor and the radio to operate, the crystal needs to be trimmed in order to reach ppm required for the bluetooth spec (50ppm). Please check the following FAQhttp://support.dialog-semiconductor.com/faq-page#n388
3) The 580 also uses a low power clock source which switces when it falls into low power mode. The low power clocks can be provided either by a crystal (external - XTAL32) or by an internal RCX circuit. Which of the two provides the clock source can be chosen in the da14580_config with the CFG_LP_CLK the settings are indicated by the comments next to the #define.
4) The only place you have to change this is in the da14580_config.h.
Although i dont think that a low RSSI is the consiquence of a wrong crystal setting since you observe this issue when you dont use sleep mode.
Thanks MT_dialog
嗨
we have added a resistor near the antenna and it seems to fixed the low rssi
although sometimes if we press the "search again" button in the dsps app a few time it detect the ble module with low rssi