Stm32f100 notes - Revision history

Ted: /* ^ References */

2021-06-04T00:00:08Z

^ References

2021-04-14T13:30:08Z

2021-04-14T04:23:46Z

^ Comparison STM32F Discovery board versus LPC1114 prototype board

2021-04-14T04:18:34Z

^ References

2019-02-28T23:25:13Z

^ References

2019-01-29T18:08:11Z

^ Comparison STM32F Discovery board versus LPC1114 prototype board

2019-01-25T22:19:30Z

^ Comparison STM32F Discovery board versus LPC1114 prototype board

2019-01-25T20:21:41Z

^ Comparison STM32F Discovery board versus LPC1114 prototype board

2019-01-25T20:04:09Z

2019-01-04T18:26:17Z

^ SN 434757 gives always zero readings

← Older revision		Revision as of 00:00, 4 June 2021
Line 1,215:		Line 1,215:
	* https://electronics.stackexchange.com/questions/32991/how-do-i-develop-for-stm32-discovery-on-linux		* https://electronics.stackexchange.com/questions/32991/how-do-i-develop-for-stm32-discovery-on-linux

		+	* https://www.mikroe.com/fusion-for-stm32 Fusion for STM32

	<!-- comment -->		<!-- comment -->

@@ Line 4: / Line 4: @@
 == Overview ==
-This article to hold notes on early works with STMicro's STM32F100VL Discovery Board.  We're using arm-none-eabi-gcc and assember versions:
+This article to hold notes on early works with STMicro's STM32F100VL Discovery Board.  Early work here refers to 2018 July - 2019 February work with bringing up serial comm's and I2C communication with a sample CO2 sensor.  New work related to [https://github.com/oresat Oresat] voluteer actities and personal exploration of [https://chibios.org ChibiOS] is in the local wiki article [[stm32f-2021|STM32 2021]].
 <pre>

@@ Line 1,188: / Line 1,188: @@
 </pre>
 Given that Sensirion's SCD30 sends a CRC byte after every two bytes of data returned to a calling / master I2C device, the twenty two byte string string from the STM32F board should actually return as thirty three bytes of data.  In the LPC1114 firmware, our routine to query sensor serial number tells the I2C subsystem to expect n bytes . . .
-<code>
+<code> </code>
 <!--
@@ Line 1,204: / Line 1,200: @@
      *  https://en.wikipedia.org/wiki/Single-precision_floating-point_format
 -->
 <!-- comment -->

← Older revision		Revision as of 04:18, 14 April 2021
Line 1,215:		Line 1,215:

	* https://community.st.com/thread/44899-how-to-activate-floating-point-for-sprintf-in-your-project		* https://community.st.com/thread/44899-how-to-activate-floating-point-for-sprintf-in-your-project
		+
		+	2021-04-13
		+	* https://electronics.stackexchange.com/questions/32991/how-do-i-develop-for-stm32-discovery-on-linux

@@ Line 1,218: / Line 1,218: @@
 <!-- comment -->
 <center>
 - - - [[#top|top of page]] - - -
 </center>

← Older revision		Revision as of 18:08, 29 January 2019
Line 1,196:		Line 1,196:

	</code>		</code>
		+
		+	<!--
		+	2019-01-29 Snippet of e-mail to Al P:
		+
		+	One thing I've observed separate from these memory allocation, interrupt and timing issues has to do with floating point values. In my initial experimental set-up using an ST micro dev board, sensor readings return to my code as floating point values, but small enough and low enough precision that I could normally ignore the exponent and sign parts of the values and treat the lower bytes as an integer. Now in the context of using these sensors in a circuit whose A/D and PWM circuits are much like PX3's, and code is PX3 firmware based, I'm getting much larger reading values. These may yet be accurate, but looks like I can no longer do the lazy thing and treat a float as an integer less than 2^16. To your recollection is the routine CON_TxFloat() based on
		+
		+	* https://en.wikipedia.org/wiki/Single-precision_floating-point_format
		+	-->

@@ Line 1,175: / Line 1,175: @@
 == [[#top|^]] Comparison STM32F Discovery board versus LPC1114 prototype board ==
 I2C communications seem to be only working part way on the prototype board with capacitor array and an SCD30 now socketed, communicating with an LPC1114 microcontroller.  The serial numbers reported on the STM32F Discovery Value Line board are twenty two characters long and of the form in the following text snippet.  The serial numbers reported back on the LPC based board are truncated by a few characters:
 <pre>
-    sensor serial number is 425319-426062-73361217      shown in single quotes, SCD30 returns serial number:  '435148-436657-73'
+   query for SN:       425319-426062-73361217             '435148-436657-73'
 </pre>

← Older revision		Revision as of 20:04, 25 January 2019
Line 1,170:		Line 1,170:

	425319-426062-73361217		425319-426062-73361217
		+
		+
		+	<!-- comment -->
		+
		+	== [[#top\|^]] Comparison STM32F Discovery board versus LPC1114 prototype board ==
		+
		+	I2C communications seem to be only working part way on the prototype board with capacitor array and an SCD30 now socketed, communicating with an LPC1114 microcontroller. The serial numbers reported on the STM32F Discovery Value Line board are twenty two characters long and of the form in the following text snippet. The serial numbers reported back on the LPC based board are truncated by a few characters:
		+
		+	<pre>
		+
		+	sensor serial number is 425319-426062-73361217
		+
		+	</pre>
		+

← Older revision		Revision as of 18:26, 4 January 2019
Line 1,156:		Line 1,156:
	asking sensor if data ready . . .		asking sensor if data ready . . .
	</pre>		</pre>
		+
		+
		+	<!-- comment -->
		+
		+	=== [[#top\|^]] SN 441623 gives always zero readings ===
		+
		+	441623-441455-73245187
		+
		+
		+	<!-- comment -->
		+
		+	=== [[#top\|^]] SN 425319 gives always zero readings ===
		+
		+	425319-426062-73361217