Hi,
为了略微重新设计现有项目，我们希望从DA14680切换到DA14682。首先，我尝试使用SDK 1.0.10从现有的SmartSnippets Studio（v1.6.3.981）中编程硬件。当我在尝试编程时收到错误时，我下载了更新的SDK（1.0.14）并导入了相应的脚本。我第一次尝试编程，它显示了设备选择，并在选择正确的处理器后，我能够编程设备。但是，在尝试调试项目时，我总是卡在重置处理程序中。
When trying to program and debug the old device (DA14680), I can't get the device selection to come up. The script 'program_qspi_config.bat' can be found under the scripts project, but it does not appear under external tools.
我还尝试使用更新版本的SmartSnippets Studio（v2.0.14.1748），但我无法让项目编译在这里。
My questions are:
- 是否需要更新的SDK来编程和调试DA14682？
- 如何获得编程脚本的设备选择来提出？
- Do I need the newer version of SmartSnippets to work with the DA14682?
Thank you,
枪Schwab
设备：
嗨ghschwab，
For the DA1468x product family, theDA1468x SDK1.0.14.1081和SmartSnippets Studio V1.6.3 for Windows OS建议使用。
Did you import the python scripts on your workspace? Would it be possible to share some screenshots, so that I can understand your configuration?
你也可以跟随UM-B-047：DA1468X入门开发套件。
谢谢，PM_Dialog
Hi,
感谢您的回答！
我正在附加屏幕截图以显示IDE版本和SDK。
I had only imported "scripts", not "python scripts". The necessary scripts do appear now. However, when trying to program the processor, I get the message that A file in the JLink path cannot be found. I didn't really change anything there. How do I set the JLink path?
谢谢，
枪
嗨ghschwab，
您有定制董事会，或者您正在使用我们的任何DKS？
您能否请重新安装该工具并用干净的SDK目录尝试它？请删除.metadata文件夹。
谢谢，PM_Dialog
Hi,
谢谢您的答复。
与此同时，我重新安装了所有内容并从干净的板岩开始。我能够导入项目并立即编译。
I am also able to program the device, but when trying to debug it, it hangs in the Reset Handler in the file "startup_AMRCM0.S". We have a custom board.
Do you have any recommendations what I could try?
该软件用DA14680在先前版本的板上工作。除了编程时选择正确的芯片，是否有其他步骤可以切换到DA14682？
Thank you,
枪
嗨ghschwab，
If you run the project without the debugger attached, is it running properly? Are you using any of the SDK examples?
是否有可能分享屏幕截图？
谢谢，PM_Dialog
Hi,
似乎似乎没有完全运行，因为我看不到蓝牙设备广告。
在以前的硬件线上DA14680，它工作正常。
我没有使用SDK示例，因为这是我们的自定义硬件，我们的软件在以前的硬件上运行良好。
Are there any other steps necessary to switch to the DA14682?
我正在附上调试器的屏幕截图。
谢谢，
枪
嗨ghschwab，
Could you please if the HW designs guidelines documents (link is provided below) had been followed when the schematics/PCB was being developed, as this sounds like a hardware related issue?
此外，您是否构建了DA14682配置项目？
https://www.dialog-seminile.com/sites/default/files/an-b-061_da1468x_application_hardware_design_guidelines_v1.9.pdf.
谢谢，PM_Dialog
Hi,
I will check the hardware guidelines once again, but I assume they were followed, as everything worked fine on the previous hardware.
我检查了DA14680和DA14682的示例项目（peripherals_demo）的构建配置，但我找不到差异。您是否可以将我指出，以便为DA14682构建需要进行调整？
谢谢，
枪
Hi,
我们还经历了硬件指导方针，我们确信我们遵循一切。我正在从我们的电路图中附加摘录，可以检查您是否发现任何错误的东西？
谢谢，
枪
嗨ghschwab，
让我检查原理图，我会尽快回复你。
谢谢，PM_Dialog
Hi,
I have an update. I came across the DA14681 to DA14683 Porting Guide and followed the steps. Also, I was able to verify that the same issue appeared on a standard daughter board, so it is not hardware related.
我能够按照移植指南中描述的更改，但现在项目不会构建。这是错误：
建筑目标：Biavi + _device.elf
Invoking: Cross ARM C Linker
C:\Dialog_SDKS\DA1468x_DA15xxx_SDK_1.0.14.1081\DA1468x_DA15xxx_SDK_1.0.14.1081\sdk\interfaces\ble_stack\DA14683-00-Debug\libble_stack_da14683_00.a(rom_patch.o): In function `patched_hci_command_handler':
/home/build/workspace/sdk680/release_build_manual/artifacts/tmp/blex_stack/sdk/interfaces/ble_stack/da14683-00-release/../src/rom_patch/rom_patch.c:1721：未定义的参考`hci_command_handler'
./sdk/ble/src/stack/plf/black_orca/src/arch/main/ble/arch_main.o：在function`ble_platform_initialization'中：
C：/dialog_sdks/da1468x_da15xxx_sdk_1.0.14.1081/da1468x_da15xxx_sdk_1.0.14.1081/sdk/interfaces/ble/src/stack/plf/black_orca/src/arch/main/ble/arch_main.c：931：未定义引用`ble_tx_desc_data_user'
C:/Dialog_SDKS/DA1468x_DA15xxx_SDK_1.0.14.1081/DA1468x_DA15xxx_SDK_1.0.14.1081/sdk/interfaces/ble/src/stack/plf/black_orca/src/arch/main/ble/arch_main.c:931: undefined reference to `BLE_TX_DESC_CNTL_USER'
c：/dialog_sdks/da1468x_da15xxx_sdk_1.0.14.1081/da1468x_da15xxx_sdk_1.0.14.1081/sdk/interfaces/ble/src/stack/plf/black_orca/src/arch/main/ble/arch_main.c：931：未定义的参考`llm_le_adv_dummy_idx'
C：/dialog_sdks/da1468x_da15xxx_sdk_1.0.14.1081/da1468x_da15xxx_sdk_1.0.14.1081/sdk/interfaces/ble/src/stack/plf/clack_orca/src/arch/main/ble/arch_main.c：931：未定义引用给`llm_le_scan_con_req_adv_dir_idx'
C：/diaLog_sdks/da1468x_da15xxx_sdk_1.0.14.1081/da1468x_da15xxx_sdk_1.0.14.1081/sdk/interfaces/ble/src/stack/plf/black_orca/src/arch/main/ble/arch_main.c：931：未定义的参考`llm_le_scan_rsp_idx'
C：/dialog_sdks/da1468x_da15xxx_sdk_1.0.14.1081/da1468x_da15xxx_sdk_1.0.14.1081/sdk/interfaces/ble/src/stack/plf/black_orca/src/arch/main/ble/arch_main.c：931：未定义的参考`llm_le_adv_idx'
C:/Dialog_SDKS/DA1468x_DA15xxx_SDK_1.0.14.1081/DA1468x_DA15xxx_SDK_1.0.14.1081/sdk/interfaces/ble/src/stack/plf/black_orca/src/arch/main/ble/arch_main.c:931: undefined reference to `rom_hci_cmd_desc_root_tab'
。/sdk/ble/src/stack/plf/black_orca/src/arch/main/ble/jump_table.o:(.rodata.rom_func_addr_table_var+0x10c): undefined reference to `llc_le_length_conn_init_func'
。/sdk/ble/src/stack/plf/black_orca/src/arch/main/ble/jump_table.o:(.rodata.rom_func_addr_table_var+0x128): undefined reference to `smpc_public_key_exchange_start_func'
。/sdk/ble/src/stack/plf/black_orca/src/arch/main/ble/jump_table.o:(.rodata.rom_func_addr_table_var+0x12c): undefined reference to `smpc_dhkey_calc_ind_func'
./sdk/ble/src/stack/plf/black_orca/src/arch/main/ble/jump_table.o::(.rodata.rom_func_addr_table_var+0x130）：未定义的参考`smpm_ecdh_key_create_func'
collect2.exe：错误：LD返回1个退出状态
制作：*** [biavi + _device.elf]错误1
我该怎么办？
谢谢，
枪
Hi,
another update:
在选择正确的ROM.SYMBOLS文件（指南中未描述）后，项目现在编译。
但是，它仍然显示在开始时完全相同的行为，它停止在我们的自定义硬件和子板上的重置处理程序中。仍然必须缺少配置步骤。
嗨ghschwab，
Thanks for the update. This sounds like a software related issue. Could you please give a try with one of the SDK1 examples? Are you able to replicate this? Additionally, could you please share a screenshot showing where the code freezes in the bug mode?
谢谢，PM_Dialog
Hi,
我能够在对话框子板和硬件上运行firewerals_demo。但是，PXP_Reporter演示不编译（请参阅附图）。
The error message is:
Building target: pxp_reporter.elf
Invoking: Cross ARM C Linker
C：/ Diasemi / SmartsnippetsStudio / GCC / 4_9-2015Q1 / Bin /../ Lib / GCC / ARM-None-EABI / 4.9.3 /../../../../ ARM-None-EABI /bin / ld.exe：无法打开链接器脚本文件c：\ users \ ghschwab.gft \ workspace_smartsnippets_sdk1.0.14 \ pxp_reporter / da14683-00-debug_qspi / mem.ld：Account
每次都是相同的，pureinals_demo works，pxp_reporter不编译，我们自己的软件将编译但未正确运行。
I am attaching a screenshot where our our app is stuck in the debugger.
I would be happy to send you a copy of the project, but it is too bit. Is there another way to send it to you?
谢谢，
枪
嗨ghschwab，
此错误的最可能原因是因为安装程序未生成链接器脚本以使项目构建完成。在发生实际构建之前，SmartSnippets Studio（SST）应从MEM.LD.H文件生成链接器脚本，并在“构建文件夹中构建一个MEM.LD文件”。在您的情况下，上述文件永远不会构建，因此该工具无法找到mem.ld文件。这可能是由于几个原因，就像makefile.targets文件不在项目目录中，或缺少的配置等。似乎SSS的安装具有问题，或者您没有正确导入项目。请注意，SDK与SSS一起使用框中而无需任何其他配置。由于您已正确安装该工具，因此所有项目都应在框中编译。此外，您已看到的这种错误可能与您的工作区有关。我建议您按照以下步骤操作：
谢谢，PM_Dialog