MicroHacker Forum

Of course it is. Oh well that makes this a bit easier

OK Here you hopfully ill be able to rcover my DAED Pam thanks conxxxx
have replaced pic to correct error Know working out the mode the MCU is in

Have been looking over the forum for the data to reprogram my bricked Pam I have the cal files but I need the onboard prim bootloader
Someone did say they were on hear. Can anyone help or have they been moved ?

The files can be found in another PAM thread: viewtopic.php?f=29&t=70#p600

Post your dump from bricked PAM here, to try to understand what happened.

Yeah, i knew that this header has the leads for the Debug interface, good job Stevebe!
I'm excited if you manage to restore it this way. Keep us update please. Unfortunately i have less time at the moment, as i loved to assist... damned.

DGAlexandru wrote: ↑20 Jan 2020, 18:04 Motorola BDM is with BKGD, GND, RESET, VDD

So it's really one single wire for communication?!

Yes

BTW Stevebe, if you want to keep your original settings of PAM (things like Serial Number, date of manufacture) you should not rewrite the EEPROM data; write only the Flash data.

Thanks for all the comments and help i will keep all posted, as far as keeping the info of the bricked module that will sort of depend on whats happend
with the daTA it certain isnt returning any thing at all so i would gues the primary boot has been lost/damage when i load the wrong vbf through no falk of my own..
and i will post what ever dump i can get from the unit

FOUND the MOD A B C
A and B are both tied to gnd via 10k
and mod C shares a pin with the BKGD and is tied to VDD with a 10k


sorry graphics are not great but only have a toy grafix editor lol

I read firmware PAM module Via X-Prog 5.5.1.
Pin on PAM module to X-Prog :

I only have a clone BDM but software is naff I’ll have to find a better software