Mmdvm kicad Duplex hat 14mhz firmware issues

Help with Raspberry Pi Foundation Boards (Raspberry Pi, Pi Zero, Pi Zero W, Pi A, Pi B, Pi B+, Pi2 B, Pi3 B, Pi 3 B+)
2E0WKS
Posts: 14
Joined: Sun Jul 21, 2019 10:00 pm

Mmdvm kicad Duplex hat 14mhz firmware issues

Post by 2E0WKS »

Having built 18 hotspots I have a number running kicad Duplex board and have had to update firmware as the pistar project evolves.

Hat Firmware 1.5.2 cuts out at least on fusion after 29 secs approximately, 1.4.17 works well.

The flashing issue is pi star identifying Pi4 as a pi3 which bulks up writing firmware.

Symptoms solid green light and firmware downgrade does not work.
Trying to reflash on Pi4 fails.

I have killed and brought back to life 2 hats by flashing on a pi 4 and then the same process on a pi zero to flash to 1.5.2 and downgrade to 1.4.17

I would appreciate some guidance on how to report the issue as it appears to be a firmware, stm32 controller and pistar issue.

I would very much like to be able to flash via Pi4 as I have several devices I need 1.4.7 firmware and they are not local to me.
Is there a way to alter gpio flash tool to see Pi4 as Pi4 or do pistar team need to look into this?

I'd prefer not to have hotspots posted back as I do this as a non profit hobby with fellow amateurs and team viewer easier.

Thanks
KE7FNS
Pi-Star Team
Posts: 1944
Joined: Wed Apr 17, 2019 11:11 pm

Re: Mmdvm kicad Duplex hat 14mhz firmware issues

Post by KE7FNS »

2E0WKS wrote: Fri Dec 04, 2020 1:53 pm Hat Firmware 1.5.2 cuts out at least on fusion after 29 secs approximately, 1.4.7 works well.
MMDVM_HS 1.4.7 was released on Aug 21, 2018, that is way too to far to go back. I would recommend you work backwards from 1.5.2 and try every release until you find a version that works correctly. Then once you identify the version that works correctly, compare the source code of the two and find the differences.
2E0WKS wrote: Fri Dec 04, 2020 1:53 pm The flashing issue is pi star identifying Pi4 as a pi3 which bulks up writing firmware.
The flashing scripts don't really care about which RPi is identified. They just display information posted from the logs, and it isn't critical to the operation of the flashing process, its only to make it pretty for humans to read while its doing things.

You seem to be bringing up multiple issues but combining them all into one. Can you provide the error you are encountering when running the Pi-star flashing scripts and what doesn't work properly?
2E0WKS wrote: Fri Dec 04, 2020 1:53 pm I have killed and brought back to life 2 hats by flashing on a pi 4 and then the same process on a pi zero to flash to 1.5.2 and downgrade to 1.4.7
You can't really kill a STM32 by writing a bad flash, you can always recover it and boot it to its default bootloader because the bootloader is written in ROM on the chip an cannot be changed.
2E0WKS wrote: Fri Dec 04, 2020 1:53 pm I would appreciate some guidance on how to report the issue as it appears to be a firmware, stm32 controller and pistar issue.
The YSF mode cutting out ISN'T 'Pi-star issue'. Post an issue report on the MMDVM_HS github, I see you already posted another issue there.
2E0WKS wrote: Fri Dec 04, 2020 1:53 pm I would very much like to be able to flash via Pi4 as I have several devices I need 1.4.7 firmware and they are not local to me.
Is there a way to alter gpio flash tool to see Pi4 as Pi4 or do pistar team need to look into this?

I'd prefer not to have hotspots posted back as I do this as a non profit hobby with fellow amateurs and team viewer easier.
If you are wanting a specific version of the firmware, you should download the source code for that version and compile it and then just copy that firmware file to a machine remotely, and then update the hat manually. Then you could just repeat the copying and flashing of the firmware over and over on as many devices as you want.

Also, if you are installing RPi 4's on 18 hotspots, in my opinion thats just a waste of 18 RPi 4's, you should use an older and cheaper RPi.
If someones previous actions are any indication of their future actions, then I predict the deletion and removal of access will happen at any moment. 7-11-2020.

"07/13/20 This Website Has Been Taken Down" ... again :lol:
KE7FNS
Pi-Star Team
Posts: 1944
Joined: Wed Apr 17, 2019 11:11 pm

Re: Mmdvm kicad Duplex hat 14mhz firmware issues

Post by KE7FNS »

2E0WKS wrote: Fri Dec 04, 2020 1:53 pm The flashing issue is pi star identifying Pi4 as a pi3 which bulks up writing firmware.

Symptoms solid green light and firmware downgrade does not work.
Trying to reflash on Pi4 fails.
I have just finished testing the pi-star flashing scripts using a RPi 4 with various versions of MMDVM_HS.

