2017 VNA Design Notes - Revision history

Frohro at 20:16, 23 May 2017

2017-05-23T20:16:47Z

← Older revision		Revision as of 13:16, 23 May 2017
Line 1:		Line 1:

	These are notes so I don't forget what I needed to do to get things working for the software on the 2017 VNA project. This is not how you should write up your project! The purpose of this page is to give you an idea how a design is done. As you go along, you learn and the design gets better. In your write up you should describe the finished product, not how you there. The purpose of this page is to show you how the design process went. An you design, ideas occur to you, and you investigate them. Some work, and some don't. So DO NOT write your project up like this! ==		These are notes so I don't forget what I needed to do to get things working for the software on the 2017 VNA project. This is not how you should write up your project! The purpose of this page is to give you an idea how a design is done. As you go along, you learn and the design gets better. In your write up you should describe the finished product, not how you there. The purpose of this page is to show you how the design process went. An you design, ideas occur to you, and you investigate them. Some work, and some don't. So DO NOT write your project up like this!

	==Hardware==		==Hardware==

Frohro at 20:16, 23 May 2017

2017-05-23T20:16:27Z

← Older revision		Revision as of 13:16, 23 May 2017
Line 1:		Line 1:

	These are notes so I don't forget what I needed to do to get things working for the software on the 2017 VNA project.		These are notes so I don't forget what I needed to do to get things working for the software on the 2017 VNA project. This is not how you should write up your project! The purpose of this page is to give you an idea how a design is done. As you go along, you learn and the design gets better. In your write up you should describe the finished product, not how you there. The purpose of this page is to show you how the design process went. An you design, ideas occur to you, and you investigate them. Some work, and some don't. So DO NOT write your project up like this! ==

	==Hardware==		==Hardware==
	The test circuit is the [https://etherkit.github.io/si5351abb_landing_page.html Etherkit SI5351 Breakout Board]. The I2C pins SDA (P6.4) and SCL (P6.5) on the MSP432 Launchpad are used to communicate with the SI5351A. The jumpers J2 and J3 are set for 3.3V operation like [https://etherkit.github.io/si5351abb_usage.html this]. [[File:test_circuit.jpg\|800px]]The pinout for the MSP-EXP432P401R for Energia (arduino) applications on using this launchpad on this [http://energia.nu/pin-maps/guide_msp432p401r/ page] helped me figure this out. The I2C pins are the same on our board's design. The results can be seen here: [[File:lo_results.jpg\| 800px\|]]		The test circuit is the [https://etherkit.github.io/si5351abb_landing_page.html Etherkit SI5351 Breakout Board]. The I2C pins SDA (P6.4) and SCL (P6.5) on the MSP432 Launchpad are used to communicate with the SI5351A. The jumpers J2 and J3 are set for 3.3V operation like [https://etherkit.github.io/si5351abb_usage.html this]. [[File:test_circuit.jpg\|800px]]The pinout for the MSP-EXP432P401R for Energia (arduino) applications on using this launchpad on this [http://energia.nu/pin-maps/guide_msp432p401r/ page] helped me figure this out. The I2C pins are the same on our board's design. The results can be seen here: [[File:lo_results.jpg\| 800px\|]]

Frohro: /* Testing Serial Communications */

2017-05-23T20:12:12Z

Testing Serial Communications

@@ Line 865: / Line 865: @@
 It was also not always clear what keys send what with minicom, so I used the serial port sniffer program to see that LF was a CTRL-J (0x0A).  This is the termination character I was sending from the MSP432.  The serial port sniffer may also be handy snooping on the communications between octave and the MSP432.  The way I used it to look at the pseudo tty was:
   <nowiki>$ jpnevulator -a --tty /dev/pts/2 --read</nowiki>
-After looking at jpnevulator a bit, I decided it was difficult to use compared to [https://github.com/nochkin/interceptty interceptty] which was compiled from source.  This program creates a virtual terminal that you connect to with the octave script and will show all the data passing to the serial port and the direction it is going.  You don't need to use all kinds of complicated switches to use it for this purpose, though there are switches if you need them.  I just did this:
+After looking at jpnevulator a bit, I decided it was difficult to use compared to [https://github.com/nochkin/interceptty interceptty] which I just compiled from source.  This program creates a virtual terminal that you connect to with the octave script and will show all the data passing to the serial port and the direction it is going.  You don't need to use all kinds of complicated switches to use it for this purpose, though there are switches if you need them.  I just did this:
   <nowiki>$ interceptty /dev/ttyACM0 /tmp/ttyDUMMY</nowiki>
 Then I connected the octave program with this using:
   <nowiki>s1 = serial("/tmp/ttyDUMMY")</nowiki>

Frohro: /* Using Energia with Driverlib */

2017-05-23T20:08:31Z

Using Energia with Driverlib

Show changes

Frohro: /* Using Energia with Driverlib */

2017-05-12T23:47:57Z

Using Energia with Driverlib

← Older revision		Revision as of 16:47, 12 May 2017
Line 567:		Line 567:
	return 1;		return 1;
	}		}



	</nowiki>		</nowiki>
	This shows how to incorporate the Hwi_create(), etc. to set up the interrupt vectors.		This shows how to incorporate the Hwi_create(), etc. to set up the interrupt vectors.

Frohro: /* Notes on ADC14 */

2017-05-12T23:45:01Z

Notes on ADC14

← Older revision		Revision as of 16:45, 12 May 2017
Line 371:		Line 371:
	ADC14_enableConversion();		ADC14_enableConversion();
	}		}


	</nowiki>		</nowiki>

