- #Display led during receive tyt uv8000e how to
- #Display led during receive tyt uv8000e driver
- #Display led during receive tyt uv8000e code
The value in register 0x0F was inspected or overwritten while transmitting. With a modified Python script ( tool2.py), In the original CPS'es ' Test Mode' screen. The original firmware possibly initialises this register based on the settings The read-out value (ADLinVol=0b11001) is different from the default. 11001 = (12 - 25*1.5) dB = -25.5 dBĪt the time of this writing, it wasn't clear where and why the MD380 firmware modifies |||| ||||_ bit 0 : not specified in the HR_C5000 datasheet The md380-tool (Python script invoked above) showed register 0x0f contained 0xC8. The datasheet (partially translated from Chinese to English) says ' MicGain' is a bitgroup =0x00 =0x08 =0x00 =0x00įor example, the author wanted to know the 'microphone gain' setting. $ python md380_tool.py c5000 # Prints some DMR registers. # before accessing USB from Python /c/tools/md380tools $ c:/tools/libusb-win32/bin/amd64/testlibusb-win.exe # DL4YHF: for windows, tickle USB $ cd c:/tools/md380tools /c/tools/md380tools This can be achieved via Python script, by calling c5000() in md380_tool.py : In the 'hooked' usb.c : usb_dnld_hook(), c5000_spi0_readreg() and c5000_spi0_writereg() can be called. See english translation, chapter 8, 'data read and write'.
#Display led during receive tyt uv8000e how to
How to access registers inside the HR_C5000 chip is described in the datasheet, In the md380tools pulled from Github in 2016-12, this was already the case.Īt the time of this writing (2016-12), c5000_spi0_readreg() was still the original code, To use some of these diagnostic functions, some of the macros in config.h must be defined,įor example CONFIG_SPIC5000 to read and (for the brave-hearted) write registers in the C5000 as explained below.įor this feature, CONFIG_SPIC5000 must be defined in config.h. |_ util.c mkascii(), uli2w(), strhex(), wstrhex() |_ usersdb.c implements the DMR user database, find_dmr(), etc |_ usb.c USB Hook functions, optional C5000 register access via USB, etc |_ system_stm32f4xx.c Low-level CPU initialisation |_ stm32f4xx_it.c default interrupt handlers for STM32F4xx |_ rtc_timer.c wrapper functions for the "RTC Timer"-Task |_ printf.c subroutines for lightweight 'printf' |_ os.c Hook functions for the real time OS |_ netmon.c 'highly volatile' network monitor, controlled via hotkeys
#Display led during receive tyt uv8000e driver
|_ lcd_driver.c Much faster LCD driver for text output |_ keyb.c implements a few hotkey functions |_ irq_handlers.c interrupt handlers, first used for ' dimmed backlight' |_ i2c.c i2c Hooks and diagnostic functions |_ dmr.c hooks some of the DMR packet handler functions |_ dmesg.c Kernel logging functions and buffers |_ display.c high-level drawing functions |_ dispinit.c display_reset(), display_init() |_ console.c simple text console for netmon |_ app_menu.c alternative menu, opened via red BACK button |_applet/src : Contains most interesting parts of the patched firmware. | First calls SystemInit(), then main(), as CMSIS wants us to :o)
#Display led during receive tyt uv8000e code
| |_ startup_stm32f4xx.s interrupt vector table and 'early startup' code |_applet/lib : STM32F4xx peripheral library from STM. | No MD380 specific functions in these stm32_. |_applet/inc : 'Library configuration file' by ST. | > porting to a new target application version. | > unstable features or to disable standard features when | > Configures our patches, either to temporarily enable
The links to the C sources below only work after copying this file into ?/md380tools/docs !
An own menu (independent of the original firmware).
Dimmed 'ambient' backlight for the display.Own experiments with / additions to the experimental firmware.Hooked functions (in the original firmware).Processing of analog inputs (volume pot, battery voltage, etc).Disassembling parts of the original firmware.See also: RT3/MD-380 hardware, RT3/MD-380 index (by DL4YHF) The fourth part describes a few of the author's experiments with own additions to the experimental firmware. With the intention of 'trying to understand' which hardware resources (timers, audio interface, etc) The third part contains fragments of information about the original firmware, The second part contains the description of firmware modifications tried by DL4YHF.įor a complete and up-to-date documentation, build your own (using Doxygen or similar) from the source,Īnd see what's in the most recent distribution of Travis Goodspeed's MD380 Tools ! The first part of this file contains a 'heavily linked' overview of the patches for the MD380 / RT3 firmware.Īnything in this file is an 'interpretation' of DL4YHF, which may be utterly wrong. ('informal' and most likely outdated, by DL4YHF, )