<?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>Interrput line number configuration nRF5340</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/112871/interrput-line-number-configuration-nrf5340</link><description>Hi, 
 I faced some issues regarding multiple IRQ_CONNECT being onvoked on the same irq and I went into this post : 
 LPUART nRF5340 fatal error - Nordic Q&amp;amp;A - Nordic DevZone - Nordic DevZone (nordicsemi.com) 
 Does it means that any &amp;lt;PERIPHERAL&amp;gt;X interrput</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 10 Jul 2024 10:48:41 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/112871/interrput-line-number-configuration-nrf5340" /><item><title>RE: Interrput line number configuration nRF5340</title><link>https://devzone.nordicsemi.com/thread/493125?ContentTypeID=1</link><pubDate>Wed, 10 Jul 2024 10:48:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e3747fac-a481-4d9d-b3b8-159d28664bc3</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;I see, thanks for the clarification. Unfortunately, the Zephyr drivers does not support dynamic un-initialization and re-initialization of peripherals which would be required to allow shared usage of multiple peripherals with the same ID. This&amp;nbsp;is however possible if you use the nrfx drivers directly as demonstrated by the&amp;nbsp;&lt;a href="https://docs.nordicsemi.com/bundle/ncs-2.6.1/page/zephyr/samples/boards/nrf/nrfx_prs/README.html"&gt;nrfx peripheral resource sharing example&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: Interrput line number configuration nRF5340</title><link>https://devzone.nordicsemi.com/thread/493120?ContentTypeID=1</link><pubDate>Wed, 10 Jul 2024 10:20:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f64f29d9-e92c-42eb-b37c-10e330acb68c</guid><dc:creator>Ben_Squar3d</dc:creator><description>&lt;p&gt;Ok got it! I wondered if I could perform similar operation for other peripheral to workaround the limitation of TWIM0 OR SPI0 and TWIM1 OR SPI1 etc.. It seems not possible, thank you for you answer&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Interrput line number configuration nRF5340</title><link>https://devzone.nordicsemi.com/thread/493110?ContentTypeID=1</link><pubDate>Wed, 10 Jul 2024 09:51:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ad704142-c643-4dc4-89d9-cf93e170491d</guid><dc:creator>Vidar Berg</dc:creator><description>[quote user="Ben_Squar3d"]why does re-route GPIOTE IRQ to GPIOTE1 (47) instead of GPIOTE0 (9) work?[/quote]
&lt;p&gt;The problem discussed in&amp;nbsp;linked Q&amp;amp;A seems to be about the application switching from using GPIOTE0 to GPIOTE1 after building the application for the Non Secure Processing Environment (i.e. nrf5340dk_nrf5340_cpuapp&lt;strong&gt;_ns)&lt;/strong&gt;. Therefore, the harcoded IRQ number had to be changed to match the selected peripheral.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Could you provide a bit more information about what you are trying to achieve?&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Interrput line number configuration nRF5340</title><link>https://devzone.nordicsemi.com/thread/492970?ContentTypeID=1</link><pubDate>Tue, 09 Jul 2024 12:58:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:aef97f72-4274-4ee7-a315-73b0b98fc192</guid><dc:creator>Ben_Squar3d</dc:creator><description>&lt;p&gt;Sorry, I should have been more precise. I know some peripherals share same address space :&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1720529621377v3.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;And I know that is why IRQ_CONNECT can only be called once per irq number/peripheral ID. My questions were : why does re-route GPIOTE IRQ to GPIOTE1 (47) instead of GPIOTE0 (9) work? In the same way, could I re-route IRQ of I2C0 (8) to I2C1 (9) ? Like GPIOTE0 and GPIOTE1, I2C0 and I2C1 doesn&amp;#39;t share adderss space. Thank you&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Interrput line number configuration nRF5340</title><link>https://devzone.nordicsemi.com/thread/492966?ContentTypeID=1</link><pubDate>Tue, 09 Jul 2024 12:45:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2419c65a-a510-4e71-9b47-632f7a4c41e5</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;If you read the PS carefully, you will see that multiple peripherials share address space. That includes the IRQ line.&lt;/p&gt;
&lt;p&gt;You can only use one of the instances - either UART, SPIM,SPIS or TWI.&lt;/p&gt;
&lt;p&gt;The UART0 is used by multiple examples, so try i2c1 or i2c2 in your dts or overlay file.&lt;/p&gt;
&lt;p&gt;You can inspect the combined dts in the build/zephyr subdir, it should enable (&amp;quot;okay&amp;quot;) only one of the peripherials with the same address.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>