<?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>Programming nRF9E5 through AT25320B</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/28229/programming-nrf9e5-through-at25320b</link><description>Hello, 
 I understand the nRF9E5 is programmed through the externally attached AT25320B, ok. I understand three bytes are appended to the .hex file for the 8051. Since I am programming the AT25320B from the hex file do I need to decipher the .hex file</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 13 Dec 2017 11:37:31 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/28229/programming-nrf9e5-through-at25320b" /><item><title>RE: Programming nRF9E5 through AT25320B</title><link>https://devzone.nordicsemi.com/thread/111489?ContentTypeID=1</link><pubDate>Wed, 13 Dec 2017 11:37:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:09c7522d-47b0-4c0e-8317-149c06457e05</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;By the way, I assume you are aware there is a utility called EEPREP, which adds the header bytes for you?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Programming nRF9E5 through AT25320B</title><link>https://devzone.nordicsemi.com/thread/111488?ContentTypeID=1</link><pubDate>Wed, 13 Dec 2017 11:36:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e07354c5-2efb-4e5f-9007-4d5bd0a4d4eb</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;You are correct of course. I misunderstood your question.&lt;/p&gt;
&lt;p&gt;0x0B means the version and reserved fields are 0, while the SPEED field is 1 and the XO_FREQ field is 3, which you have correctly decoded to mean an SPI speed of 1MHz max and a crystal frequency of 16MHz.&lt;/p&gt;
&lt;p&gt;The final 3 bytes before the checksum are the first 3 bytes of the program, executing a jump to address 0x0928 (if my rusty 8051 assembler knowledge serves me right...)&lt;/p&gt;
&lt;p&gt;Sorry for the confusion, and best regards ;)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Programming nRF9E5 through AT25320B</title><link>https://devzone.nordicsemi.com/thread/111487?ContentTypeID=1</link><pubDate>Tue, 12 Dec 2017 19:44:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b91af8ae-0aa2-408a-92c5-2daf96058026</guid><dc:creator>Cy</dc:creator><description>&lt;p&gt;Thank you for your response, much appreciated! I have looked at table 60, but I am not able to see another way to interpret it.
The starting line of the hex file, an example range demo
:060000000B0309020928B0
The hex interpretation is 6 bytes on the line, start programming at address 0x0000, with the (0x00) data: 0x0B,0x03,0x09,0x02,0x09,0x28.
The first three bytes into the AT25320B are 0x0B, 0x03, and 0x09
0x0B: Speed = 1MHz (eeprom) XO_FREQ = 16MHz
0x03: Offset to start User program - byte 3.
0x09: number of 256 byte blocks in the user program.&lt;/p&gt;
&lt;p&gt;In this interprectation I am interpreting the hex file and only programming the pertinent bits into the EEprom.&lt;/p&gt;
&lt;p&gt;If I am wrong in my interpretation of Table 60, please help me understand, thank you!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Programming nRF9E5 through AT25320B</title><link>https://devzone.nordicsemi.com/thread/111490?ContentTypeID=1</link><pubDate>Tue, 12 Dec 2017 11:59:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:754f3be5-935f-46c1-a3d1-4d2e5ba419a8</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Have you read chapter 21.2 in the &lt;a href="http://www.nordicsemi.com/index.php/chi/nordic/download_resource/10455/2/37257538/2441"&gt;nRF9E5 Product Specification&lt;/a&gt;?&lt;/p&gt;
&lt;p&gt;Table 60 shows how the first three bytes should be coded. The first byte is used for the Version, Speed and XO_FREQ fields. The second byte is the code start offset, and the third byte is the number of 256 byte blocks used by the program.&lt;/p&gt;
&lt;p&gt;In other words you shouldn&amp;#39;t split up the fields like you did in your example.&lt;/p&gt;
&lt;p&gt;Best regards&lt;br /&gt;
Torbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>