Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem upgrading the firmware #324

Closed
TomToy621 opened this issue Mar 9, 2021 · 17 comments
Closed

Problem upgrading the firmware #324

TomToy621 opened this issue Mar 9, 2021 · 17 comments

Comments

@TomToy621
Copy link

TomToy621 commented Mar 9, 2021

What is happening?
Describe here why you are unable to upgrade the firmware. Before describing your problems, do the following:

Were you able to update the firmware before?
Things might be confusing the first time, please check the video available on the link above.

Can you try the upgrade with a different PC/Portapack/HackRF?
If is possible, swap hardware and try again. Also, try different USB cables, even if the one you are using works fine for other purposes.

Additional
Add photos and videos of your procedure.


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@TomToy621
Copy link
Author

TomToy621 commented Mar 9, 2021

Hello,

I think I watched the video carefully for the firmware update v1.3.1.
I've got an issue when i try to start my Portapack H2 HackRF, sometime it doesn't start at all, sometimes after few tries it starts after a while and sometime it starts very quickly.It also doesn't start at all with the micro SD inside before starting, it works when i add the sd card after the start...
Features i've tried for the moment seem to work awhen i succeed in starting my device and adding the SD card

Could anyone tell me from where it can come from?

Thanks a lot for your help, have a good one

Tom

https://www.youtube.com/watch?v=FDNUBM1ruWk

20210308_205005
20210308_223201
Capture5
Capture4
Capture3
Capture
Capture2
20210308_225141

@eried
Copy link
Member

eried commented Mar 10, 2021

It sounds like a hardware problem, how old is the unit?

@TomToy621
Copy link
Author

Hey @eried, thx for your reply!!I've just received the unit few dayz ago...

@TomToy621
Copy link
Author

As I won't get any refund or return possibility from BG, do you think it's a Hack RF 1 or Portapack H2 issue?Is there any possibility to check with for example a multimeter or any other device where the problem comes from?
Thanks

Tom

@euquiq
Copy link
Contributor

euquiq commented Mar 10, 2021

You can disassemble it (with care) and use the hack rf alone, through USB, with your computer.

Also remember to never turn it on and transmit without an antenna attached to it. It is a fast way to burn the TX amp if used.

@TomToy621
Copy link
Author

Hey @euquid, thx, i did the firmware update with the hack rf dissasembled from the portapack as preconised...Will use the hack rf alone and perhaps later try to understand what's the issue

@port513
Copy link

port513 commented Mar 11, 2021

Since this is a Portapack H2+ you should try this firmware before disecting your unit https://www.mmdvm.club/index.php/h2.html
H2+ will not function as expected with this repos 1.3.1 and until they decide to synch them we have to use different 1.3.1.

But as I said, I got weird startup issues, could not boot if SD-card was in the slot etc until I changed to the other firmware.

@TomToy621
Copy link
Author

thx, would be pleased to try this solution, but the link you gave me seems not to be working anymore, can you tell me the name of this firmware and if I can find it somewhere else?

@TomToy621
Copy link
Author

can I also try older versions of the mayhem?

@port513
Copy link

port513 commented Mar 12, 2021

can I also try older versions of the mayhem?

If you have H2+ it will not work with older. You need this file https://www.mmdvm.club/usr/uploads/2021/03/232153741.zip

Just tried the link and it's still working as it should

I downgraded my H2+ and got a few hundred new bugs ;) So don't do that if you want to be sane this weekend ;)

@zhang00963
Copy link
Contributor

zhang00963 commented Mar 24, 2021

This seems to be caused by the firmware's failure to correctly recognize the H2 + audio chip,
You can modify the test as follows.

For / firmware / application/ portapack.cpp The file is compiled after modification.
It has been tested on ak4951en of H1 and wm8731 / wm8731s of H2. It can automatically identify the type of audio chip and drive it,

image

@eried
Copy link
Member

eried commented Mar 25, 2021

Hey @zhang00963 have you tried in other portapacks? with the old chip? Would you mind making a PR in github so everyone could test it?

@zhang00963
Copy link
Contributor

Hi @eried I have portapack H1, which uses the audio chip of ak4951en.and portapack H2 + which uses the audio chip of wm8731s, and I try to replace wm8731s with wm8731 audio chip. After testing, portapack can work normally.
I think the problem is that in the init function, the I2C / I2S is not ready when the [portapack_cpld_config()] function is executed, resulting in the audio chip detection function not working properly,
I'll do some tests,Submit a PR.

@eried
Copy link
Member

eried commented Apr 7, 2021

I'll do some tests,Submit a PR.

How are your tests going @zhang00963 ? It would be nice to release a new version with these soon so people do not need to worry about different versions

@ckuethe
Copy link
Contributor

ckuethe commented Apr 18, 2021

As reported in #301, portapack_nightly_202104180016_next.bin allows my portapack to boot with an sdcard inserted.

@ckuethe
Copy link
Contributor

ckuethe commented Apr 22, 2021

@TomToy621 try it with Mayhem 1.4.0 - it's working on my portapack.

@ArjanOnwezen
Copy link
Contributor

Looks like a duplicate of #346

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants