<?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>nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/84461/nrfjprog-verify-fails-with-chiperase</link><description>Hi, 
 We&amp;#39;ve been using nrfjprog with no particular issue for a while now. Usually to fully flash a chip (whether it&amp;#39;s for a complete re-flash or for a new chip) we run those 2 steps: 
 nrfjprog -f nrf52 --eraseall nrfjprog -f nrf52 --program firmware</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 14 Feb 2022 15:56:10 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/84461/nrfjprog-verify-fails-with-chiperase" /><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/352954?ContentTypeID=1</link><pubDate>Mon, 14 Feb 2022 15:56:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cf265dfc-c9b9-464c-a436-3757278b3fa1</guid><dc:creator>zilhk</dc:creator><description>&lt;p&gt;Thank you for the information.&lt;br /&gt;Setting the watchdog timer behaviour to &amp;quot;NRF_WDT_BEHAVIOUR_PAUSE_SLEEP_HALT&amp;quot; fixes the issue!&amp;nbsp;&lt;span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/1f642.svg" title="Slight smile"&gt;&amp;#x1f642;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The WDT is started right at the beginning of our &amp;quot;main()&amp;quot; function.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/352937?ContentTypeID=1</link><pubDate>Mon, 14 Feb 2022 14:55:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d41b3409-acdd-40b5-841f-ef39ba9d91d7</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;As you can read in the&amp;nbsp;&lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.nrf52832.ps.v1.1%2Fwdt.html"&gt;documentation&lt;/a&gt;, by default, the watchdog will be active counting down the down-counter while the CPU is sleeping and when it is halted by the debugger. You can also read more about&amp;nbsp;&lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.nrf52832.ps.v1.1%2Fpower.html&amp;amp;anchor=unique_961802881"&gt;reset behavior.&lt;/a&gt;&lt;br /&gt;In your case, the watchdog timer seems to be running while halted. It may be started during the erase operation and finished before the erase operation is performed, thereby causing the error.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;The solution would be either to use two-way workaround which already works well for you, or to disable (turn off) the watchdog timer while debugging.&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/352907?ContentTypeID=1</link><pubDate>Mon, 14 Feb 2022 13:38:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:48dae099-53c7-45a8-b78f-a90bdae83859</guid><dc:creator>zilhk</dc:creator><description>&lt;p&gt;Hi Dejan,&lt;/p&gt;