Frohro: /* Using Energia with Driverlib */

2017-05-12T23:43:26Z

Using Energia with Driverlib

← Older revision		Revision as of 16:43, 12 May 2017
Line 443:		Line 443:

	#endif /* TA_UP_H_ */		#endif /* TA_UP_H_ */
	</nowiki> and the ta_up.c file is:		</nowiki>
			and the ta_up.c file is:
	<nowiki>/*		<nowiki>/*
	* ta_up.c		* ta_up.c
Line 571:		Line 572:


	</nowiki> This shows how to incorporate the Hwi_create(), etc. to set up the interrupt vectors.		</nowiki>
			This shows how to incorporate the Hwi_create(), etc. to set up the interrupt vectors.

	Energia is multi threaded, executing up to four .ino files separately. The example MultiTaskSerial was helpful to understand this, and for serial communication dubugging. Using it I found the Energia serial monitor/port on my Linux box is /dev/ttyACM0 (usually). I was able to make an example project that used code from the SimpleLink DriverLib for toggling a GPIO to turn on and off a LED on P1.0 work with a .ino file. To include a C header file in a .ino source file, you need to use:		Energia is multi threaded, executing up to four .ino files separately. The example MultiTaskSerial was helpful to understand this, and for serial communication dubugging. Using it I found the Energia serial monitor/port on my Linux box is /dev/ttyACM0 (usually). I was able to make an example project that used code from the SimpleLink DriverLib for toggling a GPIO to turn on and off a LED on P1.0 work with a .ino file. To include a C header file in a .ino source file, you need to use:

Frohro: /* Using Energia with Driverlib */

2017-05-12T23:42:16Z

Using Energia with Driverlib

Show changes

Frohro: /* Testing Serial Communications */

2017-05-11T22:31:03Z

Testing Serial Communications

← Older revision		Revision as of 15:31, 11 May 2017
Line 414:		Line 414:
	2017/05/10 08:49:50 socat[14265] N PTY is /dev/pts/3		2017/05/10 08:49:50 socat[14265] N PTY is /dev/pts/3
	2017/05/10 08:49:50 socat[14265] N PTY is /dev/pts/5		2017/05/10 08:49:50 socat[14265] N PTY is /dev/pts/5
	2017/05/10 08:49:50 socat[14265] N starting data transfer loop with FDs [5,5] and [7,7]		2017/05/10 08:49:50 socat[14265] N starting data transfer loop with FDs [5,5] and [7,7]</nowiki>
	</nowiki>
	I don't want to use su powers with these virtual serial ports so I change the write permissions:		I don't want to use su powers with these virtual serial ports so I change the write permissions:
	<nowiki>sudo chmod a+rw /dev/pts/3</nowiki>		<nowiki>sudo chmod a+rw /dev/pts/3</nowiki>

Frohro: /* Testing Serial Communications */

2017-05-11T22:30:40Z

Testing Serial Communications

← Older revision		Revision as of 15:30, 11 May 2017
Line 411:		Line 411:
	<nowiki>$ sudo socat -d -d pty,raw,echo=0 pty,raw,echo=0 </nowiki>		<nowiki>$ sudo socat -d -d pty,raw,echo=0 pty,raw,echo=0 </nowiki>
	Then I get back something like this:		Then I get back something like this:
	<nowiki>~~[sudo] password for frohro:~~		<nowiki>
	2017/05/10 08:49:50 socat[14265] N PTY is /dev/pts/3		2017/05/10 08:49:50 socat[14265] N PTY is /dev/pts/3
	2017/05/10 08:49:50 socat[14265] N PTY is /dev/pts/5		2017/05/10 08:49:50 socat[14265] N PTY is /dev/pts/5