Issue: Going to "HardFault_HandlerC" while debugging

嗨premkumar，

Have you made any changes to the app_dis_init() ? Can you please try to download the example projects as is, in order to check if the same incident occurs?

Thanks MT_dialog

嗨premkumar，

对不起，但目前我们只支持Keil而不是DA14580上的Eclipse。请检查doc an-b-024.pdf，也许您会发现它有用。

Thansk MT_dialog

嗨premkumar，

app_ble_peripheral,使用一个定制的概要文件rder to interact with the mobile application. If you want to sent data from the peripheral you have instruct it from your mobile phone (meaning read a characteristic, or write the configuration of a characteristic to sent notifications or indications). All of the handlers that are being called when instructed by the appropriate characteristic are located in the user_custs1_impl.c. For example in the specified project the function user_custs1_ctrl_wr_ind_handler() is called when the CUST1_IDX_CONTROL_POINT_VAL characteristic is written if the value written (send by the central) is other than 0 then the firmware start a software timer. When the timer elapses sends a notification (updates the value of CUST1_IDX_ADC_VAL_1_VAL), the notification is received by the central only if the notifications are enabled by the central. More info regarding the SDK5 and the examples can be found in the UM-B-050.pdf.

Thanks MT_dialog

嗨premkumar，

About the jump table please have a look at this posthttp://support.dialog-semiconductor.com/jumptablebase88also regarding the jump table, its usage is mainly to overide functions in ROM, if you want for instance the ROM code not to use the default function (the one located in the jump table), you can implement your own function in RAM and overide the function in ROM through the jump table, the rom_sym_def.txt file includes all the symbols from functions that are located in the ROM memory. I am not aware for the files that are created in eclipse.

If you have tried to access the document then you should have accepted and submitted the terms and conditions for using the software and the documents. It takes a couple of days for the admin to grand your access to the documents. Just be a bit patient and your access will be granded.

Thanks MT_dialog

嗨premkumar，

Have you accepted the terms and conditions when you 've tried to donwload the SDK and the user manuals in order for access to be granted ?

Thanks MT_dialog

嗨premkumar，

The procedure is quite simple you just click on the link you want to access and if your access is granted then you can see the document, if your access isn't granted then the terms and conditions dialog should appear. After accepting this your request goes through the admin in order to grand you access to the portal (the procedure takes a couple of days). Please check the links of the documents below. We dont have a request in our system at the moment. Try to access the links i provided, and check if you can download the documents.

http://support.dialog-semiconductor.com/resource/um-b-050-da1458x-softwa...

http://support.dialog-semiconductor.com/resource/da14583-datasheet

Thanks MT_dialog

嗨premkumar，can you go to the DA14580 product, Software & Tools and click on padlock icon next to the SDK or its release notes (top items). This should open up the SDK access request.

BR JE_Dialog

Hi Premukar,

我们没有为580提供带寄存器地图/系统查看器的.srf文件。但我想你可以通过内存窗口观看你的寄存器。

Thanks MT_dialog

Hi premkumar,

There isn't any other official I2C driver for the 580 other than the eeprom driver but there is extensive explanation of how the driver operates on some related i2c posts on the forum. Please check the following links.

http://support.dialog-semiconductor.com/multiple-byte-read-i2c

http://support.dialog-semiconductor.com/documentation

Thanks MT_dialog

嗨premkumar，

You can find the needed information about the base addresses in the 580 and scatter file info in the document UM-B-011: User Manual - DA14580 Memory map and scatter file.

Thanks MT_dialog

Hi Premukar,

You can see the booting sequence of the 14583 in the UM-B-012 Creation of a secondary bootloader section 5. The example projects are compatible with using the da14583, you just have to build them by using the 583 option. You can use Smart Snippets with the 14583 as well and burn the Flash, just make sure to select the proper configuration of the SPI pins (selecting 14583 should choose the right pins but you can also check the selected pins from the board setup). If you want to interact with the flash you can have a look at the proximity example where it uses the SUOTA profile in order to initialize, to enable and interact with the internal flash. Using the internal flash on 14583 doesn't require a special driver just the right pins.

Thanks MT_dialog

Hi Premukar,

Make sure that the proper UART pins are connected in order for the Smart Snippets to download the flash programmer to your device. Also make sure that the correct SPI pins are selected from the Board Setup section. After opening the Smart Snippets you should choose the 14583 version of the chip, this should select the appropriate SPI pins (although you should explicitly check the pins in the board setup). After that choose the SPI tab, press connect (in order for the flash programmer to be downloaded in the chip) and then erase the SPI flash (the most probable reason for not be able to erase or burn the flash is the pin selection - 2_0, 2_3, 2_4, 2_9 should be selected in board setup). There is no need to download any binaries for burning the flash Smart Snippets downloads it on the connection procedure.

Thanks MT_dialog

嗨premkumar，

You can't burn the OTP multiple times, OTP stands for One Time Programmable, you can only flip the bits from 0 to 1.

Thanks MT_dialog