prof-braino / propforth Goto Github PK

What steps will reproduce the problem?

Need word to de-initialize SD card. This would be use for re-running the 
SD-init tests, also possible for wiping card?

What is the expected output? What do you see instead?

After executing de-init word, card should cause same behavior as a card that 
has not be initialized by sd_scripts.  That is, no partitions defined, not 
autoboot files defined. If possible, also remove FAT formating, not a critical 
requirement.  

presently, it is hard to get an SD card back to an original state, the result 
can be that the card does not respond until formatted by windows(?). 

Please use labels and text to provide additional information.

Per discussion 20110626

What steps will reproduce the problem?
After RESET:
  Prop0 Cog6 RESET - last status: 0 ok
  Prop0 Cog6 ok
  free
  15048 bytes free - 161 cog longs free
  Prop0 Cog6 ok
After fsload sd_driver.f (from EEPROM):
  Prop0 Cog6 ok
  free
  12544 bytes free - 161 cog longs free
  Prop0 Cog6 ok
After fsload sdfs.f (from EEPROM)
  Prop0 Cog6 ok
  free
  8446 bytes free - 161 cog longs free
  Prop0 Cog6 ok
  decimal
  [ifndef mountsys : mountsys 0000000001 sd_mount ; ]
  \ mountusr ( -- ) mount the user disk
  [ifndef mountusr : mountusr 65538 sd_mount ; ]
  mountsys
  Prop0 Cog6 ok
  free
  8404 bytes free - 4 cog longs free
  Prop0 Cog6 ok

then:
  fsload unload_sd.f  \ it would nice to be able to "unmount" in unload_sd.f to free up the COG space
  forget build_sddriver
  Prop0 Cog0 ok
  Prop0 Cog6 ok
  free
  15048 bytes free - 4 cog longs free
  Prop0 Cog6 ok
What is the expected output? What do you see instead?

  - Expected 161 longs free again instead of 4

What version of the product are you using? On what hradware?
 V4.5 on Gadget Gangster prop module

Please provide any additional information below.
 - reported by user mindrobots prop forum post
http://forums.parallax.com/showthread.php?132332-PropForth-4.5-Available-for-dow
nload&p=1010557&viewfull=1#post1010557

Consider Change to Propforth Design to add a Requirement for a Configuration 
Log file.

What is the expected output? What do you see instead?

A file (in EEPROM? on SD) is maintained to record the currently loaded support, 
in the context of "load and forget" functionality.

Please use labels and text to provide additional information.

Per discussion 20110626

What steps will reproduce the problem?

.digits tests "a >", should be "9 >"

Lines 27, 28, 29

What is the expected output? What do you see instead?

The code to set the text color in red is commented out of the interpret word

I was beginning to like this, can we put it back?

What steps will reproduce the problem?

Consider Change to Propforth Design to add a Requirement for a VMS style file 
backups.

What is the expected output? What do you see instead?

Files on the disk are associated with a serial number; date time stamp if 
available or sequenctial otherwise.   
When a file is saved or written to media, the file recieves a stamp.
When tehfile is changed, a new copy with a new stamp is saved.  
All previous versions are left intact on the disk.
Files are written with at least 1 empty block on the end by default.  If a file 
is does not have at least 1 empty block, the next save allocates 1 more block 
to the file, and saves it with the new stamp. 

User is responsible for clearing old files (re-init SD and copy most recent 
file to new disk)

Please use labels and text to provide additional information.

Per discussion 20110626

from caskaz:

>> Incorrect comment for word"nip" in PropForthPart1.f
>> ( x1 x2 -- x1 ) --> ( x1 x2 -- x2 )

1 2 nip
st?
ST: 00000002

What steps will reproduce the problem?
 -  One of the steps in a 1.x.x test should verify the version string. 

 - Should this be in the Load kerenl tests 1.1.1 & 1.1.2,
or in the regenerate kerenl tests 1.1.3 & 1.1.4?

What is the expected output? What do you see instead?

 - proper version string check in at least on test

Please use labels and text to provide additional information.

What steps will reproduce the problem?
test-1.2.1 LoadLogicAnalyzer.txt

