OBOn Mon, Jul 13, 2015 at 08:36:14AM +0530, Rupin Chheda wrote: > This is an incredible amount of information and help!
Yay! :) > Nordic documentation is expected to be up to date? Should I also start a > thread at Nordic? Sounds good. It'd be good to know if there is documentation elsewhere that we should be referring to. It would also be possible for openocd to deal with unknown HWIDs more pragmatically. The CONFIG registers in nrf51 also include CODEPAGESIZE and CODESIZE configuration registers, which together tell the flash size. We could read this if the HWID lookup fails, and work out flash size that way. (I think using HWID is still preferable when known because the chip revision tells you which of the errata might apply. At the moment I don't think openocd relies on this for anything though, there are errata workarounds in openocd but they're applied without checking revision as they don't cause any side effects on later chip revisions.) I don't have any time to write a patch for this at the moment, but if you happened to then I think it'd be a worthwhile addition. Otherwise I'll try and remember to revisit it the next time I power up an nrf51. :) Angus ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
