SJ One Board - Revision history

Preet: /* Obtain the Board */

2018-02-07T17:58:29Z

‎Obtain the Board

2014-10-28T03:28:16Z

‎Board Sample Code & Experiments

2014-08-01T20:11:02Z

‎Data logging

2014-08-01T20:07:20Z

‎Timer Services

2014-08-01T20:04:30Z

‎About the Board

2014-06-05T01:58:02Z

‎Wireless

2014-06-01T22:15:37Z

‎Debugging a Crash

2014-03-20T20:38:38Z

2013-12-09T16:56:58Z

‎Board Overlay

2013-12-09T16:56:27Z

‎The Basics

@@ Line 3: / Line 3: @@
 === Obtain the Board ===
-*  If you are a San Jose State University student, you can obtain the board from SCE at Engr294.
+*  If you are a San Jose State University student, you can obtain the board by contacting Preet
 *  For remote users, you can contact [[User:Preet | '''Preet''']]

@@ Line 392: / Line 392: @@
 *  You can read about [http://socialledge.com/docs/wireless_8h.html Doxygen generated docs] or read through '''wireless.h'''
 *  VIDEO : [http://www.youtube.com/watch?v=9iXo3P6JX0s Mesh Network API]
 <BR/>

@@ Line 533: / Line 533: @@
 === Data logging ===
-One of the best ways to debugging a project is to log useful information.  There is a logging facility available but as of now, it requires that you are running FreeRTOS since it logs data in a low priority task.
+One of the best ways to debugging a project is to log useful information.  There is a logging facility available and it is best to use FreeRTOS that provides optimized operation.  See "file_logger.h" for more details and parameters.
 <syntaxhighlight lang="C">

@@ Line 338: / Line 338: @@
 <BR/>
 === Timer Services ===
-Getting system time using C libraries should work, but you can also get time directly from "rtc.h".  Other than this, there are two more timer services you can use as demonstrated in the code sample below.
+Getting system time using C libraries is an option, but you can also get time directly from "rtc.h".  Other than this, there are two more timer services you can use as demonstrated in the code sample below.
 <syntaxhighlight lang="cpp">
@@ Line 346: / Line 346: @@
 void timers()
+{
-     /* You can get the time since the board has been powered in milli-seconds */
+     /* You can get the time since the board has been powered */
      uint64_t uptime_ms = sys_get_uptime_ms();
-     /* You can compute time delta in microseconds too */
+     /* There is also a polling timer available in C++, read "soft_timer.hpp" for more info. */
-     uint64_t timer_micro_sec = sys_get_high_res_timer_us();
+     SoftTimer myTimer(1000);
      if (myTimer.expired()) {
          /* Do something */

@@ Line 9: / Line 9: @@
 *  [http://www.nxp.com/documents/user_manual/UM10360.pdf '''LPC1758 User Manual''']
 *  [[File:2012SJOneBoardSchematic.pdf|2013 SJ One Board Schematic]]
-*  512K ROM, 64K RAM, 1M SPI Flash, and Micro-SD for storage.
+*  512K ROM, 64K(96K) RAM, 1M(2M) SPI Flash, and Micro-SD for storage.
 *  Built-in Nordic Wireless (Board-to-Board communication)
 *:  [[Low Powered Mesh Network stack|Software Stack for Mesh Network]]

@@ Line 393: / Line 393: @@
 === Wireless ===
 This board can communicate to other boards using a very low-powered wireless technology.  Here are various resources :
-*  Code samples are at [[Interactive Wireless Nodes Project]] (towards the bottom).
+*  Code samples are at [[Low Powered Mesh Network stack]] (towards the bottom).
 *  You can read about [http://socialledge.com/docs/wireless_8h.html Doxygen generated docs] or read through '''wireless.h'''
 *  VIDEO : [http://www.youtube.com/watch?v=9iXo3P6JX0s Mesh Network API]
 <BR/>
 == Interrupts & Memory Map ==
 Read the following articles as replacements :

← Older revision		Revision as of 22:15, 1 June 2014
Line 534:		Line 534:
	* Open <B><code>*.lst</code></b> file from the <B><code>_build</code></b> folder, and search for last four digits of PC. That is where the crash happened.		* Open <B><code>*.lst</code></b> file from the <B><code>_build</code></b> folder, and search for last four digits of PC. That is where the crash happened.
	* '''LR''' is the "return address" of the previously called function. But I think if you see "0x123F", search for "1240" or "123C" because I think you have to subtract one from the LR value so that it lies on 4 byte boundary.		* '''LR''' is the "return address" of the previously called function. But I think if you see "0x123F", search for "1240" or "123C" because I think you have to subtract one from the LR value so that it lies on 4 byte boundary.
		+
		+	=== Data logging ===
		+	One of the best ways to debugging a project is to log useful information. There is a logging facility available but as of now, it requires that you are running FreeRTOS since it logs data in a low priority task.
		+
		+	<syntaxhighlight lang="C">
		+	#include "file_logger.h"
		+
		+	void foo()
		+	{
		+	LOG_INFO("Some info");
		+	LOG_WARN("Some warning");
		+	LOG_ERROR("Some error happened, value is: %u", 123);
		+
		+	/* All the info is logged to a file (log.csv)
		+	* You can open this file using terminal command "cat log.csv"
		+	* You can also modify the destination to the SD card by defining
		+	* logging filename to "1:log.csv" at file_logger.h
		+	*/
		+	}
		+	</syntaxhighlight>

← Older revision		Revision as of 20:38, 20 March 2014
Line 527:		Line 527:
	#endif /* end MY_NEW_FILE_H__ */		#endif /* end MY_NEW_FILE_H__ */
	</syntaxhighlight>		</syntaxhighlight>
		+
		+	<BR/>
		+	== Debugging a Crash ==
		+	When the crash happens, it will print some useful info upon next boot, and it will also tell you the last running task before the crash happened (if you are running FreeRTOS). The next clues can be determined by doing this:
		+	* Note down the address of '''PC''' and '''LR''' from the crash info printout
		+	* Open <B><code>*.lst</code></b> file from the <B><code>_build</code></b> folder, and search for last four digits of PC. That is where the crash happened.
		+	* '''LR''' is the "return address" of the previously called function. But I think if you see "0x123F", search for "1240" or "123C" because I think you have to subtract one from the LR value so that it lies on 4 byte boundary.

@@ Line 44: / Line 44: @@
 [[File:devtutorial_SjOneIO.png|center|frame|SJ One Board IO]]
-== Board Overlay ==
+=== Board Overlay ===
 This board overlay can be compared against diagrams above to get an idea of where the IOs are located.
 [[File:devtutorial_SjOneBoardOverlay.png|center|frame|SJ One Board Overlay]]
 <BR/>
 == The Basics ==
 === Sample Projects & Where to start?? ===

@@ Line 60: / Line 60: @@
 <br/>
 === External SPI Devices ===
@@ Line 112: / Line 113: @@
 <BR/>
 == External Components ==
 === GPIO & High-Power LED ===