<?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>PCA10100 project not working for nRF52833 SoC</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/63252/pca10100-project-not-working-for-nrf52833-soc</link><description>Hi, 
 We have custom board based on nRF52833 SoC. We are trying to use SDK_v16.0.0/examples/ble_peripheral/ble_app_uart/pca10100/s140. 
 Using Segger Embedded studio, program is not downloading to flash but with nRF Connect it is downloading. 
 Is it</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 02 Jul 2020 12:35:09 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/63252/pca10100-project-not-working-for-nrf52833-soc" /><item><title>RE: PCA10100 project not working for nRF52833 SoC</title><link>https://devzone.nordicsemi.com/thread/258100?ContentTypeID=1</link><pubDate>Thu, 02 Jul 2020 12:35:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d2580a9c-0b02-4203-b94e-3ed285df368b</guid><dc:creator>Sridhar Jonnavittula</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;Yes after reinstalling it is working fine.&lt;/p&gt;
&lt;p&gt;Thank you.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: PCA10100 project not working for nRF52833 SoC</title><link>https://devzone.nordicsemi.com/thread/258088?ContentTypeID=1</link><pubDate>Thu, 02 Jul 2020 11:56:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f7f304e6-334e-4d08-8b70-4b4661ea92c1</guid><dc:creator>Karl Ylvisaker</dc:creator><description>&lt;p&gt;Hello,&lt;br /&gt;&lt;br /&gt;This could be caused by a faulty connection, or a bad Segger install.&lt;br /&gt;Could you ensure that the connection between the nRF52833 SoC and the J-Link is in good condition?&lt;br /&gt;Please see &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/54469/ses-error-reported-failed-to-download-application"&gt;this ticket&lt;/a&gt;&amp;nbsp;for details around resolving a bad Segger install - in essence it seems that you will need to reinstall Segger and the related JLink drivers to resolve this issue.&lt;br /&gt;&lt;br /&gt;Could you reinstall SES and J-Link driver, and let me know if this resolves your issue?&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Karl&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: PCA10100 project not working for nRF52833 SoC</title><link>https://devzone.nordicsemi.com/thread/258085?ContentTypeID=1</link><pubDate>Thu, 02 Jul 2020 11:45:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:87decfa3-a3dd-447e-bcfc-484a7b7090be</guid><dc:creator>Sridhar Jonnavittula</dc:creator><description>&lt;p&gt;&lt;strong&gt;Target-&amp;gt;Connect J-Link&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Connecting &amp;#39;J-Link&amp;#39; using &amp;#39;USB&amp;#39;&lt;br /&gt;&amp;nbsp; Connecting to target using SWD&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Loaded /usr/share/segger_embedded_studio_for_arm_4.22/bin/libjlinkarm.so&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Firmware Version: J-Link EDU Mini V1 compiled May 26 2020 15:04:19&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; DLL Version: 6.50a&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Hardware Version: V1.00&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Target Voltage: 3.299&lt;br /&gt;&amp;nbsp; Device &amp;quot;CORTEX-M4&amp;quot; selected.&lt;br /&gt;&amp;nbsp; Found SW-DP with ID 0x2BA01477&lt;br /&gt;&amp;nbsp; Scanning AP map to find all available APs&lt;br /&gt;&amp;nbsp; AP[2]: Stopped AP scan as end of AP map has been reached&lt;br /&gt;&amp;nbsp; AP[0]: AHB-AP (IDR: 0x24770011)&lt;br /&gt;&amp;nbsp; AP[1]: JTAG-AP (IDR: 0x02880000)&lt;br /&gt;&amp;nbsp; Iterating through AP map to find AHB-AP to use&lt;br /&gt;&amp;nbsp; AP[0]: Core found&lt;br /&gt;&amp;nbsp; AP[0]: AHB-AP ROM base: 0xE00FF000&lt;br /&gt;&amp;nbsp; CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)&lt;br /&gt;&amp;nbsp; Found Cortex-M4 r0p1, Little endian.&lt;br /&gt;&amp;nbsp; FPUnit: 6 code (BP) slots and 2 literal slots&lt;br /&gt;&amp;nbsp; CoreSight components:&lt;br /&gt;&amp;nbsp; ROMTbl[0] @ E00FF000&lt;br /&gt;&amp;nbsp; ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7&lt;br /&gt;&amp;nbsp; ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT&lt;br /&gt;&amp;nbsp; ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB&lt;br /&gt;&amp;nbsp; ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM&lt;br /&gt;&amp;nbsp; ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU&lt;br /&gt;&amp;nbsp; ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Target-&amp;gt;Download File-&amp;gt;Download &lt;br /&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Connecting &amp;#39;J-Link&amp;#39; using &amp;#39;USB&amp;#39;&lt;br /&gt;&amp;nbsp; Connecting to target using SWD&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Loaded /usr/share/segger_embedded_studio_for_arm_4.22/bin/libjlinkarm.so&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Firmware Version: J-Link EDU Mini V1 compiled May 26 2020 15:04:19&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; DLL Version: 6.50a&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Hardware Version: V1.00&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Target Voltage: 3.299&lt;br /&gt;&amp;nbsp; Device &amp;quot;CORTEX-M4&amp;quot; selected.&lt;br /&gt;&amp;nbsp; Found SW-DP with ID 0x2BA01477&lt;br /&gt;&amp;nbsp; Scanning AP map to find all available APs&lt;br /&gt;&amp;nbsp; AP[2]: Stopped AP scan as end of AP map has been reached&lt;br /&gt;&amp;nbsp; AP[0]: AHB-AP (IDR: 0x24770011)&lt;br /&gt;&amp;nbsp; AP[1]: JTAG-AP (IDR: 0x02880000)&lt;br /&gt;&amp;nbsp; Iterating through AP map to find AHB-AP to use&lt;br /&gt;&amp;nbsp; AP[0]: Core found&lt;br /&gt;&amp;nbsp; AP[0]: AHB-AP ROM base: 0xE00FF000&lt;br /&gt;&amp;nbsp; CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)&lt;br /&gt;&amp;nbsp; Found Cortex-M4 r0p1, Little endian.&lt;br /&gt;&amp;nbsp; FPUnit: 6 code (BP) slots and 2 literal slots&lt;br /&gt;&amp;nbsp; CoreSight components:&lt;br /&gt;&amp;nbsp; ROMTbl[0] @ E00FF000&lt;br /&gt;&amp;nbsp; ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7&lt;br /&gt;&amp;nbsp; ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT&lt;br /&gt;&amp;nbsp; ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB&lt;br /&gt;&amp;nbsp; ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM&lt;br /&gt;&amp;nbsp; ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU&lt;br /&gt;&amp;nbsp; ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM&lt;br /&gt;Preparing target for download&lt;br /&gt;&amp;nbsp; Executing Reset script TargetInterface.resetAndStop()&lt;br /&gt;&amp;nbsp; Reset: Halt core after reset via DEMCR.VC_CORERESET.&lt;br /&gt;&amp;nbsp; Reset: Reset device via AIRCR.SYSRESETREQ.&lt;br /&gt;Downloading &amp;#39;s113_nrf52_7.0.1_softdevice.hex&amp;#39; to J-Link&lt;br /&gt;&amp;nbsp; Programming 2.7 KB of addresses 00000000 -- 00000aff&lt;br /&gt;&amp;nbsp; Programming 105.0 KB of addresses 00001000 -- 0001b3ff&lt;/p&gt;
&lt;p&gt;It says Generic Error&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/pastedimage1593690319506v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;Is there any particular SES version for this nRF52833 SoC? We use version 4.22.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: PCA10100 project not working for nRF52833 SoC</title><link>https://devzone.nordicsemi.com/thread/258070?ContentTypeID=1</link><pubDate>Thu, 02 Jul 2020 11:06:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9f7488dd-7059-43a1-985e-742f07f5b38b</guid><dc:creator>Karl Ylvisaker</dc:creator><description>[quote user="Jonnavittula sridhar"]Yes, our custom board has JLink pins out and connected via debugger.[/quote]
&lt;p&gt;Alright, this is good to know, that changes things.&lt;/p&gt;
[quote user="Jonnavittula sridhar"]So when debugger USB interface is connected to Windows PC which runs SES cant able to download prebuilt hex file&amp;nbsp;ble_app_uart_pca10100_s140.hex using Download Intel Hex file option but nRF Connect for desktop &lt;strong&gt;Programmer&lt;/strong&gt; application and &lt;strong&gt;nrfjprog&lt;/strong&gt; can download in the same Windows PC.[/quote]
&lt;p&gt;Are you able to connect to the JLink from SES? Is there an error prompt when you try to use the &amp;quot;Target-&amp;gt;Download&amp;quot; button? If so, which one?&lt;/p&gt;
[quote user="Jonnavittula sridhar"]Furthermore, be advised that the ble_app_uart PCA10100 project is made for the nRF52833 DK specifically, and it is not guaranteed to work right off the bat on a custom board - due to possible differences in the PCB&amp;#39;s.[/quote]
&lt;p&gt;I do not understand what you mean by this including this quotation from my previous reply, please elaborate.&lt;/p&gt;
[quote user="Jonnavittula sridhar"]Why SES cant even program?[/quote]
&lt;p&gt;SES should be able to program your device just fine as long as it is connected to the JLink, which in turn is connected to your nRF52833 SoC.&lt;br /&gt;Please specify what behavior you are seeing when you attempt to use SES to program your device.&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Karl&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: PCA10100 project not working for nRF52833 SoC</title><link>https://devzone.nordicsemi.com/thread/258054?ContentTypeID=1</link><pubDate>Thu, 02 Jul 2020 10:34:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e9590f1f-f778-4ebf-a7d2-fcfd97d9104c</guid><dc:creator>Sridhar Jonnavittula</dc:creator><description>&lt;p&gt;Yes, our custom board has JLink pins out and connected via debugger.&lt;/p&gt;
&lt;p&gt;So when debugger USB interface is connected to Windows PC which runs SES cant able to download prebuilt hex file&amp;nbsp;ble_app_uart_pca10100_s140.hex using Download Intel Hex file option but nRF Connect for desktop &lt;strong&gt;Programmer&lt;/strong&gt; application and &lt;strong&gt;nrfjprog&lt;/strong&gt; can download in the same Windows PC.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;span style="text-decoration:underline;"&gt;&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;span style="text-decoration:underline;"&gt;Furthermore, be advised that the ble_app_uart PCA10100 project is made for the nRF52833 DK specifically, and it is not guaranteed to work right off the bat on a custom board - due to possible differences in the PCB&amp;#39;s.&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Why SES cant even program?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: PCA10100 project not working for nRF52833 SoC</title><link>https://devzone.nordicsemi.com/thread/258046?ContentTypeID=1</link><pubDate>Thu, 02 Jul 2020 10:18:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0d00af9b-1631-465b-9cae-a5f020f67604</guid><dc:creator>Karl Ylvisaker</dc:creator><description>&lt;p&gt;Hello,&lt;br /&gt;&lt;br /&gt;How is the nRF52833 SoC connected to your computer - do you have it connected to a debugger?&lt;br /&gt;SES will need a J-Link interface to program and debug your SoC.&lt;br /&gt;The nRF Connect programmer can write a prebuilt .hex directly to your MCUbootloader.&lt;br /&gt;&lt;br /&gt;Furthermore, be advised that the ble_app_uart PCA10100 project is made for the nRF52833 DK specifically, and it is not guaranteed to work right off the bat on a custom board - due to possible differences in the PCB&amp;#39;s.&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Karl&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>