Welcome to uv-k5-firmware-custom Discussions!

[muzkr]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[idrugiput-netizen]

Hi, I have a question, does version 4.3 for V2 py032f030 support the larger versions of the 1Mb or 2Mb eeprom chip (M24M01, M24M02). I would like to replace the original eeprom with one of these

[muzkr]

I won't give you a simple “yes/no” answer, but here's some information for your reference:

1. Ensure the chip footprint fits
2. Note that address pins A0:2 are grounded. The firmware uses a bit-banged I2C implementation with a 7-bit address of 0x50, but you can modify the code to match your address.

[idrugiput-netizen]

The original eeprom is BL24C64A. there are videos on youtube where the factory is changed with M24M01 or M24M02, but in order for the radio to recognize them, they flashed the firmware IJV, FAGCI reborn, cec fw.. so I'm interested in whether this F4HWN firmware would also recognize larger chips

[ErikS-web]

PCB version 1.8 does support 2 places for an eeprom. Remove the 64 and place 2 new eeproms.

For practical tips, see Multiboot project of Losehu for V1 radio, with some nice pictures in the Wiki

https://github.com/losehu/uv-k5-bootloader-custom/wiki/40-%E2%80%90-Step%E2%80%90by%E2%80%90step-plan#-2--stack-2-x-m24m02rd-eeproms

[ErikS-web]

@muzkr Thanks for your work.

Just used your https://github.com/muzkr/uv-k5-firmware-custom/releases/tag/v4.3
with https://github.com/muzkr/uv-k5-firmware-custom/blob/v2/archive_V2/v4.3/f4hwn.bandscope.bin

and seems to work OK

Question... would you consider to port Nunu firmware. I do prefer his Memory / Spectrum channel Scan.

[muzkr]

Hello!

First, the answer to your question is no.
Second, I welcome any V1 firmware author to use the code from this repository (especially the hardware driver portion) to enable their firmware to support V2.
Third, users of this repo's v4.2 firmware SEEM satisfied, so I'm confident the v4.3 firmware works well.

[idrugiput-netizen]

Today I received the uvk5 v3 (with 512kb,) and I immediately inserted the firmware f4hwn v.4.3.2 and I compared the sound with another uvk5 v2, firmware f4hwn v.4.3 for version 2, and I can say that the v2 has a much sharper sound, with more hiiss .. is it due to the firmware or is it due to the hardware?by the way, I like the sound on v3 much more, and I wonder if it can be the same on v2, is it something to do with firmware 4.3(v2)

[muzkr]

Hello!
I'm afraid I'm not qualified to answer your question. However, I can tell you that the V3 vs V2 represents a major hardware change. Just looking at the radio chip alone, V2 uses the bk4819, while V3 uses the bk4829. By comparison, the V1 to V2 upgrade involved a minor hardware change, merely replacing the MCU. Empirically speaking, if your V2 performs on par with the V1, it indicates that both the hardware and firmware are functioning correctly.
I'm extremely interested in the "512kb" you mentioned in your comment. I understand you're referring to the V3 you purchased having 64KB of SPI flash. I always thought the K5 V3 had 2MB of SPI flash. If a 64KB version exists, that would be quite a novelty. I'm quite skeptical that you misunderstood. Could you clarify? After all, SPI flash smaller than 2MB is quite rare.

[idrugiput-netizen]

https://www.aliexpress.com/item/1005006887181974.html?spm=a2g0o.order_list.order_list_main.21.78c81802Dx07Bm
M24M02-DRMN6TP
M24M01-RMN6TP
https://www.youtube.com/watch?v=Sg41OMVMMUM&t=1671s

I thought I would replace the factory BL24C64A with one of those two, as in the video from YouTube

https://www.aliexpress.com/item/1005009774884879.html?spm=a2g0o.productlist.main.5.63ac6h6L6h6LcB&algo_pvid=732cd09e-ca0a-4559-ab63-cd976eb42df0&algo_exp_id=732cd09e-ca0a-4559-ab63-cd976eb42df0-4&pdp_ext_f=%7B%22order%22%3A%22-1%22%2C%22eval%22%3A%221%22%2C%22fromPage%22%3A%22search%22%7D&pdp_npi=6%40dis%21EUR%2159.82%2129.91%21%21%21484.00%21242.00%21%40211b81a317665919624886746e6fc2%2112000050123713215%21sea%21SRB%21167334188%21X%211%210%21n_tag%3A-29919%3Bd%3A2db6eb13%3Bm03_new_user%3A-29895&curPageLogUid=G2BWtCyOzrKz&utparam-url=scene%3Asearch%7Cquery_from%3A%7Cx_object_id%3A1005009774884879%7C_p_origin_prod%3A

and this one arrived a few days ago, in black color,

[muzkr]

I don't think it's V3, or even V2. But I'm not sure. I really wouldn't recommend buying V1 or V2, to this day. Good luck.

[idrugiput-netizen]

yes v3 i flashed it with f4hwn 4.3 for k5 v3.. bootloader is v7.0.11

[muzkr]

One minute you say v2, the next you say v3. To put it politely, your statements are imprecise and confusing; to be blunt, they're utter nonsense. No offense intended. Honestly, you're making me laugh in frustration.

[muzkr]

V3 uses a 2MB SPI NOR flash, not an EEPROM like V1 and V2. Replacing V3's with an EEPROM? That's creative!

[idrugiput-netizen]

I have two radios, first with v2 py032f030, 64kb,,, and second v3 py072, with 512kb.. In both now i use your fork f4hwn.. In v2 v. 4.3.. In v3 v. 4.3.2.. My question for upgrade large eeprom is for my first radio with py032f030.. V2.. Both device is quansheng uvk5 (8)