<?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>Customising a bluetooth Zephyr sample</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/91010/customising-a-bluetooth-zephyr-sample</link><description>Hi, 
 I am currently developing with the nRF52 DK (nRF52832 SoC) and the nRF52833 DK (nRf52833 SoC). I have built and flashed the Bluetooth: Peripheral HT sample from Zephyr to both boards successfully. I have tested the application with an Android mobile</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 23 Aug 2022 01:07:39 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/91010/customising-a-bluetooth-zephyr-sample" /><item><title>RE: Customising a bluetooth Zephyr sample</title><link>https://devzone.nordicsemi.com/thread/382780?ContentTypeID=1</link><pubDate>Tue, 23 Aug 2022 01:07:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d767898a-7192-4763-996f-40b2ce4f7589</guid><dc:creator>adam_atmo</dc:creator><description>&lt;p&gt;Great, thank you Simon.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Customising a bluetooth Zephyr sample</title><link>https://devzone.nordicsemi.com/thread/382719?ContentTypeID=1</link><pubDate>Mon, 22 Aug 2022 13:56:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6bc33868-b07f-4f25-bc2b-975253e1b2e9</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;A) When a config has &amp;quot;dependencies&amp;quot; it is dependent on those listed configurations to be valid in a project. I&amp;#39;m not sure how much of a definition you&amp;#39;re looking for to be honest.&lt;/p&gt;
