DMR working only in RX and not in TX

[KG6RUT]

Yeah, something is weird with that radio, check the DMR ID again and make sure it matches what is in your hotspot also try the hotspot on public.

Yeah, if the password was incorrect you wouldn't be able to connect to the BM server at all and you wouldn't be able to listen to TG 91.

What firmware is the radio (ht) on? Also what firmware is the hat on?

I have re checked and the DMR ID is the same, i can also see the hotspot in my brandmeister page.
The HAT firmware is "HS_Hat:v1.4.6" it is STM32 HAT, i am running a raspberry pi 3b with pistar version 4.1.3.
The firmware of my HT is MD380Tools Ver. 2018-04-01 CP Ver: V01.40

Thank you very much for your help

The Hat for sure is dated, I am running 1.5.2....

[IU3NNX]

The Hat for sure is dated, I am running 1.5.2....

I agree completely.

v1.4.6 is from Jul 21, 2018

@IU3NNX
I'd at least update it to v1.4.17

I have tried to update it in every way but the system tells me that this is the newer version, i also downloaded a .bin from git hub and i tried to flash it but nothing to do, could you help me?

[KG6RUT]

Also, keep in mind that depending what hat you have you may need to close a jumper on the board......on mine, I had to solder closed JP1

[IU3NNX]

I have tried to update it in every way but the system tells me that this is the newer version, i also downloaded a .bin from git hub and i tried to flash it but nothing to do, could you help me?

Code: Select all

sudo pistar-mmdvmhshatflash hs_hat

I don't think you've said which board you have so, I'll assume you've got a simplex hat, that has got a 14.7456MHz TCXO, if not leave off the hs_hat and it will display all of the different options.

I have tried this command before and it has no effect i get a message that says that the update went fine but looking the output i can see this:

Screenshot (61)_LI.jpg (84.25 KiB) Viewed 3836 times

[KG6RUT]

Pretty sure thats because the memory is write protected due to the fact that the jumper has NOT been soldered closed......thats my guess from some simple searching.....you need to remove the hat and solder closed jumper 1......GL!

[IU3NNX]

Pretty sure thats because the memory is write protected due to the fact that the jumper has NOT been soldered closed......thats my guess from some simple searching.....you need to remove the hat and solder closed jumper 1......GL!

Thank you a lot for your kind help, now that i know what the problem could be i will try to solder it and try to update again

73 IU3NNX

[KG6RUT]

i have a duplex hat, the JP1 that was soldered is in the right bottom corner.....yours will be different I suspect....

[IU3NNX]

Pretty sure thats because the memory is write protected due to the fact that the jumper has NOT been soldered closed......thats my guess from some simple searching.....you need to remove the hat and solder closed jumper 1......GL!

Actually the jumper doesn't have any relation to the STM32 write protection.

The jumper just allows automatic updating on that specific board design (if you follow the traces you'll see where it goes), it is still possible to manually jump the BOOT1 1 and - pads while kicking off the firmware update command. It is pretty finicky though, it takes some fiddling with to get a flash to initalize.

However his problem could be that the chip is locked, and in that case he is going to need a ST-Link to unlock it.

i have seen that if the chip is locked i can unlock it with stm32 software that i have downloaded, unfurtunatly i dont have a STlink but i have a Serial to USB converter that i use to send code to arduino nano, i will try if i am able to erase the protection with it, i am also looking to delete md380toolz, is it possible that all will work with the orginal firmware?