Quiz 6.3 - Revision history

Frohro at 23:12, 2 November 2016

2016-11-02T23:12:21Z

← Older revision		Revision as of 16:12, 2 November 2016
Line 2:		Line 2:

	To get the Assembly List file, go into the Build Settings->Build->Advanced Options->Assembler, and tick the Generate listing file box.		To get the Assembly List file, go into the Build Settings->Build->Advanced Options->Assembler, and tick the Generate listing file box.
	[[File:assembly-listing-option.png]]		[[File:assembly-listing-option.png\|800px]]
	Here is the listing file I got using the MSP430G2553 processor.		Here is the listing file I got using the MSP430G2553 processor.
	<nowiki>MSP430 Assembler Unix v15.12.3 Tue Nov 1 17:48:13 2016		<nowiki>MSP430 Assembler Unix v15.12.3 Tue Nov 1 17:48:13 2016

Frohro at 01:07, 2 November 2016

2016-11-02T01:07:13Z

← Older revision		Revision as of 18:07, 1 November 2016
Line 1:		Line 1:
	~~Sections~~ start their location counters at zero. ~~The .bss directives don't advance the counter, because they go off to a different section.~~ Assembly instructions take up bytes of memory according to what they are and their addressing mode. Whenever a .sect happens the location counter is reset to zero. There is more in section 2 of this [http://www.ti.com/lit/ug/slau131m/slau131m.pdf TI Manual on the Assembler]. This quiz is ~~more~~ tailored to understanding the Assembly List file, that has a field for the location counter. Code Composer Studio doesn't generate this by default anymore. It is good to look at though. I wasn't able to correctly get the location counter values correct without ~~the compiler's help~~, and I'm impressed if you got them. Fortunately we can still get it to make an assembly listing for us.		New sections start their location counters at zero. Assembly instructions take up bytes of memory according to what they are and their addressing mode. Whenever a .sect, or .text happens the location counter is reset to zero. There is more in section 2 of this [http://www.ti.com/lit/ug/slau131m/slau131m.pdf TI Manual on the Assembler]. This quiz is tailored to understanding the Assembly List file, that has a field for the location counter. Code Composer Studio doesn't generate this by default anymore. It is good to look at for this quiz though. I wasn't able to correctly get the location counter values correct without it, and I'm impressed if you got them. Fortunately we can still get it to make an assembly listing for us.

	To get the Assembly List file, go into the Build Settings->Build->Advanced Options->Assembler, and tick the Generate listing file box.		To get the Assembly List file, go into the Build Settings->Build->Advanced Options->Assembler, and tick the Generate listing file box.

Frohro at 01:02, 2 November 2016

2016-11-02T01:02:57Z

← Older revision		Revision as of 18:02, 1 November 2016
Line 1:		Line 1:
	Sections start their location counters at zero. The .bss directives don't advance the counter, because they go off to a different section. Assembly instructions take up bytes of memory according to what they are and their addressing mode. Whenever a .sect happens the location counter is reset to zero. There is more in section 2 of this [http://www.ti.com/lit/ug/slau131m/slau131m.pdf TI Manual on the Assembler]. This quiz is more tailored to understanding the Assembly List file, that has a field for the location counter. Code Composer Studio doesn't generate this by default anymore. It is good to look at though. I wasn't able to correctly get the location counter values correct without the compiler's help. Fortunately ~~you~~ can still get it to make an assembly listing for ~~you~~.		Sections start their location counters at zero. The .bss directives don't advance the counter, because they go off to a different section. Assembly instructions take up bytes of memory according to what they are and their addressing mode. Whenever a .sect happens the location counter is reset to zero. There is more in section 2 of this [http://www.ti.com/lit/ug/slau131m/slau131m.pdf TI Manual on the Assembler]. This quiz is more tailored to understanding the Assembly List file, that has a field for the location counter. Code Composer Studio doesn't generate this by default anymore. It is good to look at though. I wasn't able to correctly get the location counter values correct without the compiler's help, and I'm impressed if you got them. Fortunately we can still get it to make an assembly listing for us.

	~~You~~ get the Assembly List file ~~by going~~ into the Build Settings->Build->Advanced Options->Assembler, and tick the Generate listing file box. ~~Here is the listing file I got using the MSP430G2553 processor.~~		To get the Assembly List file, go into the Build Settings->Build->Advanced Options->Assembler, and tick the Generate listing file box.
	[[File:assembly-listing-option.png]]		[[File:assembly-listing-option.png]]
			Here is the listing file I got using the MSP430G2553 processor.
	<nowiki>MSP430 Assembler Unix v15.12.3 Tue Nov 1 17:48:13 2016		<nowiki>MSP430 Assembler Unix v15.12.3 Tue Nov 1 17:48:13 2016

	Tools Copyright (c) 2003-2015 Texas Instruments Incorporated		Tools Copyright (c) 2003-2015 Texas Instruments Incorporated
	../main.asm PAGE 1		../main.asm
			PAGE 1

	1 .cdecls C,"msp430.h" ; include c header		1 .cdecls C,"msp430.h" ; include c header
