mirror of
https://github.com/portapack-mayhem/mayhem-firmware.git
synced 2024-11-23 18:15:34 +00:00
Updated Debug (markdown)
Mark Thompson
parent
b06cc380c3
commit
21799eafcc
25
Debug.md
25
Debug.md
@ -1,4 +1,4 @@
|
||||
## Memory
|
||||
## Memory Usage
|
||||
Gives the information on the memory used by M0 core.
|
||||
## SD Card
|
||||
Gives information on the SD card and allows it to be tested.
|
||||
@ -29,10 +29,16 @@ Thanks to GSG developers and our Mayhem git admin , we merged their commit about
|
||||
|
||||
|
||||
|
||||
Individual registers of each peripheral IC can be read or written with this application. If the peripheral has more registers than fits on the screen, the encoder dial can be turned when the Update button is highlighted to view the additional registers. Care should be taken when writing, as it may be possible to cause hardware damage by writing to some memory locations.
|
||||
|
||||
## Temperature
|
||||
|
||||
|
||||
|
||||
## Temperature
|
||||
Data is provided by the MAX 2837 (or MAX 2839) on chip digital temperature sensor. The accuracy is quoted as 4.33°C per value.
|
||||
|
||||
|
||||
|
||||
## Buttons Test
|
||||
This shows when either the buttons are pressed, the encode knob is turned or the screen is touched. It can also show if the encoder when turned is cleanly stepping the states as it is turned. Encoder sensitivity is now adjustable in Settings, and the encoder can be desoldered and replaced with a better-quality version if it has issues. The test screen also has an option for testing the "long press" feature which is applicable to the directional keys and the DFU switch only.
|
||||
|
||||
@ -47,10 +53,12 @@ Allows testing the Touch Screen calibration (and your artistic skill) by drawing
|
||||
|
||||
Note that the screen-shot icon is still active but hidden (it will become visible if that spot of the Touch Screen is pressed).
|
||||
|
||||
## P. Memory
|
||||
## Pers. Memory
|
||||
Displays the contents of the persistent memory area. (256 bytes)
|
||||
|
||||
It is split into three pages, pages can be changes with the encoder and the current offset from the start of p.mem area is displayed on the top: "XX+" Also on the last page theres some padding with FFs displayed after the p.mem area ends.
|
||||
|
||||
|
||||
It is split into three pages, pages can be changes with the encoder and the current offset from the start of p.mem area is displayed in the left column.
|
||||
|
||||
At the bottom it displays also the current size of the data_t struct (this is what we persist into p.mem) and the currently stored checksum (it is calculated from the first 252 bytes of the p.mem area when changes are made to the settings and then written to the last 4 bytes of p.mem)
|
||||
|
||||
@ -59,8 +67,13 @@ The version of the stored config isn't displayed separately but it can be seen a
|
||||
## Debug Dump
|
||||
Writes a file containing debug information to the DEBUG folder.
|
||||
|
||||
## Memory Dump
|
||||
Allows a region of memory to be saved to a file in the DEBUG folder in hexadecimal ASCII format, and allows direct read/write access to specified memory locations for debug purposes. Memory addresses should be a multiple of 4 to avoid causing a fault. Care should be taken when writing, as it may be possible to cause hardware damage by writing to some memory addresses.
|
||||
|
||||
|
||||
|
||||
## M0 Stack Dump
|
||||
Writes a file containing M0 stack contents to the DEBUG folder.
|
||||
|
||||
## Fonts Viewer
|
||||
Displays the 5x8 and 8x16 font character set. (Firmware version 1.7.4 only)
|
||||
## Font Viewer
|
||||
Displays the 5x8 and 8x16 font character sets.
|
||||
|
||||
Loading…
Reference in New Issue
Block a user