<?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>nRF5340 system design with a second BT SOC to deliver Bluetooth Classic?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/93778/nrf5340-system-design-with-a-second-bt-soc-to-deliver-bluetooth-classic</link><description>We have come to understand that the nRF5340 will not support BT classic (multiple tickets confirming this). But we still have a use-case that requires both BLE Audio and BT Classic audio. So we are investigating if it is possible to make a system design</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 14 Nov 2022 09:11:36 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/93778/nrf5340-system-design-with-a-second-bt-soc-to-deliver-bluetooth-classic" /><item><title>RE: nRF5340 system design with a second BT SOC to deliver Bluetooth Classic?</title><link>https://devzone.nordicsemi.com/thread/395490?ContentTypeID=1</link><pubDate>Mon, 14 Nov 2022 09:11:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:70b525fa-dc05-4bb0-bedd-d6680dfa9bb4</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;I got a reply from my colleague that he does not know any internal R&amp;amp;D groups working on BT Classic. All are with LE only.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF5340 system design with a second BT SOC to deliver Bluetooth Classic?</title><link>https://devzone.nordicsemi.com/thread/395368?ContentTypeID=1</link><pubDate>Fri, 11 Nov 2022 15:10:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2a7f71fc-eea1-4c62-bea1-6ab57a3e6814</guid><dc:creator>Hakgus</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thanks for your reply. Yes I agree that long term BT classic will be replaced by BLE but we have to&amp;nbsp;interact with&amp;nbsp;todays mobile phones and support them for some more time. We understand Nordics strategy in this.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;But yes please, any more information would be very appreciated. Are there examples of system designs or considerations to adhere to that can help us forward?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF5340 system design with a second BT SOC to deliver Bluetooth Classic?</title><link>https://devzone.nordicsemi.com/thread/395286?ContentTypeID=1</link><pubDate>Fri, 11 Nov 2022 10:48:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5999bc10-0845-482d-9fa8-c01411d17416</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;All of our products in Nordic are foccused on low power IoT use cases. So no, I do not think BT classic was every on table with our roadmaps as BT Classic is very power intensive protocol and do not suit low power IoT devices we cater to.&lt;/p&gt;
&lt;p&gt;The use cases for BLE Audio are relatively new and atleast I haven&amp;#39;t heard of any customer designs that are two chip solutions from different vendors. But it should be very straightforward design if both the SoCs have their own memories and radio components. The design becomes more complex when there are shared resources between two.&lt;/p&gt;
&lt;p&gt;I have asked my colleague who have more insights in the BLE Audio part to see if he has any knowledge of use cases such as yours.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>