After spending an entire day not being able to get the example projects to run on DA1585 Pro kit I found these two posts hinting at the problem
https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bl...
https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bl...
原来我秀康AB和使用6.02nstead of 6.04 worked for pillars 1-6.
However the All in One (pillar 7) still does not work for me with 6.02 and 14585. It goes to watch dog after entering arch_rom_init().
(1) Is my problem with pillar 7 due to remaining silicon / SDK issues?
(2) WHERE was this information about 6.02 and 6.04 given? I may have missed it.
Thanks
Device:
Hi nvoster,
1) I suppose that you are using a pro kit, so try to attach the flash of the motherboard, the reason that the NMI occurs is because the device apprently is trying to communicate with an external flash and there is no flash attached. The interrupt occurs in the bond_db_init() function, at least on my side.
2) There isn't any official announcement or document explaining this about the AB versions.
Thanks MT_dialog
Hi MT
(updated)
Re 1) Thank you for pointing out the crash point. Using cache only for DB bonding solves the problem for now.
#undef USER_CFG_APP_BOND_DB_USE_SPI_FLASH
#undef USER_CFG_APP_BOND_DB_USE_I2C_EEPROM
Re 2) Based upon your overall product features I've already selected your new chipsets for 3 new customer projects but I want you all to know this is the second time I've been burned pretty hard by an undocumented issue. Also should we be doing dev with AB silicon? Say I do the dev on 6.0.2 then order 10k for parts and they're AC or greater. Won't I have incompatible firmware?
Thanks
Hi nvoster,
Yes, the 6.0.2 SDK will be incompatible with the new SDK and its not advised to do your development on this SDK but on the latest with new silicon.
A mail is sent to the registered email address.
Thanks MT_dialog