-
-
Notifications
You must be signed in to change notification settings - Fork 555
Debug
Gives the information on the memory used by M0 core.
Gives information on the SD card and allows it to be tested.
Gives information on the peripherals:
- RFFC5072
- MAX2837
- SI5351C
- WM8731 or Ak4951 (depending on the IC audio codec detected in your PP brd)
Note : Recently (Manufacturing year: 2023) GSG introduced the new r9 Hackrf board version (already compatible with Hackrf and Portapack-Mayhem fw's).
That new Hackrf board revision r9 has two 2 IC’s changes:
- MAX2837 was replaced by MAX2839.
- Si5351C was replaced by Si5351A with additional clock distribution. A series diode was added to the antenna port power supply.
Starting with HackRF One r6, hardware revisions are detected by firmware and reported by hackrf_info.
Thanks to GSG developers and our Mayhem git admin , we merged their commit about all those r9 hw support in our Portapack Mayhem Debug menu tool. And now you can also easily detect that r9 version without disassembling the boards :
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.
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.
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.
Allows testing the Touch Screen calibration (and your artistic skill) by drawing on the screen using a stylus.
The following controls are available:
- Select key returns to Debug menu.
- Left key changes the pen to a random color (hold in the button to rotate through them faster); this can also be done while drawing.
- Down key clears the screen to a random color (like shaking your Etch-a-Sketch).
- Turning the Encoder dial changes the pen size.
To save your masterpiece, note that the screen-shot icon is still active but hidden (it will become visible if that precise spot of the Touch Screen is pressed). Try the Settings -> Touch app for improving calibration of your touchscreen.
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 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)
The version of the stored config isn't displayed separately but it can be seen as the first 4 bytes of the p.mem area.
Writes a file containing debug information to the DEBUG folder.
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.
Writes a file containing M0 stack contents to the DEBUG folder.
Displays the 5x8 and 8x16 font character sets.
Generates a sine wave beep of the specified frequency and duration (0 means an infinite duration) to test the audio output and speaker/headphones frequency response.
Note
The wiki is incomplete. Please add content and collaborate.
Important
- This is a public wiki. Everything is visible to everyone. Don't use it for personal notes.
- Avoid linking to external tutorials/articles; they may become outdated or contain false information.
How to collaborate
How to ask questions correctly
- First steps
- Usage cautions
- Intended use and Legality
- Features
- PortaPack Versions (which one to buy)
- HackRF Versions
- Firmware update procedure
- Description of the hardware
- User interface
- Powering the PortaPack
- Troubleshooting
- Applications
-
Compilation of the firmware
- Compile on WSL with ninja
- How to compile on Windows faster with WSL 2
- Using Docker and Kitematic
- Docker command-line reference
- Using Buddyworks and other CI platforms
- Notes for Buddy.Works (and other CI platforms)
- Using ARM on Debian host
- All in one script for ARM on Debian host
- Compile on Arch based distro (exclude Asahi)
- Dev build versions
- Notes About ccache
- Create a custom map
- Code formatting
- PR process
- Description of the Structure
- Software Dev Guides
- Tools
- Research
- UI Screenshots
- Maintaining
- Creating a prod/stable release (Maintainers only)
- Maintaining rules
- Development States Notes