&lt;p&gt;I believe so, we have a call to &amp;quot;nrf_drv_wdt_init()&amp;quot; with NRF_DRV_WDT_DEAFULT_CONFIG passed as the config.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m realizing now that this is a &amp;quot;legacy&amp;quot; feature.&lt;/p&gt;
&lt;p&gt;Do you recommend switching to something else?&lt;/p&gt;
&lt;p&gt;Thanks.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/352872?ContentTypeID=1</link><pubDate>Mon, 14 Feb 2022 12:37:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:59667e73-9135-402b-bcfe-d485e4c941d1</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;Are you using a watchdog timer in your application?&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/352861?ContentTypeID=1</link><pubDate>Mon, 14 Feb 2022 12:06:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c2c53924-b8c8-4884-89ce-4d898b39425d</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;No problem.&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/352532?ContentTypeID=1</link><pubDate>Fri, 11 Feb 2022 10:05:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:aa544625-84c6-47e7-aed5-87d3d46f641e</guid><dc:creator>zilhk</dc:creator><description>&lt;p&gt;Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/352530?ContentTypeID=1</link><pubDate>Fri, 11 Feb 2022 10:03:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5d08eaf3-253d-445a-b3f5-ae1b3ef9ed6e</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;I have&amp;nbsp;asked internally and waiting for the reply.&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/352268?ContentTypeID=1</link><pubDate>Thu, 10 Feb 2022 09:49:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:136c5878-2942-47e5-8045-1d435f870e22</guid><dc:creator>zilhk</dc:creator><description>&lt;p&gt;Thank you!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/352070?ContentTypeID=1</link><pubDate>Wed, 09 Feb 2022 12:46:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:02a7580e-21ce-4b62-8ace-a49ca98e4dc1</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;Thank you for the hex file.&lt;br /&gt;&lt;br /&gt;I have managed to reproduce your problem.&lt;br /&gt;I&amp;#39;ll come back to you when I get more information about a potential solution.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/351846?ContentTypeID=1</link><pubDate>Tue, 08 Feb 2022 14:13:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bef28005-54ec-4410-ad2e-e200dd6f6618</guid><dc:creator>zilhk</dc:creator><description>&lt;p&gt;Sure, here you go.&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/full_5F00_firmware_5F00_factory.zip"&gt;devzone.nordicsemi.com/.../full_5F00_firmware_5F00_factory.zip&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/351835?ContentTypeID=1</link><pubDate>Tue, 08 Feb 2022 13:57:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e7a7de76-3038-49c1-91de-586035e0df19</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;If possible, could you please provide your flash (hex) file?&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/351734?ContentTypeID=1</link><pubDate>Tue, 08 Feb 2022 10:12:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1455f9e1-faa3-4590-a81d-f4045fbf87f1</guid><dc:creator>zilhk</dc:creator><description>&lt;p&gt;Here it is.&lt;br /&gt;The 0x2e000 address is the beginning of the flash area we use for fstorage. Our firmware modifies it on each boot. I suppose it fails because this area is not cleared beforehand.&lt;br /&gt;&lt;br /&gt;&lt;code&gt;&amp;nbsp;nrfjprog -f nrf52 --program _build/full_firmware_factory.hex --reset --log &lt;/code&gt;&lt;br /&gt;&lt;code&gt;--verify&lt;/code&gt;&lt;br /&gt;&lt;code&gt;Parsing image file.&lt;/code&gt;&lt;br /&gt;&lt;code&gt;Verifying programming.&lt;/code&gt;&lt;br /&gt;&lt;code&gt;ERROR: [&amp;nbsp; nRF52] - Data does not match in address range [0x0002e000-0x0002e05c] (Flash)&lt;/code&gt;&lt;br /&gt;&lt;code&gt;ERROR: [&amp;nbsp; nRF52] - Expected byte value 0x39 but read 0x10 at address 0x0002e000.&lt;/code&gt;&lt;br /&gt;&lt;code&gt;ERROR: [&amp;nbsp; nRF52] - Flash verification failed.&lt;/code&gt;&lt;br /&gt;&lt;code&gt;ERROR: [&amp;nbsp; nRF52] - Failed while verifying file _build/full_firmware_factory.hex.&lt;/code&gt;&lt;br /&gt;&lt;code&gt;ERROR: Write verify failed.&lt;/code&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/351731?ContentTypeID=1</link><pubDate>Tue, 08 Feb 2022 10:06:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:29779dd0-cece-451d-980a-5002a99d6d71</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;What exactly is the output of&amp;nbsp;&lt;span&gt;&amp;nbsp;&amp;quot;nrfjprog -f nrf52 --program _build/full_firmware_factory.hex&amp;nbsp; --verify --reset&amp;quot; if you don&amp;#39;t run&amp;nbsp;&amp;quot;nrfjprog -f nrf52 --eraseall&amp;quot; beforehand?&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/351721?ContentTypeID=1</link><pubDate>Tue, 08 Feb 2022 09:50:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1d0162c6-fa98-4dbc-b686-3e1b5857ba93</guid><dc:creator>zilhk</dc:creator><description>&lt;p&gt;Yes but only if&amp;nbsp; &amp;quot;&lt;span&gt;nrfjprog -f nrf52 --eraseall&lt;/span&gt;&amp;quot; is run first&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/351718?ContentTypeID=1</link><pubDate>Tue, 08 Feb 2022 09:45:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b1d3bf64-7fb2-408d-93ff-255502a0ddc3</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;What happens if you don&amp;#39;t use --sectorerase&amp;nbsp; in &amp;quot;nrfjprog -f nrf52 --program _build/full_firmware_factory.hex --sectorerase --verify --reset&amp;quot;. Does it work then?&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/351614?ContentTypeID=1</link><pubDate>Mon, 07 Feb 2022 15:58:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c32b3955-5ed8-4340-879f-df67d90d9956</guid><dc:creator>zilhk</dc:creator><description>&lt;p&gt;I&amp;#39;ve also tried with the --verify flag, it works as long as I&amp;#39;m not using --chiperase&lt;/p&gt;
&lt;p&gt;&lt;span&gt;nrfjprog -f nrf52 --eraseall&lt;br /&gt;nrfjprog -f nrf52 --program&amp;nbsp;_build/full_firmware_factory.hex --sectorerase --verify --reset&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;and&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;nrfjprog -f nrf52 --eraseall&lt;br /&gt;nrfjprog -f nrf52 --program&amp;nbsp;_build/full_firmware_factory.hex --verify --reset&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;both work fine&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/351610?ContentTypeID=1</link><pubDate>Mon, 07 Feb 2022 15:48:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0374d8de-1b29-4c41-bb5e-2c82b80b6fe4</guid><dc:creator>zilhk</dc:creator><description>&lt;p&gt;Yes, exactly.&lt;br /&gt;Thanks for checking this out!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/351608?ContentTypeID=1</link><pubDate>Mon, 07 Feb 2022 15:35:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:00c2ccb3-e59b-4502-87eb-8800c87dd677</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;Thank you for the log file.&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/351606?ContentTypeID=1</link><pubDate>Mon, 07 Feb 2022 15:34:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bae11374-7f7d-4e9c-8a90-98cdb70d807a</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The command &amp;quot;&lt;span&gt;nrfjprog -f nrf52 --program&amp;nbsp;_build/full_firmware_factory.hex --sectorerase --reset&lt;/span&gt;&amp;quot; works both with and without --sectorerase. &lt;br /&gt;The command you were running with errors was &amp;quot;&lt;span&gt;nrfjprog -f nrf52 --program&amp;nbsp;_build/full_firmware_factory.hex --chiperase --verify --reset --log&lt;/span&gt;&amp;quot;&lt;br /&gt;Is this correct?&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/351596?ContentTypeID=1</link><pubDate>Mon, 07 Feb 2022 15:09:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cb574d64-b0be-4168-ac8b-ee5a2a666058</guid><dc:creator>zilhk</dc:creator><description>&lt;p&gt;Yes, tried again and had no issue without using --sectorerase&lt;br /&gt;&lt;br /&gt;Just realized I didn&amp;#39;t read your question properly and deleted my earlier reply, sorry.&lt;/p&gt;
&lt;p&gt;Filename is `_build/full_firmware_factory.hex` but I&amp;#39;ve edited my post and replaced it with just firmware.hex&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/351591?ContentTypeID=1</link><pubDate>Mon, 07 Feb 2022 15:03:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bfe64a20-6a5a-45d3-aa6a-455882b8bd9d</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;No errors when using nrfjprog without --sectorerase?&lt;br /&gt;What about hex file name?&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/351589?ContentTypeID=1</link><pubDate>Mon, 07 Feb 2022 15:02:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dc5ae97d-e7b5-45de-8a1e-121538476adc</guid><dc:creator>zilhk</dc:creator><description>&lt;p&gt;Yes filename is `_build/full_firmware_factory.hex` but I&amp;#39;ve edited my post and replaced it with just firmware.hex for simplicity (I guess that failed!)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/351588?ContentTypeID=1</link><pubDate>Mon, 07 Feb 2022 15:01:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5b10d0cc-d7a4-4022-aec5-864a5ea42fd4</guid><dc:creator>zilhk</dc:creator><description>&lt;p&gt;Here is the log, first attempt worked, second failed&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/3808.log.log"&gt;devzone.nordicsemi.com/.../3808.log.log&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/351587?ContentTypeID=1</link><pubDate>Mon, 07 Feb 2022 15:00:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6e51bee4-07d8-440b-935b-5661741d8e98</guid><dc:creator>zilhk</dc:creator><description>&lt;p&gt;Hi! Yes, it works flawlessly when doing it 2 steps.&lt;br /&gt;&lt;br /&gt;It&amp;#39;s actually what I&amp;#39;ve been doing for months before I tried to use --chiperase&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrfjprog verify fails with chiperase</title><link>https://devzone.nordicsemi.com/thread/351575?ContentTypeID=1</link><pubDate>Mon, 07 Feb 2022 14:29:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5ab06c14-bf47-4819-a5fa-795a6fe376b1</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;What is the actual name of the hex file you want to build - is it _build/full_firmware_factory.hex?&lt;br /&gt;Could you try using &amp;quot;&lt;span&gt;nrfjprog -f nrf52 --eraseall&amp;quot; and&lt;/span&gt;&amp;nbsp;&amp;quot;nrfjprog -f nrf52 --program firmware.hex --reset&amp;quot; (without --sectorerase)? Are there any errors in that case?&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>