4. The following uses cog 5 and sets pins 0 and 1 oscillating. Make sure there 
is nothing connected to these pins that would interfere, or cause a problem.

- add -

4. The following uses cog 5 and sets pins 0 and 1 oscillating. Make sure there 
is nothing connected to these pins that would interfere, or cause a problem. 

Terminal program (Teraterm) must be set to at least 130 columns by 65 rows for 
sampling to display properly.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

What steps will reproduce the problem?
   test-2.1.1 SD.txt

5. paste contents of sdfs.f (sd) into teraterm
   saveforth
   reboot

   ADD NOTE to the affect that that if the SD card has already been initialized, the reboot will cause the previous initialization's autoboot script to run.

   User should hold down ESC key after reboot
        -or-
   remove SD card from slot; error message will be 166 unknown error
(SD card not Found)

  A.  Does error 166 come from other causes or can we assume it is SD card not found/not present/did not initialize?

  B.  Can a step be added BEFORE this step to "wipe the SD"?  This is the discussion we had about including code for a dangerous word that word completely wipe the SD card of any forth and perhaps FAT formatting. 

What is the expected output? What do you see instead?

  Stated result only occurs using virgin card, once an SD card is initialized the autoboot script runs

Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. type fl from command line, or paste from file
2. when paste operation is complete, type st?
3.

What is the expected output? What do you see instead?
Prop0 Cog6 ok
st?
ST:
Prop0 Cog6 ok
fl

Prop0 Cog6 ok
st?
ST: 0000000000
Prop0 Cog6 ok


Please use labels and text to provide additional information.

What steps will reproduce the problem?

test-1.3.2 EEPROMfsRD.txt

change line

4. Must have run test-3.1.1,  So that a file FSWRITE.F is in the EEPROM File 
System
-should be-
4. Must have run test-1.3.1,  So that a file FSWRITE.F is in the EEPROM File 
System


What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

What steps will reproduce the problem?
test-1.1.1 LoadDevKernel.txt

Def_0verflowtest

---
: overflowtest 40 0 do i . i loop cr ;
###
: overflowtest 40 0 do i loop cr ;
Prop0 Cog6 ok
%%%

What is the expected output? What do you see instead?
: overflowtest 40 0 do i loop cr ;
Should be
: overflowtest 40 0 do i . i loop cr ;


Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. Examine PropForth.spin
2. Search for "base"
3. Notice instead of "BASE", the definition has the identifier "mcwBase"

What is the expected output? What do you see instead?
BASE is the expected identifer for the variable that holds the current number 
base, per the standard.
mcwBase is not per the standard

Please use labels and text to provide additional information.

NOTE: fix to be implemented in version 3.0

What steps will reproduce the problem?

  user caskaz had problems with using the code for EEPROM fs and SD fs.
The code was correct, but he didn't under about power cycling after swapping 
cards. 

  http://forums.parallax.com/showthread.php?133312-PropForth4.6-is-available-for-download&p=1025223&viewfull=1#post1025223

What is the expected output? What do you see instead?

   Instructions need improvement to clarify intended use.  
   Include comments in code
   Include comments in test case
   Indicate proper commands to execute to initialize card after swap without power cycle. 

Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. Loading code containing the comment character \ with the 'FL' command
cause the lines to be 'truncated' into one big line when echoed,
eventually causing an over run "UNDEFINED WORD" message for defined words.

This cuases an issue around yellow: 

: color_list
color dup
1f swap W! 2+ dup    \ blue
f800 swap W! 2+ dup    \ red
f81f swap W! 2+ dup    \ magenda
7e0 swap W! 2+ dup     \ green
7fe swap W! 2+ dup     \ cyan
ffe0 swap W! 2+ dup    \ yellow
ffff swap W! 2+ dup    \ white
a18a swap W! 2+ dup    \ brown
fbc0 swap W! 2+ dup    \ orange
f998 swap W!           \ pink
drop
;
2.
This has no issue:

variable color
: color_list
color dup
1f swap W! 2+ dup      
\ blue
f800 swap W! 2+ dup    
\ red
f81f swap W! 2+ dup    
\ magenda
7e0 swap W! 2+ dup     
\ green
7fe swap W! 2+ dup     
\ cyan
ffe0 swap W! 2+ dup    
\ yellow
ffff swap W! 2+ dup    
\ white
a18a swap W! 2+ dup    
\ brown
fbc0 swap W! 2+ dup    
\ orange
f998 swap W!           
\ pink
drop
;

actual example is LCD020 from parallax forum thread
http://forums.parallax.com/forums/default.aspx?f=25&p=4&m=468264#m474031

Please use labels and text to provide additional information.

What steps will reproduce the problem?
  - Tests 1.x.x (and 2.x.x) specify spinneret instead of allowing ANY prop board.
  - Spinneret is not required until Test 3.1.1,  which has prerequisite 2.1.1 SD. 

What is the expected output? What do you see instead?

 - Can this be sorted out by defining a test 3.1.0 that sets up the initial state for the 3.1.x spinneret tests?  

Please use labels and text to provide additional information.

What steps will reproduce the problem?

test-4.1.1 SerialLoopback.txt
step  4. Must have run test-3.1.1,  So that a file FSWRITE.F is in the EEPROM 
File System

states prerequisite test is  test 1.3.2 (and 1.3.2 incorrectly states 
prerequisite  test-3.1.1, should be 1.3.1)

BUT 4.1.1 is on PROTOBOARD, 1.3.1 and 1.3.2 were on SPINERET

-suggestion-

reword step 4 to include

step  4. Must have run test-3.1.1 ON PROTOBOARD,  So that a file FSWRITE.F is 
in the 

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

What steps will reproduce the problem?

test-3.1.2 RTC.txt
6. paste contents of rtc.f (rtc) into teraterm

Please add step to edit rtc.f for current timezone

\ variable timezone -8 timezone L!  \ Vancouver timezone
variable timezone -6 timezone L!    \ Chicago  timezone