I had no issues at all with the flashing process of upgrading or downgrading.

Perhaps your specific hat requires installing jumpers to begin the flash (failure to init). I cannot determine what exactly the failure is because you haven't provided the error details of your specific problem.
If someones previous actions are any indication of their future actions, then I predict the deletion and removal of access will happen at any moment. 7-11-2020.

"07/13/20 This Website Has Been Taken Down" ... again :lol:
2E0WKS
Posts: 14
Joined: Sun Jul 21, 2019 10:00 pm

Re: Mmdvm kicad Duplex hat 14mhz firmware issues

Post by 2E0WKS »

Simply the argument isn't worth the effort, I can't see the benefit of posting further as your obviously looking for some kind of engagement or hostile response.
1)1.5.2 drops after 29 seconds on multiple devices 1.4.17 fine.
2) pi 4 the script identifies pi 4 as pi 3 and fails flashing hat, same sd card same hat pi zero it completes.

Pi zero far too slow for later versions of pi-star even overclocked.
Why would you want a pi 3 when a pi 4 2gb same price here.

The pi star project is great and I shall no longer bother posting here as I have more productive things to do than justify myself or have an argument.

I bid you good day
KE7FNS
Pi-Star Team
Posts: 1944
Joined: Wed Apr 17, 2019 11:11 pm

Re: Mmdvm kicad Duplex hat 14mhz firmware issues

Post by KE7FNS »

2E0WKS wrote: Fri Dec 04, 2020 7:37 pm Simply the argument isn't worth the effort, I can't see the benefit of posting further as your obviously looking for some kind of engagement or hostile response.
No, I'm looking for specific details on the errors you encountered that you conveniently left out of your "report".
2E0WKS wrote: Fri Dec 04, 2020 7:37 pm 1)1.5.2 drops after 29 seconds on multiple devices 1.4.17 fine.
Again, not a "pi-star issue".
2E0WKS wrote: Fri Dec 04, 2020 7:37 pm 2) pi 4 the script identifies pi 4 as pi 3 and fails flashing hat, same sd card same hat pi zero it completes.
Again, I tested the Pi-star flashing scripts. I had no such failures on a RPi 4B.
2E0WKS wrote: Fri Dec 04, 2020 7:37 pm Pi zero far too slow for later versions of pi-star even overclocked.
The majority of hotspot users are using RPi Zero W's so your statement is unfounded.
2E0WKS wrote: Fri Dec 04, 2020 7:37 pm The pi star project is great and I shall no longer bother posting here as I have more productive things to do than justify myself or have an argument.

I bid you good day
Nobody is arguing with you.

You could simply be typing something incorrectly or perhaps your hardware requires jumpers to be installed. I don't know because I can't determine it because you failed to include the details and when asked for the details you interpret that as an argument.
If someones previous actions are any indication of their future actions, then I predict the deletion and removal of access will happen at any moment. 7-11-2020.

"07/13/20 This Website Has Been Taken Down" ... again :lol:
KE7FNS
Pi-Star Team
Posts: 1944
Joined: Wed Apr 17, 2019 11:11 pm

Re: Mmdvm kicad Duplex hat 14mhz firmware issues

Post by KE7FNS »

Please post the output of the "sudo pistar-mmdvmhshatflash hs_dual_hat" command so I can see the exact error you are encountering.
If someones previous actions are any indication of their future actions, then I predict the deletion and removal of access will happen at any moment. 7-11-2020.

"07/13/20 This Website Has Been Taken Down" ... again :lol:
User avatar
G8SEZ
Posts: 437
Joined: Fri Apr 13, 2018 8:26 pm

Re: Mmdvm kicad Duplex hat 14mhz firmware issues

Post by G8SEZ »

2E0WKS wrote: Fri Dec 04, 2020 7:37 pm Simply the argument isn't worth the effort, I can't see the benefit of posting further as your obviously looking for some kind of engagement or hostile response.
1)1.5.2 drops after 29 seconds on multiple devices 1.4.17 fine.
2) pi 4 the script identifies pi 4 as pi 3 and fails flashing hat, same sd card same hat pi zero it completes.

Pi zero far too slow for later versions of pi-star even overclocked.
Why would you want a pi 3 when a pi 4 2gb same price here.

The pi star project is great and I shall no longer bother posting here as I have more productive things to do than justify myself or have an argument.

I bid you good day
Hmm, from that description it looks like you need to update pistar and upgrade it too the recognition code has had a few tweaks for Pi 4 boards, use sudo pistar-update and then sudo pistar-upgrade, it might take a couple of cycles of these commands. Not a bad idea to upgrade the OS, if you go in via SSH then this will happen during the pistar-update process.

If you're having flashing problems it could be because the JP1 jumper on the dual HAT isn't shorted.
--

