<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>dfu-cc.proto output manually adjusted?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/23907/dfu-cc-proto-output-manually-adjusted</link><description>I was redefining the init packet and when it came time to generate the nano-pb files, it looks like there is a fair amount of difference in the newly auto generated pb.c and pb.h files. Since I ran into problems installing modules necessary to follow</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 04 Aug 2017 09:09:36 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/23907/dfu-cc-proto-output-manually-adjusted" /><item><title>RE: dfu-cc.proto output manually adjusted?</title><link>https://devzone.nordicsemi.com/thread/94095?ContentTypeID=1</link><pubDate>Fri, 04 Aug 2017 09:09:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:df5aa534-f466-4660-a9ee-8b8abdfafc71</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;@jeffs: You can find it, &lt;code&gt;camel_case_splitter.py&lt;/code&gt;, in the \external\nano-pb\generator folder.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: dfu-cc.proto output manually adjusted?</title><link>https://devzone.nordicsemi.com/thread/94096?ContentTypeID=1</link><pubDate>Thu, 03 Aug 2017 18:19:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:03a8127d-0dde-4c3b-af6e-8fcc8e4c65f2</guid><dc:creator>jeffs</dc:creator><description>&lt;p&gt;Thanks, Bjørn.&lt;/p&gt;
&lt;p&gt;Care to share the script?  I didn&amp;#39;t see it in the source distribution. It might be helpful for customers if it was released with nRFUtil source and mentioned in the docs, or, maybe even better, use an adapter header file to redefine them instead of modifying the tool&amp;#39;s output file directly.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: dfu-cc.proto output manually adjusted?</title><link>https://devzone.nordicsemi.com/thread/94094?ContentTypeID=1</link><pubDate>Thu, 03 Aug 2017 13:38:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:279e9f5c-f3c7-433a-aa2d-1e6bd9377b11</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;Hi Jeffs,&lt;/p&gt;
&lt;p&gt;you are correct, the files are modified after they are generated using the , i.e. we run a CamelCase splitter script to align it the rest of the SDK, i.e. with our internal code standard.&lt;/p&gt;
&lt;p&gt;Best regards&lt;/p&gt;
&lt;p&gt;Bjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>