⚠️ Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.wsdof.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
Because i see through your posts that you have different kind of issues when running a validated fw on a custom board, and as far as i can understand all the issues are quite random, when running the fw, either you get a hardfault, or you are not able to access the OTP, or you get the above issue (which is a memory corruption issue, apparently the vector table is corrupted), i can only assume that the issue is the custom board that you are using and most probably a soldering or assembly issue, that can cause issues on the supply voltages and what you see are side-effects, you can check the VDCDC voltage in order to verify that this is ok. Also perhaps there is an issue with the XTAL16 that you are using on the custom board. Additionally perhaps there are issues with the JTag connections and the downloaded code is corrupted, you can check that by instructing keil to perform a verification to the downloded code "Options for target" -> "Debug" -> "Settings" check the "Verify Code Download".
Hi jlabuac,
Because i see through your posts that you have different kind of issues when running a validated fw on a custom board, and as far as i can understand all the issues are quite random, when running the fw, either you get a hardfault, or you are not able to access the OTP, or you get the above issue (which is a memory corruption issue, apparently the vector table is corrupted), i can only assume that the issue is the custom board that you are using and most probably a soldering or assembly issue, that can cause issues on the supply voltages and what you see are side-effects, you can check the VDCDC voltage in order to verify that this is ok. Also perhaps there is an issue with the XTAL16 that you are using on the custom board. Additionally perhaps there are issues with the JTag connections and the downloaded code is corrupted, you can check that by instructing keil to perform a verification to the downloded code "Options for target" -> "Debug" -> "Settings" check the "Verify Code Download".
Thanks MT_dialog
Hi Dialog,
Thanks for the direction. We will look into this and let you know the update.