&lt;p&gt;C)&amp;nbsp;Okay,&amp;nbsp;I double checked this on my end, and there seems to be a&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.0.2/nrf/known_issues.html#softdevice-controller"&gt; known issue here&lt;/a&gt;, that was just recently added to the main branch. So if you&amp;#39;re using NCS version 2.0.2 or older these&amp;nbsp;&lt;span&gt;BT_CTLR_TX_PWR won&amp;#39;t work properly, and you have to use the dynamic TX power control. Sorry about that. So either update to the main branch or use the dynamic power control.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;2. As long as you also enable the necessary configs,&amp;nbsp;&lt;strong&gt;CONFIG_BT_CTLR_PHY_CODED=y&amp;nbsp;&lt;/strong&gt;&amp;amp;&amp;nbsp;&lt;strong&gt;CONFIG_BT_EXT_ADV=y&lt;/strong&gt;, I believe so. But make sure that you don&amp;#39;t have any other &amp;quot;bt_le_adv_param&amp;quot; structs in the sample that can overwrite or conflict with this.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Customising a bluetooth Zephyr sample</title><link>https://devzone.nordicsemi.com/thread/382550?ContentTypeID=1</link><pubDate>Mon, 22 Aug 2022 02:30:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b7a044d4-7c58-4eeb-9667-fccbf6fb994d</guid><dc:creator>adam_atmo</dc:creator><description>&lt;p&gt;Hi Simon,&lt;/p&gt;
&lt;p&gt;1. Thank you - I have a few questions/issues regarding this:&lt;/p&gt;
&lt;p&gt;A. What is the definition of a dependency with regards to a .conf file?&lt;/p&gt;
&lt;p&gt;B. Must the dependency be added into the prj.conf file? If so, this does not solve the problem.&amp;nbsp;There is an error when setting&amp;nbsp;&lt;strong&gt;CONFIG_HAS_HW_NRF_RADIO_TX_PWR_HIGH&lt;/strong&gt;=y. This seems to be an issue that was also identified &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/68850/config_bt_ctlr_tx_pwr_plus_8-has-no-effect-while-advertising"&gt;in this post&lt;/a&gt; but no clear answer was suggested.&lt;/p&gt;
&lt;p&gt;C. Are you sure it is possible to configure the TX power using the prj.conf&amp;nbsp;alone (this would be most convenient) or do additional functions need to be used&amp;nbsp;in the source code?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;2. I am referring to the snippet that you posted -&amp;nbsp;&lt;span&gt;&amp;nbsp;can I&amp;nbsp;add this &lt;strong&gt;&lt;em&gt;create_advertising_coded&lt;/em&gt;&lt;/strong&gt;&amp;nbsp;function into the source code in addition to the existing advertising functions in the &lt;/span&gt;&lt;a href="https://docs.zephyrproject.org/2.6.0/samples/bluetooth/peripheral_ht/README.html"&gt;Bluetooth: Peripheral HT&lt;/a&gt;&lt;span&gt;&amp;nbsp;sample&lt;/span&gt;&lt;span&gt;?&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thanks again for the assistance,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Adam&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Customising a bluetooth Zephyr sample</title><link>https://devzone.nordicsemi.com/thread/382172?ContentTypeID=1</link><pubDate>Thu, 18 Aug 2022 08:30:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f77491b2-6c9b-4aa1-be88-db8e3af5c274</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi Adam&lt;/p&gt;
&lt;p&gt;1. Indeed, you also need to include the dependencies for a config you set, so you also have to set&amp;nbsp;&lt;strong&gt;CONFIG_HAS_HW_NRF_RADIO_TX_PWR_HIGH=&lt;/strong&gt;Y&amp;nbsp;in your config file as well.&lt;/p&gt;
&lt;p&gt;2. What is &amp;quot;this function&amp;quot;?&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Customising a bluetooth Zephyr sample</title><link>https://devzone.nordicsemi.com/thread/381996?ContentTypeID=1</link><pubDate>Wed, 17 Aug 2022 11:29:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:31a2ad69-a0bc-44a1-8d69-d458a5e7e63c</guid><dc:creator>adam_atmo</dc:creator><description>&lt;p&gt;Thanks Simon,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;1. I did try that and it doesn&amp;#39;t seem to change the TX power value when I tested it. I added the following line into the prj.conf file:&amp;nbsp;&lt;span class="pre"&gt;&lt;strong&gt;CONFIG_BT_CTLR_TX_PWR_PLUS_8=y&lt;/strong&gt;. I get the following message&amp;nbsp;next to this line:&amp;nbsp;&lt;em&gt;In build_833: n&lt;/em&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="pre"&gt;Furthermore, I get the following problem message&amp;nbsp;in VS Code:&amp;nbsp;&lt;/span&gt;&lt;span class="pre"&gt;&lt;em&gt;CONFIG_BT_CTLR_TX_PWR_PLUS_8 was assigned the value y, but got the value n. Missing dependencies: HAS_HW_NRF_RADIO_TX_PWR_HIGH&lt;/em&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="pre"&gt;2. Can I&amp;nbsp;add this function into the source code in addition to the existing advertising functions in the &lt;a href="https://docs.zephyrproject.org/2.6.0/samples/bluetooth/peripheral_ht/README.html"&gt;Bluetooth: Peripheral HT&lt;/a&gt;&lt;span&gt;&amp;nbsp;sample&lt;/span&gt;?&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="pre"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="pre"&gt;Thanks very much,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="pre"&gt;Adam&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Customising a bluetooth Zephyr sample</title><link>https://devzone.nordicsemi.com/thread/381980?ContentTypeID=1</link><pubDate>Wed, 17 Aug 2022 10:48:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d9768274-4e68-4e39-9888-c45a818af79b</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;1. Okay, to just set the TX power statically to +8dBm you can add the &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/kconfig/index.html#CONFIG_BT_CTLR_TX_PWR_PLUS_8"&gt;CONFIG_BT_CTLR_TX_PWR_PLUS_8 &lt;/a&gt;to the Kconfig file of your project.&lt;/p&gt;
&lt;p&gt;2. You can set up a Coded PHY advertising with something like this snippet from the &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/bluetooth/peripheral_hr_coded/README.html"&gt;peripheral_hr_coded &lt;/a&gt;sample:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;static int create_advertising_coded(void)
{
	int err;
	struct bt_le_adv_param param =
		BT_LE_ADV_PARAM_INIT(BT_LE_ADV_OPT_CONNECTABLE |
				     BT_LE_ADV_OPT_EXT_ADV |
				     BT_LE_ADV_OPT_CODED,
				     BT_GAP_ADV_FAST_INT_MIN_2,
				     BT_GAP_ADV_FAST_INT_MAX_2,
				     NULL);

	err = bt_le_ext_adv_create(&amp;amp;param, NULL, &amp;amp;adv);
	if (err) {
		printk(&amp;quot;Failed to create advertiser set (%d)\n&amp;quot;, err);
		return err;
	}

	printk(&amp;quot;Created adv: %p\n&amp;quot;, adv);

	err = bt_le_ext_adv_set_data(adv, ad, ARRAY_SIZE(ad), NULL, 0);
	if (err) {
		printk(&amp;quot;Failed to set advertising data (%d)\n&amp;quot;, err);
		return err;
	}

	return 0;
}&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Yes, the Coded PHY sample should be possible to build for the nRF52833 as well, we&amp;#39;ve just not set it up and tested it on our end, so we can&amp;#39;t add it to the sample page.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Customising a bluetooth Zephyr sample</title><link>https://devzone.nordicsemi.com/thread/381871?ContentTypeID=1</link><pubDate>Wed, 17 Aug 2022 02:39:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:120e0cc9-14c5-441d-bdf9-d1d0bab02117</guid><dc:creator>adam_atmo</dc:creator><description>&lt;p&gt;Thanks for the help Simon,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;1. That is for the HCI power control application where the TX power is modulated according to the RSSI. How can I simply set the default power to 8dBm in the&amp;nbsp;&lt;a href="https://docs.zephyrproject.org/2.6.0/samples/bluetooth/peripheral_ht/README.html"&gt;Bluetooth: Peripheral HT&lt;/a&gt;&lt;span&gt;&amp;nbsp;sample from Zephyr?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;2. Can you please be more specific as to what advertising initialization needs to change in the&amp;nbsp;&lt;a href="https://docs.zephyrproject.org/2.6.0/samples/bluetooth/peripheral_ht/README.html"&gt;Bluetooth: Peripheral HT&lt;/a&gt;&amp;nbsp;sample? Do I need to change the bt_ready function (code attached below)?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Furthermore, under requirements for the&amp;nbsp;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/bluetooth/peripheral_hr_coded/README.html"&gt;Peripheral Heart Rate Monitor with Coded PHY&lt;/a&gt;&amp;nbsp;sample, it does not support the nRF52833 DK which I am using. Surely this sample can be built for the nRF52833 as it supports Coded PHY?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;table class="highlight tab-size js-file-line-container js-code-nav-container js-tagsearch-file" data-hpc="" data-tab-size="8" data-paste-markdown-skip="" data-tagsearch-lang="C" data-tagsearch-path="samples/bluetooth/peripheral_ht/src/main.c"&gt;
&lt;tbody&gt;
&lt;tr&gt;&lt;/tr&gt;
&lt;tr&gt;
&lt;td id="LC53" class="blob-code blob-code-inner js-file-line"&gt;&lt;span class="pl-k"&gt;static&lt;/span&gt; &lt;span class="pl-k"&gt;void&lt;/span&gt; &lt;span class="pl-en"&gt;bt_ready&lt;/span&gt;(&lt;span class="pl-k"&gt;void&lt;/span&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td id="L54" class="blob-num js-line-number js-code-nav-line-number js-blob-rnum" data-line-number="54"&gt;&lt;/td&gt;
&lt;td id="LC54" class="blob-code blob-code-inner js-file-line"&gt;{&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td id="L55" class="blob-num js-line-number js-code-nav-line-number js-blob-rnum" data-line-number="55"&gt;&lt;/td&gt;
&lt;td id="LC55" class="blob-code blob-code-inner js-file-line"&gt;&lt;span class="pl-k"&gt;int&lt;/span&gt; err;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td id="L56" class="blob-num js-line-number js-code-nav-line-number js-blob-rnum" data-line-number="56"&gt;&lt;/td&gt;
&lt;td id="LC56" class="blob-code blob-code-inner js-file-line"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td id="L57" class="blob-num js-line-number js-code-nav-line-number js-blob-rnum" data-line-number="57"&gt;&lt;/td&gt;
&lt;td id="LC57" class="blob-code blob-code-inner js-file-line"&gt;&lt;span class="pl-c1"&gt;printk&lt;/span&gt;(&lt;span class="pl-s"&gt;&lt;span class="pl-pds"&gt;&amp;quot;&lt;/span&gt;Bluetooth initialized&lt;span class="pl-cce"&gt;\n&lt;/span&gt;&lt;span class="pl-pds"&gt;&amp;quot;&lt;/span&gt;&lt;/span&gt;);&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td id="L58" class="blob-num js-line-number js-code-nav-line-number js-blob-rnum" data-line-number="58"&gt;&lt;/td&gt;
&lt;td id="LC58" class="blob-code blob-code-inner js-file-line"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td id="L59" class="blob-num js-line-number js-code-nav-line-number js-blob-rnum" data-line-number="59"&gt;&lt;/td&gt;
&lt;td id="LC59" class="blob-code blob-code-inner js-file-line"&gt;&lt;span class="pl-c1"&gt;hts_init&lt;/span&gt;();&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td id="L60" class="blob-num js-line-number js-code-nav-line-number js-blob-rnum" data-line-number="60"&gt;&lt;/td&gt;
&lt;td id="LC60" class="blob-code blob-code-inner js-file-line"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td id="L61" class="blob-num js-line-number js-code-nav-line-number js-blob-rnum" data-line-number="61"&gt;&lt;/td&gt;
&lt;td id="LC61" class="blob-code blob-code-inner js-file-line"&gt;err = &lt;span class="pl-c1"&gt;bt_le_adv_start&lt;/span&gt;(BT_LE_ADV_CONN_NAME, ad, &lt;span class="pl-c1"&gt;ARRAY_SIZE&lt;/span&gt;(ad), &lt;span class="pl-c1"&gt;NULL&lt;/span&gt;, &lt;span class="pl-c1"&gt;0&lt;/span&gt;);&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td id="L62" class="blob-num js-line-number js-code-nav-line-number js-blob-rnum" data-line-number="62"&gt;&lt;/td&gt;
&lt;td id="LC62" class="blob-code blob-code-inner js-file-line"&gt;&lt;span class="pl-k"&gt;if&lt;/span&gt; (err) {&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td id="L63" class="blob-num js-line-number js-code-nav-line-number js-blob-rnum" data-line-number="63"&gt;&lt;/td&gt;
&lt;td id="LC63" class="blob-code blob-code-inner js-file-line"&gt;&lt;span class="pl-c1"&gt;printk&lt;/span&gt;(&lt;span class="pl-s"&gt;&lt;span class="pl-pds"&gt;&amp;quot;&lt;/span&gt;Advertising failed to start (err &lt;span class="pl-c1"&gt;%d&lt;/span&gt;)&lt;span class="pl-cce"&gt;\n&lt;/span&gt;&lt;span class="pl-pds"&gt;&amp;quot;&lt;/span&gt;&lt;/span&gt;, err);&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td id="L64" class="blob-num js-line-number js-code-nav-line-number js-blob-rnum" data-line-number="64"&gt;&lt;/td&gt;
&lt;td id="LC64" class="blob-code blob-code-inner js-file-line"&gt;&lt;span class="pl-k"&gt;return&lt;/span&gt;;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td id="L65" class="blob-num js-line-number js-code-nav-line-number js-blob-rnum" data-line-number="65"&gt;&lt;/td&gt;
&lt;td id="LC65" class="blob-code blob-code-inner js-file-line"&gt;}&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td id="L66" class="blob-num js-line-number js-code-nav-line-number js-blob-rnum" data-line-number="66"&gt;&lt;/td&gt;
&lt;td id="LC66" class="blob-code blob-code-inner js-file-line"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td id="L67" class="blob-num js-line-number js-code-nav-line-number js-blob-rnum" data-line-number="67"&gt;&lt;/td&gt;
&lt;td id="LC67" class="blob-code blob-code-inner js-file-line"&gt;&lt;span class="pl-c1"&gt;printk&lt;/span&gt;(&lt;span class="pl-s"&gt;&lt;span class="pl-pds"&gt;&amp;quot;&lt;/span&gt;Advertising successfully started&lt;span class="pl-cce"&gt;\n&lt;/span&gt;&lt;span class="pl-pds"&gt;&amp;quot;&lt;/span&gt;&lt;/span&gt;);&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td id="L68" class="blob-num js-line-number js-code-nav-line-number js-blob-rnum" data-line-number="68"&gt;&lt;/td&gt;
&lt;td id="LC68" class="blob-code blob-code-inner js-file-line"&gt;}&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td id="L69" class="blob-num js-line-number js-code-nav-line-number js-blob-rnum" data-line-number="69"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Customising a bluetooth Zephyr sample</title><link>https://devzone.nordicsemi.com/thread/381724?ContentTypeID=1</link><pubDate>Tue, 16 Aug 2022 09:26:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d86238ed-5d48-4b95-9956-5c54f4b98a81</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi Adam&lt;/p&gt;
&lt;p&gt;1. In &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/77753/changing-tx-power-and-phy-in-ncs-example-at-runtime"&gt;this case&lt;/a&gt;, my colleague Hung has explained how to set the TX power in the nRF Connect SDK (NCS).&lt;/p&gt;
&lt;p&gt;2. In order to enable Coded PHY, enable the following Kconfigs in your project:&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;CONFIG_BT_CTLR_PHY_CODED=y&lt;/strong&gt;&lt;br /&gt;&lt;strong&gt;CONFIG_BT_EXT_ADV=y&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;You can also check out the P&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/bluetooth/peripheral_hr_coded/README.html"&gt;eripheral Heart Rate Monitor with Coded PHY&lt;/a&gt;&amp;nbsp;project that already implements Coded PHY. The Coded PHY and extended advertising also needs to be set in the advertising initialization I believe.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>