amnemonic
commented
10 months ago configmem_dump wired, may be it's that I mess the meaning of that file. I mistake it used for dump firmware.
yes, it is used to dump configuration memory which is in EEPROM chip, dump firmware is possible only via SWD pads on PCB.
can I use a python script to flash firmware?
I was planning to add this option but after time I forgot about this. I've prepared this method which was intended to do the task. However finally I've decided to use official flashing app as it is safer.
piotr022/UV_K5_playground has a mem-map show start at 0x10C0(or Ox1000). But your docs shows flash start at 0x0F000 and end at 0x0FFFF
good point, when I was creating my memory map there was no possibility to "look" inside chip using SWD yet and firmware dumps, boot loader etc was obtained using modified functions running in firmware stock firmware, and the thing is that in FLASH memory of MCU boot loader is located at 0x0000 and regular firmware at 0x1000 but when boot process finishes then flash memory is remapped and then regular firmware is accessible at 0x0000 and bootloader at 0xF000
BackMountainDevil
bczhc
get_version, adc_read, batt_calibrator, reboot_radio, configmem_dump, configmem_read, configmem_write are tested and work good
configmem_dump wired, may be it's that I mess the meaning of that file. I mistake it used for dump firmware.
ps: can I use a python script to flash firmware? I tried use dnSPY to find out the address, lengeth, baudrate but failed cz I am not good at dnSPY. Good news your code shows the baudrate is 38400. piotr022/UV_K5_playground has a mem-map show start at 0x10C0(or Ox1000). But your docs shows flash start at 0x0F000 and end at 0x0FFFF
detail：