I am trying to run the BLE barebone application from the SDK example projects on a custom 585 board. I have run it successfully on the 585 daughter board with the Pro dev kit, and I'm now connecting my custom board to the dev kit. The DA14585 is correctly recognized by the J-link interface, and SmartSnippets can detect it as the correct device. Every time I start a debug session and run the code, it breaks in the hard fault handler. I've stepped through the code, and the fault seems to be happening during the system_init() call, specifically inside arch_rom_init() on this line:
memcpy(hci_cmd_desc_root_tab, rom_hci_cmd_desc_root_tab, 48);
我看到了这些variables being passed into memcpy are, and Keil doesn't seem to think they are defined anywhere. I'm not sure what could be causing this fault. Any help or direction on how to track this down would be appreciated.
(I don't have any external flash on my board, but I don't think this example is using external flash anyway.)
Thanks
Hi erichn,
What's the silicon that you use? For DA14585 silicon A-B the proper SDK version is 6.0.2 , in case of DA14585 silicon A-C is the SDK 6.0.4 . The most probably cause for your issue is this , please check it.
BR,
STS_Dialog.
Dialog,
I have the same issue as above. I am using SDK 6.0.4 on a custom board with DA14585 00000 1723NCAA. I am trying to run the barebone example (no changes in the code).
Hi jlabuac,
If the markings on the SoC indicate a 14585 00000 as far as i can tell that means that the chip is an AC silicon which is the latest silicon version and that probably there is something wrong with the custom board that you have and not the silicon version of the SoC. Have you tried to run the 6.0.2 and check if the hardfault occurs ?
Thanks MT_dialog
Hi Dialog,
Yes, I've also tried using the 6.0.2 but I am also having a hardfault. May I know the possible areas that I should look at on the hardware pertaining to the hardfault?
Hi jlabuac,
Well there's no standard place to look in case the hardfault occurs due to faulty custom board, since the reasons for that can be quite a few, what i can suggest is to check where the hardfault exactly occurs and after that perhaps you can have an idea what might be the problem.
Thanks MT_dialog