wojciechk8 / mmdvm_pog Goto Github PK

Hello my friend!
I will try to build the MMDVM board with your gerber files and compile the firmware from source. There is a lot to learn in the process, and it's a nice challenge for (admittedly advanced) amateurs.
But ofcourse I ran into some difficulties (and anticipate others). So could you please help with a few things:
HW

• are your gerber files good for producing a pcb without any changes? I am thinking of a minimal quantity with JLCPCB and their smt assembly process.

FW

• what is the reason for choosing stm32f105 instead of 32f103c8 (like practically all others I can see online)
• what is your development environment: windows or linux?
• in file->preferences, what is the address in "additional board manager urls" ?
  (After installing the board support according to some instructions on the net, I was able to build arduino due. But after installing the lib and switching to stm32f103, 105, 407, 411, they all fail with "unknown processor type". I followed g4klx's build instructions (many times:) ) but without success. Tried older versions of arduino ide, modified platform.txt etc..but the build still fails.)
  In the latest attempt, the f105 cpu is not even available in the "board part number". I have only F103 variants, so I must be doing something wrong.
  So, what goes here?
  

And what goes here?

• finally, do you compile from arduino ide -> sketch -> verify/compile or from the command line (and how exactly)?
• if you also tell me what is the modification in your platform.txt, I promise a big cold beer will be waiting for you in my fridge. :) :)

I am using the latest arduino ide 1.8.13 via installer.

Thanks!

For a hobbyist this project is unusable. There are so many things and steps you need to make, apart from (installing VM, linux OS, readme steps), just to be able to export a copy of gerber files and BOM. I'm in the second day and still struggling with the current state of the files to make something that works or at least exports.
"gsch2pcb mmdvm_pog.prj" produces an error because there is no such thing as "partslist4"

Although I appreciate the author's efforts and the fact that it's been public since 2017, but it's funny to see this open source adapted (by some hams, china factories), modified and transformed into a commercial product and still, someone trying to get a PCB out of this hits so many problems.
If someone has knowledge with gEDA, please step in and make a few mods to this project :

• add a voltage divider (100K pot) for J21 pin 8 to STM32F105RBT pin 27
• add 2 connections from J3 pin 38 to STM32F105RBT pin 7 (NRST) and J3 pin 40 to STM32F105RBT pin 60 (BOOT0) to avoid this hack :
  https://github.com/yo6nam/MMDVM_STMF1XX_FW/blob/master/pog_stm_update_mod.jpg
• (optional) P31 and P41 footprint changed. Parts will be replaced with :
  https://www.tme.eu/en/details/t67w-10k/1-4-inch-multiturn-tht-trimmers/sr-passives/

I see you moved the communications port from PA2 and PA3 to PA9 and 10. I edited the IOSTM_CMSIS.cpp and changed 2 to 9 and 3 to 10. I can flash the LED, but I can not communicate with the processor. Did I miss something?

73, Steve N4IRS

In duplex mode after conttinious transmitting in local group( i mean not via internet)
recieving stops... and do not responding anymore and holds the carrier of the transmitter until powered off!!
i occurs when transmitt over 2mins 30 sec

How to solve this issue?

Hello @wojciechk8, today I am looking your PCB board I like to build one but I have one suggestion. If you have time to add NXDN Led on STM32 MCU. This will be wonderful future.

Best regards, Danilo - S58DB

/tmp/ccANnA6K.s: Assembler messages:
/tmp/ccANnA6K.s:461: Warning: ignoring changed section attributes for .data
/tmp/cc8vlPEj.s: Assembler messages:
/tmp/cc8vlPEj.s:17: Warning: ignoring changed section attributes for .data
/tmp/ccMkS9xt.ltrans0.ltrans.o: In function process': /home/pi/MMDVM/SerialPort.cpp:670: undefined reference to CSerialPort::availabl eForWriteInt(unsigned char)'
collect2: error: ld returned 1 exit status
Makefile.CMSIS:145: recipe for target 'bin/mmdvm.elf' failed
make: *** [bin/mmdvm.elf] Error 1

Hey great board however I cannot find out how the IGN pin is meant to be wired.

I see there is two ign pins that appear to be connected via trace however I don't know if this pin needs to be held low with ground, held high with 3.3v or held high with 5v.

If someone could clarify more detail on this it would be great.

I have figured out it's probably for car ignition? Because my PI wont boot with this hat ontop. I have to remove it before then add it once PI is booted which is not ideal.

Cheers,
2E0PGS