Brian G8SEZ
KE7FNS
Pi-Star Team
Posts: 1944
Joined: Wed Apr 17, 2019 11:11 pm

Re: Mmdvm kicad Duplex hat 14mhz firmware issues

Post by KE7FNS »

G8SEZ wrote: Sat Dec 05, 2020 12:30 am Hmm, from that description it looks like you need to update pistar and upgrade it too the recognition code has had a few tweaks for Pi 4 boards, use sudo pistar-update and then sudo pistar-upgrade, it might take a couple of cycles of these commands. Not a bad idea to upgrade the OS, if you go in via SSH then this will happen during the pistar-update process.
What RPi 4 recognition code are you referring too?

The Pi-star flash script hasn't been modified in 16 months. Theres nothing in it that has had to be tweaked to operate on a RPi 4. The only difference I know of is RPi 4's boot with the GPIO signals in a different initialization pattern compared to other RPi models, and it needed a manual reset to allow communication to the MMDVM. That re-initialization script should of already been executed right after boot, and if it was missing his RPi wouldn't connect to the MMDVM at all, so we can deduce he has it, and it is functioning correctly.

https://github.com/AndyTaylorTweet/Pi-S ... hshatflash
G8SEZ wrote: Sat Dec 05, 2020 12:30 am If you're having flashing problems it could be because the JP1 jumper on the dual HAT isn't shorted.
Thats more than likely the problem as STM32Flash would report the error as "failure to init". I'd say it is by far the most common error and even manually jumping one of those DB9MAT DF2ET DO7EN boards I had to retry a number of times to get it to succeed, once I soldered JP1 it became completely hands free and never fails even at increased serial speeds of 912600 baud.
If someones previous actions are any indication of their future actions, then I predict the deletion and removal of access will happen at any moment. 7-11-2020.

"07/13/20 This Website Has Been Taken Down" ... again :lol:
KE7FNS
Pi-Star Team
Posts: 1944
Joined: Wed Apr 17, 2019 11:11 pm

Re: Mmdvm kicad Duplex hat 14mhz firmware issues

Post by KE7FNS »

I think I've uncovered half of what the OP is reporting, I still don't know what error he is experiencing though.

The overview of the pistar-mmdvmhshatflash script is that it downloads files from the MMDVM_HS github repo, one of those files is determined by which parameter you enter when executed and that script gets downloaded and renamed to flash.sh

Inside of that script there is some very crude OS detection going on:

https://github.com/juribeparada/MMDVM_H ... hat.sh#L42

The results of "uname -m" on a RPi 4 running Pi-star are the same as on an RPi 3 running Pi-star, WHY??? because they BOTH use the same 32-bit kernel in Pi-star even though they are both ARMv8 64-bit processors.
The message that is output to the console is effectively meaningless. It makes no difference that it says it is a RPi 3 when it is run on an RPi 4. Actually there is another issue that I see and it will say its a RPi 3 when it is run on a RPi 2B, because the RPi 2B runs the same armv7l kernel too.

If you compare the two sections for detecting armv7l against armv6l the sections of code for each are IDENTICAL, so again there is no difference in operation on a system that detects armv7l against one detected as armv6l, both of them are set to the same values when run on their respective kernel

Basically the way the script determines the platform from "uname -m" is poorly done at best. If it were properly written it should parse something like /proc/cpuinfo to retrieve the correct RPi hardware model, but realistically it isn't really needed and it is just extra meaningless fluff written to the screen. The other sections allow for the script to function correctly on x86_64 and 32-bit Linux OS's (non ARM)

Theres really no reason to have two separate cases when they both run identical code in side them. Both of those sections could be combined into one with a simple OR statement, and one line to retrieve the RPi hardware model info.

The simple fact it boils down to is it isn't a Pi-star related script, its a script from MMDVM_HS that is DOWNLOADED, so it isn't really Pi-star's responsibility. The OP needs to create 2 new issues on the MMDVM_HS github, one for the YSF cutting out after 29 seconds, and the other for the incorrect detection of the RPi model during flashing.
If someones previous actions are any indication of their future actions, then I predict the deletion and removal of access will happen at any moment. 7-11-2020.

"07/13/20 This Website Has Been Taken Down" ... again :lol:
User avatar
VK7HSE
Posts: 223
Joined: Sun Apr 15, 2018 6:35 pm
Contact:

Re: Mmdvm kicad Duplex hat 14mhz firmware issues

Post by VK7HSE »

Generally one wouldn't need to roll back on firmware releases, but you can manually download prior releases


https://github.com/juribeparada/MMDVM_HS/releases


Or if you are familiar with git you can roll back the local clone of the source code to any commit number (well number/letters) and achieve the same thing. But by doing this you will most likely need to compile it prior to uploading. I'm not going to go into detail on this because I don't believe it will solve the problem (as indicated by some replies)



Sent from my Pixel 4 XL using Tapatalk

Post Reply