<?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>Sending AT commands to a GSM</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/7536/sending-at-commands-to-a-gsm</link><description>Hello All,
I am working with a pre-programed PCB; the main components of the are a nRF51822 chip, a GPS, and a GSM. I am using a J-link to communicate to the entire board through the SWD (SWDIO and SWDCLK) pins on the nRF51. I need to send AT commands</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 22 Jun 2015 09:43:25 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/7536/sending-at-commands-to-a-gsm" /><item><title>RE: Sending AT commands to a GSM</title><link>https://devzone.nordicsemi.com/thread/26844?ContentTypeID=1</link><pubDate>Mon, 22 Jun 2015 09:43:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:48aea55c-a101-41f3-9c7b-8a997d3823f2</guid><dc:creator>Ulrich Myhre</dc:creator><description>&lt;p&gt;You can access the debug interface through e.g. the JLink DLL using nrfjprog. The nrfjprog executable has --memwr and --memrd that can be used for this. It can also download the current application if you want to have a copy of it (and if readback protection is not enabled).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sending AT commands to a GSM</title><link>https://devzone.nordicsemi.com/thread/26843?ContentTypeID=1</link><pubDate>Fri, 19 Jun 2015 01:42:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ce857088-8876-43a6-975e-3a758667d5b1</guid><dc:creator>Aaron Graves</dc:creator><description>&lt;p&gt;Hello Ulrich. When you say to use the debugger interface do you mean the &lt;em&gt;J-Link RTT Viewer&lt;/em&gt; or the debugger in &lt;em&gt;Keil&lt;/em&gt;? If you do mean &lt;em&gt;Keil&lt;/em&gt;, how can the debugger be accessed without the source project. Thanks.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sending AT commands to a GSM</title><link>https://devzone.nordicsemi.com/thread/26845?ContentTypeID=1</link><pubDate>Thu, 11 Jun 2015 10:51:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:395f8807-46ec-4226-8607-7f218fea8e2a</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@Aaron: if you have access to the SWD interface and if the firmware on the nRF51 chip is not read back protected. You can simply readout the chip&amp;#39;s image, store it. Then make your own firmware to test the GSM chip. After you have done that you can flash the original image back.&lt;/p&gt;
&lt;p&gt;Or you can simply don&amp;#39;t power the nRF51 chip, and hook the UART lines from PC to the UART pins on the GSM chip. And can try to control it from the PC. This would require some hardware hack on the board.&lt;/p&gt;
&lt;p&gt;Or you can try what Ulrich suggested.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sending AT commands to a GSM</title><link>https://devzone.nordicsemi.com/thread/26842?ContentTypeID=1</link><pubDate>Wed, 10 Jun 2015 13:19:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c4ceea7a-2c6f-4ad1-b769-9a1e87291569</guid><dc:creator>Ulrich Myhre</dc:creator><description>&lt;p&gt;Hi!&lt;/p&gt;
&lt;p&gt;I think the only possibility would be to use the debugger interface to manually write to the UART0 registers. You need to set up the PSELTXD/PSELRXD, BAUDRATE and CONFIG registers, set ENABLE to 0x04 and enable the STARTTX task first. Then you should be able to write single bytes by writing 0 to EVENTS_TXDRDY, write your byte to the TXD buffer, and poll the EVENTS_TXDRDY area periodically until it is 1 again. Assuming that the firmware is not using the UART peripheral already, reseting your settings.&lt;/p&gt;
&lt;p&gt;This is of course terribly hacky, quite slow, and keeps the debugger interface enabled (which will likely break ongoing radio activity and keep the power consumption very high). But if you need to seldomly send a few commands, this could do the trick.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>