DIY-Multiprotocol-TX-Module
DIY-Multiprotocol-TX-Module copied to clipboard
pascallanger
Modules with STM32F103C8 MCUs are not supported in release builds (e.g. URUAV TMX5, VANTAC, etc.)
This module is using wrong components with the majors being:
- STM32 with 64KB of flash (STM32F103C8) instead of 128KB (STM32F103CB)
- NAND (C00) instead of XOR (C86) affecting telemetry
If you have purchased this module, you should go back to your reseller and claim your money back since the hardware is not matching the description (64KB vs 128KB).
I can confirm that this also applies to the URUAV TMX5 Lite variant. Same MCU, same flash :(
Can you elaborate how the NAND flash is affecting telemetry? I had some really odd problems with the TMX5 lite and a FrSky D4R-II receiver. Range test was fine but when flying (~10m ) I lost control for about 3 seconds, no "telemetry lost" or "RSSI critical" warning from my radio. Happened multiple times. I am using the current v1.3.1.49 build, the module came with a really old version (1.2.xxx).
NAND flash
Nothing to do with flash, just a logic gate that's supposed to invert the telemetry signal but isn't the correct type.
Never mind, must have been all that LiPo smoke exposure after digging the burning battery out of the ground ;-D
The STM32 on the TMX5 is most likely able to go above the 64KB limit that the manufacturer indicates in the datasheet. While it can store up to 128KB which you are writing with the current Multi tooling, we've seen these modules having erratic behaviors which shows that the flash is not reliable above the 64KB... Just think about it, the components which have a full good flash are sold as128KB the others at 64KB, this is how things work. Now if you want to fly with it, it's your take but personally I won't take the risk...
It's not worth the risk, too bad I stumbled across this issue after wrecking my copter. However, the TMX5 module has so far been working fine for indoor flying, no problems with flysky and frsky D8/D16. Really awesome experience. It may have been a faulty PPM wire that caused my initial problems. That would explain the failsafe event without "low RSSI/telemetry lost" warning from my radio. Since I got my money back I am going to try to replace the STM32 with the proper STM32F103CBT6.
Vantac Lite modules are also affected by the wrong STM32 chip, added to the subject.
Could you please clarify that to me? I purchased this module https://www.banggood.com/URUAV-TMX5-4-IN-1-A7105-CC2500-CYRF6936-NRF24L01+-Multi-Protocol-Transmitter-Module-Compatible-FrSky-X9D-X10-Transmitter-p-1525898.html? And it claims to be MCU: STM32F103CBT6(128K ROM, 20K RAM) Arrived today, and I wanted to upgrade it just to see the NEW NOTE that it's not supported (anymore?). I opened it up, but to be honest I can't say if this is a 'B' or an '8'. How do I find out? Thanks
Made this pic. It's hard to make it as large as possible. I really can't say ....
That's a C8. The B has a single straight line down the left hand edge.
Your best option is to return it as it is not what they claim it to be and purchase the iRangeX IRX4 Lite
For comparison, here's a photo of the STM32F103CB in my IRX4 module. Once you know what they look like, the 8 and the B become easier to distinguish.
Thanks for clarification and F*CK. :( Btw: Would it be ok to swap the chip for one of these? https://www.aliexpress.com/item/4000113089300.html?spm=a2g0o.productlist.0.0.48c62f0d0BZCPo&algo_pvid=4c39b621-2f79-4f24-a4fc-416eea8f138a&algo_expid=4c39b621-2f79-4f24-a4fc-416eea8f138a-2&btsid=0b0a050116016613800332457ea3fd&ws_ab_test=searchweb0_0,searchweb201602_,searchweb201603_
I never had a claim with BG, but shipping already was a disaster. I guess it would be a hard fight.
Or maybe sacrifice one of these STM32 developer boards? I got two here and they show the very same chip as in the picture you posted.
If you are able to replace the STM32 by the CB version then yes it's all good. I won't be able to do it personally as it's so small but if you can then sure it will work.
Yes it's small, and I'll probably bust it, but I guess it's my best chance. It will save me from going mad with BG support. It's probably easier to open a Paypal case. And: It's holiday season in China atm as well ...
If I deselect some protocols that are not needed. And get the size below 64k will it work. Fabio Ehrengruber [email protected]
On Oct 2, 2020, at 10:44 AM, Ben Lye [email protected] wrote:
For comparison, here's a photo of the STM32F103CB in my IRX4 module. Once you know what they look like, the 8 and the B become easier to distinguish.
https://user-images.githubusercontent.com/23322579/94953293-38143a80-04df-11eb-94a0-5e645d40ff4d.jpg — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/issues/393#issuecomment-702869237, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIFQ5CPFCM3EDBF5KSQQXJ3SIYGRVANCNFSM4O6H7MQA.
Yes it's small, and I'll probably bust it, but I guess it's my best chance. It will save me from going mad with BG support. It's probably easier to open a Paypal case. And: It's holiday season in China atm as well ...
You might want to verify that the STM32 on the blue pill is genuine before you start. It's not uncommon for them to have cheap clones that have been screened to look like the genuine part.
If you hook it up with a USB-to-serial adapter you can try flashing a debug build of the multiprotocol firmware, which would tell you if the firmware sees the correct flash size via the serial console output. Or you could use Stm32flash or the STM32 Flash Demo Loader to verify that it's genuine by reading / writing it.
In any case, you will need to use a USB-to-serial adapter to flash it once and install the bootloader.
I guess I should have invested a bit more time before just swapping the STM32. I did it, and it looks decent. But I guess it needs a bootloader or something. I installed "multi flash" and installed the drivers, but there module is not recognized by windows.
The USB port won't work until you flash the bootloader. You need to do that with a USB-to-serial adapter. Once you hook the adapter up you also need to bridge the BOOT0 pins on the module.
Details are on the compiling page.
https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/blob/master/docs/Compiling_STM32.md
I wonna give you something to LAUGH OUT LOUD. Guess what: I replaced a C8 with another C8 instead of a CB. How f***** stupid can someone be ;) At least I still can run .59 and now order a CB to "repair" the module once again ;)
Looks good :)
How you did that. I also have the C8 processor. Please explain.
@talha909. What do you mean? The programming (description is a few posts back) or hardware chip swap? If you ask about hardware I'm happy to help but, as you have to ask, it may be beyond your abilities/possibilities. You need a hot air station, twizzers, flux and a steady hand. And neelde probes to check against shorts after you flow soldered the new chip. Nothing that can't be done, but it needs some experience. I definately would vote against it if you haven't done it before and also need to buy tools. Cheaper to get a replacement. If you got any other questions and I can help with something specific please let me know :)
Does anyone know where I can find the original firmware? (since I flashed it before RTFM)
What do you mean by "original firmware"? Just flash an older one and you're set. Or compile a new one with reduced protocols.
Flashed multi-stm-opentx-taer-inv-v1.3.0.53.bin and it works. Just needed the D8.
Did anyone compile a smaller one that works? I can flash it by ignoring the 128KB message but I can't bind to anything :/
