Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
pmod:pmodjstk2:reference-manual [2021/05/14 23:03] – ↷ Page moved from reference:pmod:pmodjstk2:reference-manual to pmod:pmodjstk2:reference-manual Arthur Brownpmod:pmodjstk2:reference-manual [2022/10/04 11:38] (current) – external edit 127.0.0.1
Line 76: Line 76:
  
 ===== Using the High Endurance Flash ===== ===== Using the High Endurance Flash =====
-The calibration constants that the module uses are loaded into %%RAM%% from the High Endurance Flash (HEF) during the firmware initialization which occurs shortly after power is supplied. If a calibration sequence is performed, new calibration constants are loaded into %%RAM%%. In general, it is not necessary to then write the new calibration constants in %%RAM%% to the HEF unless the user wishes to have those new calibration constants available after a power cycle. The factory loaded calibration constants are available in the header file for the Pmod JSTK2 in the [[reference:pmod:pmodjstk2:start#example_projects|Example Code]].+The calibration constants that the module uses are loaded into %%RAM%% from the High Endurance Flash (HEF) during the firmware initialization which occurs shortly after power is supplied. If a calibration sequence is performed, new calibration constants are loaded into %%RAM%%. In general, it is not necessary to then write the new calibration constants in %%RAM%% to the HEF unless the user wishes to have those new calibration constants available after a power cycle. The factory loaded calibration constants are available in the header file for the Pmod JSTK2 in the [[pmod:pmodjstk2:start#example_projects|Example Code]].
  
 If the user does want to store the calibration constants in a more permanent fashion, they may issue a command to write the constants from %%RAM%% to Flash, but it is recommended to wait at least 5 milliseconds once the Chip Select goes high after the data transfer is complete because the device is unable to respond to traffic on the SPI bus. If the user does want to store the calibration constants in a more permanent fashion, they may issue a command to write the constants from %%RAM%% to Flash, but it is recommended to wait at least 5 milliseconds once the Chip Select goes high after the data transfer is complete because the device is unable to respond to traffic on the SPI bus.
Line 86: Line 86:
 ======= Command Summary ======= ======= Command Summary =======
  
-A list of commands supported by the Pmod JSTK2 [[reference:pmod:pmodjstk2:start#example_projects|library code]] is provided below.+A list of commands supported by the Pmod JSTK2 [[pmod:pmodjstk2:start#example_projects|library code]] is provided below.
  
 ===== Get Commands ===== ===== Get Commands =====
Line 123: Line 123:
 |  6    |  VCC     |  Power Supply (3.3V)  | |  6    |  VCC     |  Power Supply (3.3V)  |
  
-Although users are welcome to create their own interface code for the Pmod JSTK2 if they so desire, although pre-constructed libraries that provide functions for initializing the module, reading in values, and adjusting calibration values exist. They are available on the %%Pmod JSTK2%% [[reference/pmod/pmodjstk2/start#example_projects|Example Code section]].+Although users are welcome to create their own interface code for the Pmod JSTK2 if they so desire, although pre-constructed libraries that provide functions for initializing the module, reading in values, and adjusting calibration values exist. They are available on the %%Pmod JSTK2%% [[pmod:pmodjstk2:start#example_projects|Example Code section]].
  
 Any external power applied to the %%Pmod JSTK2%% must be within 2.95V and 5.5V; however, it is recommended that Pmod is operated at 3.3V. Any external power applied to the %%Pmod JSTK2%% must be within 2.95V and 5.5V; however, it is recommended that Pmod is operated at 3.3V.
Line 133: Line 133:
 The schematics of the %%Pmod JSTK2%% are available {{reference:pmod:pmodjstk2:PmodJSTK2_sch.pdf|here}}. Additional information about the PIC16F1618 including communication modes and specific timings of the chip can be found by checking out its datasheet [[http://ww1.microchip.com/downloads/en/DeviceDoc/40001769B.pdf|here]]. The schematics of the %%Pmod JSTK2%% are available {{reference:pmod:pmodjstk2:PmodJSTK2_sch.pdf|here}}. Additional information about the PIC16F1618 including communication modes and specific timings of the chip can be found by checking out its datasheet [[http://ww1.microchip.com/downloads/en/DeviceDoc/40001769B.pdf|here]].
  
-Example code demonstrating how to get information from the %%Pmod JSTK2%% can be found [[reference/pmod/pmodjstk2/start#example_projects| here]]. +Example code demonstrating how to get information from the %%Pmod JSTK2%% can be found [[pmod:pmodjstk2:start#example_projects| here]]. 
  
 If you have any questions or comments about the %%Pmod JSTK2%%, feel free to post them under the appropriate section ("Add-on Boards") of the [[https://forum.digilentinc.com/|Digilent Forum]]. If you have any questions or comments about the %%Pmod JSTK2%%, feel free to post them under the appropriate section ("Add-on Boards") of the [[https://forum.digilentinc.com/|Digilent Forum]].