DA14580

advertising problem with samsung android 9 and beyond

Sun, 2020-01-19 15:24--NadavG

hi all,
we have a device using GATT protocol over da14580 ble
until recently we had no problem with the advertisement of the device
but in the past few weeks we discovered that on samsung phones using android 9 our device appear as "unnamed" and on android 10 it doesn't appear at all
we tried to run the default sdk code on the ble (SDK 5.0.4\DA1458x_SDK\5.0.4\projects\target_apps\ble_examples\ble_app_profile\Keil_5\ble_app_profile), and it acts the same - the USER_DEVICE_NAME doesn't appear on search

SL4DVKISP / GreenPAK designer command line tool

Fri, 2020-01-17 10:52--pkrmht

Dear Forum

Ist there anything like a GreenPak Designer command line tool. My intention is, once the design is completed and the GUI no longer neede, to have the ability to just program the NVM of my SLG468246 over SL4DVKISP by command (which can even be part of a script doing other things, too).

Background: I intend to make the programming of the SLG468246 device part of the production test of the board the device is on, therefore no GUI interaction is wanted.

Thanks for your inputs in advance & best regards
Peter

I2C adressing of registers

Fri, 2020-01-17 10:13--pkrmht

Dear Forum

Figure 102 (I2C block addressing) of SLG468246 datasheet states A[10:8] = "00X" addresses "2 Kbits Register Data Configuration". Since the register address space has 8 bits only, I wonder what A[10:8] = "001" is used for (I2C ping shows the device actually acknowledges at this address).
Is this just reserved for future addressing of larger address spaces (totally 4 Kbits) and has not function behind it? Or does it have a specific function? If yes, which one? Any pitfall?

Thanks for your inputs in advance & best regards
Peter

No Connect request from Master but DA14580 keep invoke on_connect and disconnect

Fri, 2020-01-17 09:50--Jeck_Wang

Hi Team,

We are developing a product with DA14580 worked as Slave while a mobile app as Master.

And we are using Security mode as passKey try to do the paring. For now, we used the DSPS app on both Android and iphone, the paring has successed on the first time.

Patching OTP FW

Thu, 2020-01-16 09:34--ViSt

Is it possible to patch a FW in written to OTP? I read some app notes that indicated that it might be possible by using SPOTA. According to UM-B-011 there is a part of the retention ram 0x81A1F to 0x81FFF which holds SPOTAR patches. The original FW does not implement SPOTA however. I suspect the bug is caused by SDK 3.0.8.0 and fixed in 3.0.10.0 so the change required may be quite large.

Field-Update of SLG46824/6 used as power sequencer

Thu, 2020-01-16 08:21--pkrmht

Dear Forum

My intention is to use SLG4682x as power sequencer in our newest Zynq MPSoC design.
Initial NVM programming will be done during production test through testpoints on I2C with the MPSoC unpowered.

In the product, the I2C-bus is controlled by MPSoC as master and available only after the SLG4682x controlled power sequencing. Therefore a field update becomes risky if the NVM programming is interrupted by a power fail: The sequencing will not work due to the now corrupted NVM and the mentionned testpoints are not accessible in the field.

Problem trying to boot DA14580 using external SPI

Wed, 2020-01-15 15:34--AlejandroCastillo

Hi team,

我们使用一个定制的硬件包括DA14580 device. We want to boot it through another microcontroller as master (ADuCM4050) by using SPI protocol, so we have implemented some functions following the Application note document (booting from serial interfaces). The first packet sent is composed by the preamble, a 0x00 and the Length LS byte. If everything was fine, we may receive an ACK (its value is 0x02) in the position 3 of rx buffer (from 0), but that's not the case. In fact, we obtain the results shown in the attached pdf.

iPhone 7 pairing failed with SDK v3.0.8.0

Wed, 2020-01-15 10:56--ViSt

我有两个版本的我们弗兰克-威廉姆斯在一个旧的产品。Version 1 running SDK v3.0.8.0 and version 2 running SDK v3.0.10.0.

When I try to pair with version 1 with an iPhone running iOS v13.3 the iPhone sends a pairing request with secure connections even though our FW is running BLE v4.0. This causes the FW to respond with pairing failed with reason invalid parameters.

It works well with older iPhones since they don't support secure connections and all androids since they won't set the secure connections flag when communicating with a device running such an old BLE version.

no advertise data details appear.

Wed, 2020-01-15 10:01--nabilahderes

Hi Dialog member,

I'm using Codeless v5.380.5.4.0. During 1st power start up, no advertise data details appear. Only device name appear.

I'm using nRF connect for evaluation. I define advertise data in function user_app_on_init.

Manufacturer specific data not appear. Could you advise me why this condition occured?

Pages

Subscribe to RSS - DA14580