What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. WORD "test
"\" position is column 113
Loaded WORD "test".
: test
1 1 + .
                            \ skip until ["]
;

2.Loaded WORD"test.
error occur UNDEFINED WORD "].
But no error when "\" position is column 112.


What is the expected output? What do you see instead?
"\" should skip characters until D.
But it seems WORD definition is executed. 

What steps will reproduce the problem?
1.
2.
3.
test-1.2.1 LoadLogicAnalyzer.txt
LogicAnalyzer.f
lac
require TWO enter key presses to begin sampling, 
instead of one as indicated

What is the expected output? What do you see instead?
At first press of enter key, there is no response or change in display

Please use labels and text to provide additional information.

Plese delete this.

base exhibits unusual behavior

1.  Setting BASE to binary 
1 base W!
Cog
causes lockup at the point where the cog number should be displayed

Reset must be pressed, or power cycled

2. setting base does not affect stack diagnostic word st?
9 a b c d e f 10 decimal st?
00009 0000a 0000b 0000c 0000d 0000e 0000f 00010
. 16
. 15




Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. compile PropForth v2.5 and load on eeprom
2. execute saveforth (whenever)
3. reboot or make HW reset


What is the expected output? What do you see instead?
Forth should start up again with a:
"
Forth cogs: 5 - 6
Cog6 ok
"
but nothing happens at all, until I reload the spincode on the eeprom

What version of the product are you using? On what operating system?
2.5 on a Propstick USB (32k)

* is not defined
u* is defined

What steps will reproduce the problem?
1. If a cog is running and a cogreset is issued the cog common area iz
zeroed while the cog is still running. This may cause issues depending on
what the cog being reset is doing. 


Workaround:
Redefine cogreset, will be fixed in the next release

\ cogreset ( n1 -- ) reset the forth cog
: cogreset 7 and dup cogstop dup dup cogd dup 100 0 fill 10 lshift cm_entry
2 lshift or or 2 hubop 2drop 
\ wait for the cog to come alive
cogDebugvalue 8000 0 do dup m@ if leave then loop drop ;

What steps will reproduce the problem?
1. boot up
2.
3.

What is the expected output? What do you see instead?
propforth v2.5...etc

What version of the product are you using? On what operating system?


Please provide any additional information below.

What steps will reproduce the problem?
1. Load propforth.spin
2. reboot
3. check version string

What is the expected output? What do you see instead?

     Expect to see

PropForth v4.6 2011JUL25 7:10 0

     Instead of 

PropForth v4.5 2011JUL25 7:10 0

Please use labels and text to provide additional information.

With Propforth 3.4 HiResVGA is loaded on the demo board:

Unplug the USB cable.

Demo board resets continuously.

With Propforth 3.4 (regular kernel) loaded on demo board:

Unplug USB cable.

RED LED flickers every couple seconds.

Could be same issue?

Reported by drohne235

What steps will reproduce the problem?
1. load debugger
2. run debugger on a word that puts a number on the stack
3. execute the word to the point the number is put on the stack

What is the expected output? What do you see instead?
Expected result is stack display show new entries added to the right.
Instead we see new numbers are added to the left.

Please use labels and text to provide additional information.
Per walkthrough 20100613

Hi salsanci & prof_braino.

I found out very little mistake on PropForth.spin.

\ lockclr (n1 -- n2) set lock n1...........the lock was set ... --> clear lock 
n1 .... the lock was clear ...

: checkdict here W@ + dictend W@ >=
if cr here W@ . dictend . _eoom clearkeys reset then ; --> if cr here W@ . 
dictend W@ . _eoom clearkeys reset then ; 

What steps will reproduce the problem?
1.Fresh load of 4.3 Beta
2.reboot
3.copy/paste fs.f

--------------
decimal         \ last line of fs.f copy/paste
Prop0 Cog0 ok

Prop0 Cog0 ok

Prop0 Cog0 ok

Prop0 Cog6 ok
fsclear
Prop0 Cog6 ok
fsls


98304  bytes free in files system

Prop0 Cog6 ok
decimal
Prop0 Cog6 ok
fsls


CON:Prop0 Cog6 RESET - last status: 90 UNKNOWN ERROR

Prop0 Cog6 RESET - last status: 90 UNKNOWN ERROR
Prop0 Cog6 ok
hex
Prop0 Cog6 ok
fsls


18000  bytes free in files system

Prop0 Cog6 ok

--------------

What steps will reproduce the problem?
1. Start a definition using create: create MyArray
2. execute MyArray
3. execute st?

What is the expected output? What do you see instead?
Expected output is data field of MyArray (DPANS94 6.1.1000)
However, no value is left on stack

http://forums.parallax.com/forums/default.aspx?f=25&m=468264&p=4

Please use labels and text to provide additional information.

What steps will reproduce the problem?

 - sd_driver.f lines 116 to 121 span 6 i/o pins, sufficient to accommodate 4 bit transfer.  But code to define pins 11 and 12 is not present.  code to define pins 11 and 12 could be present, but commented out.

What is the expected output? What do you see instead?

 - exiting code:
\ definitions for io pins connecting to the sd card

13 wconstant _sd_cs
14 wconstant _sd_di
15 wconstant _sd_clk
10 wconstant _sd_do

 - could be:
\ definitions for io pins connecting to the sd card

10 wconstant _sd_do  \ _sd_dat0
\ 11 wconstant       \ _sd_dat1
\ 12 wconstant       \ _sd_dat2
13 wconstant _sd_cs  \ _sd_dat3
14 wconstant _sd_di  \ _sd_cmd
15 wconstant _sd_clk


Please use labels and text to provide additional information.

What steps will reproduce the problem?
1.Propeller system with 2 64K EEPROMs

2."fswrite" files until one of them is written straddling the $FFFF/$10000 
boundary.

3. execute "fsload filename.ext" of the file straddling the boundary


What is the expected output? What do you see instead?

1. expected - clean load of file

2. observed - file loads clean as far as the byte at $FFFF, then it outputs the 
ASCII digit "4" and starts feeding bytes from $10014. It generally always 
causes an UNDEFINED WORD error.


Error is repeatable and consistent. Behavior seems to have no dependence on 
where in file the boundary crossing occurs.

Current workaround is to carefully load files, observing sizes to within $100 
bytes of $10000, then load a dummy file that just crosses the boundary, then 
continue to load working files. The files beyond the dummy will "fsload" just 
fine.

What steps will reproduce the problem?
1. highlight and copy the text "fsload LogicAnaLyzer.f" from readme.txt
2. paste the text into propforth using the teraterm window

What is the expected output? What do you see instead?
-Expect to see the text for LogicAnaLyzer.f scrolling down the window as it is 
compiled into the dictionary
-Instead, there is a single blank line and the propforth prompt OK.
There is no error message displayed

Please use labels and text to provide additional information.
-Typing the text "fsload LogicAnaLyzer.f" into the teraterm window DOES make 
the text for "fsload LogicAnaLyzer.f" scroll down the window as it is compiled 
into the dictionary.

What steps will reproduce the problem?
1. discovered during review 20100627
2. if create failed, lfa will be invalid next time
3. Sal to fix for v3.2


What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

What steps will reproduce the problem?
1.When bytes define by WORD"c," last odd byte is not defined.

What is the expected output? What do you see instead?
[code]
wvariable sample_1 01 c, 02 c, 03 c, 04 c, 05 c, 06 c, 07 c, 08 c, 09 c, 0a c,
wvariable sample_2 01 c, 02 c, 03 c, 04 c, 05 c, 06 c, 07 c, 
: test1
a 0 do
sample_1 2+ i dup . + C@ . cr 
loop
cr
9 0 do
sample_1 2+ i dup . + C@ . cr 
loop
cr
7 0 do
sample_2 2+ i dup . + C@ . cr 
loop
;
[/code]
Executed above.
1st and 2nd loop is ok.
Result is last loop on test1 below;
[code]
0 1
1 2
2 3
3 4
4 5
5 6
6 62
[code]
I checked it ramDyump and wordDump.
There is no value"07".



What version of the product are you using? On what hradware?
PropForth4.0a
ProtoBoard

Please provide any additional information below.

What steps will reproduce the problem?
{{{
\ _treg5 tx reg , _treg3 rx reg
__7trreg
        mov _treg6 , # 20
__Flp
            test    v_pinin , ina wc
-------------->         rcl _treg3  , # 1     <---------
            shl _treg5  , # 1 wc
            muxc    outa , v_pinout
        djnz    _treg6  , # __Flp wz
        test    v_pinin , ina wc
------------>   rcl _treg3  , # 1  <--------------------
__8trregret
        ret

}}}
What is the expected output? What do you see instead?

I'm a bit concerned about the way bits are collected. The loop itself rotates 
32 bits into _treg3 and then one more after leaving the loop. This may be 
perfectly OK if the first sample is not part of the data (maybe start bit). 
Could you ask Sal(?) for clarification? Thanks.

What version of the product are you using? On what hradware?

mcs.f - code review

Please provide any additional information below.

user kuroneko -  master of clocks and counters

Purpose of code changes on this branch:
20110131 Review for SD support v 3.0 per webpage 
http://code.google.com/p/propforth/wiki/CodeReviewSDsupport

When reviewing my code changes, please focus on:
CLARITY intial instructions
SEQUENCE of files
ADHERENCE to specification
Stack notes and comments 
correctness of algorithm(s)

After the review, I'll merge this branch into:
/trunk
SD support 4.0

What steps will reproduce the problem?
Update SD doc to include 0.1uF capacitor info:
Not needed it power and ground plane are sufficient;
required if long wires are present.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. Prop board with 2 64K EEPROMs at I2C addresses 0 and1
2. load PropForth.spin
3. load fs.f

What is the expected output? What do you see instead?

1. Do an fsls and you should get a clean display with $8000 bytes free with one 
EEPROM
With two EEPROMs display is compromised and it says -3500 (minus) bytes free

2. Load PropForth.f

3. fswrite fails and dumps everything to console and it looks like just about 
all the words make it to the dictionary. In the end "..." is misinterpreted as 
UNDEFINED.

What version of the product are you using?

1.0 PropForth 4.0


Please provide any additional information below.

1. Same hardware, remove second EEPROM works fine

Kaz submitted sin_wave routine, stating following execution times
Hi.  I made sine_wave. But very slow. For 1-cycle:

Assembler is    9msec.
PropBasic is   16msec.
Spin is       800msec
PropForth is 15000msec (15seconds).
Is this correct? Somewhere wrong?

Verified the following code takes 15 seconds to execute 200,000 iterations on 
prop demo board

e000 wconstant sine_start
f001 wconstant sine_end
variable dT

: sin
0 pinout       \ output P0 
18000000 ctra COG!   \ DUTY-single-end APIN=P0
clkfreq 21f u/ dT L!
dT L@ cnt COG@ +
100 0 do
2000 0 do      \ 0 - 360degree                        
     7ff i and 1 lshift
     i 1000 and 0= if      \ 0 - 180degree or 180 - 360degree                        
          i 800 and 0= if 
               sine_start + W@ f lshift 7fffffff + frqa COG!     \ 0 - 90degree
               else
               sine_end swap - W@ f lshift 7fffffff + frqa COG!        \ 90 - 180degree
               then
     else
          i 800 and 0= if 
               sine_start + W@ f lshift 7fffffff swap - frqa COG!     \ 90 - 270degree
               else
               sine_end swap - W@ f lshift 7fffffff swap - frqa COG!        \ 270 - 360degree
               then
     then
     dT L@ waitcnt
     loop
 loop
;

What steps will reproduce the problem?

  - Test 2.1.1 SD speciefies Spinneret instead of ANY prop with SD hardware

What is the expected output? What do you see instead?

1. Connect Propclip to the Spinneret Board or similar with SD slot hardware 
(adjust sd_driver.f lines 116 to 121 I/O pin definitions for pins  16, 17, 18, 
19, 20, and 21 per SD slot connections)

2. load PropForthKernel.spin (main) into eeprom.
(renumber remaining steps)
2->3. Start teraterm, 57.6 kb, no other change setting should be necessary.

3->4. A microsd card must be installed. These tests will DESTROY ALL DATA on 
the card. If the card has already been initialized, it will run the 
intialization scripts on boot. To prevent this hole down the escape key while 
rebooting. The escape key should be held down until the forth prompt appears.


Please use labels and text to provide additional information.

What steps will reproduce the problem?
-currently-
9. We now see cog0 is connected to the serial driver running on cog1. After 
running 2.0 term hit enter a couple of times.
-should be-
9. We now see cog0 is connected to the serial driver running on cog1. After
running 2 0 term hit enter a couple of times.


What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. Define word that uses "a"
: .BASE BASE w@ dup 10 = if ." Hex " else
                dup a  = if ." Decimal " else
                dup 2 = if ." Binary " else
                    ." Unusual "  then then then drop;
2.  Change BASE to 3  >>>  3 BASE W!
3.  Load word .BASE

What is the expected output? What do you see instead?
Expected:
UNDEFINED WORD a
Cog6 ok
Instead:
UNDEFINED WORD a  << Lockup >>

What steps will reproduce the problem?
test-1.2.1 LoadLogicAnalyzer.txt

Please change: 

6. Hit escape to sample

to: 

6. Hit escape to end sampling


What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

What steps will reproduce the problem?
 - Test 4.1.1 specifices protoboard hardware and indicate test 1.3.1 as prerequisite.
 - However test 1.3.1 specifies spinneret hardware

What is the expected output? What do you see instead?
  -  Can a test 4.1.0 specify establish all set up conditions for 4.x.x series? 

Please use labels and text to provide additional information.

What steps will reproduce the problem?

Please bring VGA support to v5.x when assembler changes are complete.
Per Demoboard pinout for VGA, Keyboard, Mouse
(Mouse is not critical at this time)

What is the expected output? What do you see instead?

NOTE: Demoboard uses pins 16-23 for VGA, this creates conflict with Spinneret 
SD configuration on pins 16-21, previously stated as "default". 

Doug has Demoboard SD added to pin 2-7 

Please use labels and text to provide additional information.

What steps will reproduce the problem?
test-1.1.1 LoadDevKernel.txt

  overflowtest

  Request to change 

: overflowtest 40 0 do i loop cr ;

  to

: overflowtest 40 0 do i dup . loop cr ;

What is the expected output? What do you see instead?
Change will demonstrate point at which overflow occures

Please use labels and text to provide additional information.