DA1468x

What is the right configuration for secure boot loader in OTP?

Wed, 2020-05-06 18:18 -- Thomas Donhauser

Hi PM_Dialog!

I need to develop an spezial OPT secure bootloader and don't know what the right config is. in ble_suota_loader the config is this:
#define dg_configEXEC_MODE                      MODE_IS_MIRRORED
#define dg_configCODE_LOCATION                  NON_VOLATILE_IS_NONE

But if I follow the the capture "3.4.3 BootROM sequence" in the documentation for da14683 the configuration may be also like this:

#define dg_configEXEC_MODE                      MODE_IS_CACHED
#define dg_configCODE_LOCATION                  NON_VOLATILE_IS_OTP

DA14683 dg_configSPI_ADAPTER issue

Sun, 2020-05-03 15:02 -- kuda

HI!

          chip id --> DA14683

          SDK -->      DA1468x_DA15xxx_SDK_1.0.14.1081\projects\dk_apps\features\ble_peripheral

          I want to enable spi adapter and find the entry  pointer in  DA1468x_DA15xxx_SDK_1.0.14.1081\sdk\bsp\config\bsp_defaults.h

          when I set  this flag  dg_configUSE_HW_SPI to 1,the compiler result is successful .

          But when I set  this flag  dg_configSPI_ADAPTER to 1,the compiler result always fail.

          these are error message,  Is there any codes or flags need to  enable ? TKS.

Crash with LD_DEFS=-DRELEASE_BUILD

Sun, 2020-05-03 12:37 -- Thomas Donhauser

Hi 

I have two da1468x USB-Kit development boards. One of them is making troubles as I mentioned already in an other forum-topic.

Here is the Link to the posting: https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-hardware-device-reference-designs/crash

BLE Connection Issue

Thu, 2020-04-30 08:59 -- johrirj88

Hi,

We are using BLE peripheral example code, from SDK which is working, but we have following situation:

We need BLE to be enabled and connected once a connection is established with a mobile app, which, as of now is disconnecting after around 10 seconds.
1. For how much time a task executes when it is created using OS_TASK_CREATE() function?
2. We need to execute it for infinite amount of time, how to do this?
3. Please share SDK manual which can explain other related queries on the functions used?

Please help in this regard asap.

Crash on hw_cpm_pll_sys_on()

Mon, 2020-04-27 15:21 -- Thomas Donhauser

Hi,

I have two da14683 USB Development Kit. In my system_init() function I call 

cm_sys_clk_init(sysclk_PLL96); to speed up. 

 

cm_sys_clk_init() calls in turn this code where in switch_to_pll().

                if (cm_poll_xtal16m_ready()) {
                        switch_to_xtal16();

                        if ((type == sysclk_PLL48) || (type == sysclk_PLL96)) {
                                switch_to_pll();
                        }
                }

In switch_to_pll() this code is invoked:

Secured Keys and Secured Boot - test before writing secure_device flag to OTP ?

Fri, 2020-04-24 09:33 -- bobspam@free.fr

Hello

I am using AES 256 CBC to transmit data to web servers using my own keys. I would like to activate security features so my symetric keys are not disclosed on the field.

 

Main idea is to

- have one binary loaded on all devices produced (I wish to avoid to execute some complex scripts generating keys on production lines. Furthermore the hardware number generator should provide better randomness than computer script)

- use the bootloader key generation feature (generate_symmetric_keys(void); in secure_hooks.c

Cannot erase QSPI?

Tue, 2020-04-21 12:49 -- point85

Hi, 

 

When trying to erase the QSPI on a DA14682 I get the following output after running the erase_qspi_jtag_win command.

.......................................................................................................................
..
.. ERASE QSPI 
..
.......................................................................................................................

Are you sure you want to completely erase QSPI (y/n or [ENTER] for n) ?
->y

Successor  for DA14683?

Fri, 2020-04-17 13:04 -- Peter Luo

Hi Dialog,

Do you have any plan to release  a successor  for DA14683?  We think the DA1469x is not ideal successor for us, because specification is changed too much!

We hope the successor of DA14683 has more memory, and can run more faster,  and support bluetooth 5.1 and keep same interfaces such as Quadrature Decoder, DIAGNOSTIC SIGNALS,etc.

Thanks, Peter  

Pages

Subscribe to RSS - DA1468x