Line 39:		Line 41:
	</nowiki>		</nowiki>

	~~You can see that my guess wasn't right.~~ The second column of numbers is the location counter. ~~:-)~~		The second column of numbers is the location counter.

Frohro at 00:59, 2 November 2016

2016-11-02T00:59:00Z

← Older revision		Revision as of 17:59, 1 November 2016
Line 1:		Line 1:
	Sections start their location counters at zero. The .bss directives don't advance the counter, because they go off to a different section. Assembly instructions take up bytes of memory according to what they are and their addressing mode. Whenever a .sect happens the location counter is reset to zero. There is more in section 2 of this [http://www.ti.com/lit/ug/slau131m/slau131m.pdf TI Manual on the Assembler]~~. I'm not certain about these, but here is what I came up with, as my best guess~~. This quiz is more tailored to the ~~old~~ Assembly List file, that has a field for the ~~section~~ counter. Code Composer Studio		Sections start their location counters at zero. The .bss directives don't advance the counter, because they go off to a different section. Assembly instructions take up bytes of memory according to what they are and their addressing mode. Whenever a .sect happens the location counter is reset to zero. There is more in section 2 of this [http://www.ti.com/lit/ug/slau131m/slau131m.pdf TI Manual on the Assembler]. This quiz is more tailored to understanding the Assembly List file, that has a field for the location counter. Code Composer Studio doesn't generate this by default anymore. It is good to look at though. I wasn't able to correctly get the location counter values correct without the compiler's help. Fortunately you can still get it to make an assembly listing for you.

	*0x0000		You get the Assembly List file by going into the Build Settings->Build->Advanced Options->Assembler, and tick the Generate listing file box. Here is the listing file I got using the MSP430G2553 processor.
	*0x0000		[[File:assembly-listing-option.png]]
	*0x0000
	*0x0002
	*0x0008
	*0x000a
	*0x000c
	*0x000e
	*0x000e
	*0x0010
	*0x0002
	*0x0000
	*0x0000

	You ~~can~~ get the Assembly List file by going into the Build Settings->Build->Advanced Options->Assembler, and tick the Generate listing file box. Here is the listing file I got using the MSP430G2553 processor.
	<nowiki>MSP430 Assembler Unix v15.12.3 Tue Nov 1 17:48:13 2016		<nowiki>MSP430 Assembler Unix v15.12.3 Tue Nov 1 17:48:13 2016

Frohro at 00:53, 2 November 2016

2016-11-02T00:53:39Z

@@ Line 1: / Line 1: @@
-Sections start their location counters at zero. The .bss directives don't advance the counter, because they go off to a different section.  Assembly instructions take up bytes of memory according to what they are and their addressing mode.  Whenever a .sect happens the location counter is reset to zero.  There is more in section 2 of this [http://www.ti.com/lit/ug/slau131m/slau131m.pdf TI Manual on the Assembler].  I'm not certain about these, but here is what I came up with.
+Sections start their location counters at zero. The .bss directives don't advance the counter, because they go off to a different section.  Assembly instructions take up bytes of memory according to what they are and their addressing mode.  Whenever a .sect happens the location counter is reset to zero.  There is more in section 2 of this [http://www.ti.com/lit/ug/slau131m/slau131m.pdf TI Manual on the Assembler].  I'm not certain about these, but here is what I came up with, as my best guess.  This quiz is more tailored to the old Assembly List file, that has a field for the section counter.  Code Composer Studio
 *0x0000
@@ Line 14: / Line 14: @@
 *0x0000
 *0x0000

Frohro at 23:46, 1 November 2016

2016-11-01T23:46:54Z

← Older revision		Revision as of 16:46, 1 November 2016
Line 1:		Line 1:
	Sections start their location counters at zero. The .bss directives don't advance the counter, because they go off to a different section. Assembly instructions take up bytes of memory according to what they are and their addressing mode. Whenever a .sect happens the location counter is reset to zero. I'm not certain about these, but here is what I came up with.		Sections start their location counters at zero. The .bss directives don't advance the counter, because they go off to a different section. Assembly instructions take up bytes of memory according to what they are and their addressing mode. Whenever a .sect happens the location counter is reset to zero. There is more in section 2 of this [http://www.ti.com/lit/ug/slau131m/slau131m.pdf TI Manual on the Assembler]. I'm not certain about these, but here is what I came up with.

	*0x0000		*0x0000

Frohro: Created page with "Sections start their location counters at zero. The .bss directives don't advance the counter, because they go off to a different section. Assembly instructions take up bytes..."

2016-11-01T23:45:50Z

Created page with "Sections start their location counters at zero. The .bss directives don't advance the counter, because they go off to a different section. Assembly instructions take up bytes..."

New page

Sections start their location counters at zero. The .bss directives don't advance the counter, because they go off to a different section. Assembly instructions take up bytes of memory according to what they are and their addressing mode. Whenever a .sect happens the location counter is reset to zero. I'm not certain about these, but here is what I came up with.

*0x0000
*0x0000
*0x0000
*0x0002
*0x0008
*0x000a
*0x000c
*0x000e
*0x000e
*0x0010
*0x0002
*0x0000
*0x0000