It does show it in assembly.
It does show it in assembly.
Dave Purola,
N8NTA
EN82fn
So who's volunteering for a Assembler-PBP decompiler?
But then we get into the issue of PBP v2.6c versus v3.
Robert
There is a decompiler for Windows. Its called IDA. It costs a skrillion Deutsche Marks. It will disassemble a PIC executable (but not of course decompile - to do that it needs to know about the compiler).
I believe the Oshonsoft line of simulators will disassemble - they have a trial version.
If you Google for "PIC disassembler" you will find myriad on and off line PIC disassemblers but not decompilers, and if you did find one it would be to C.
All things considered unless you only need to make tiny changes to the device in question, better of understand its function (as a black box) and write that up in Basic.
George
All this talk of Assembler makes me wish I had kept it fresh. Unfortunately I worked in COBOL and graduation dates back to 1984. I dabbled in various BASICs over the years but that was it.
BR is Branch Register, and that sums what I've retained. Was in top 3 in Assembler class too.
I am curious if a decompiler is within our reach. Each PBP command breaks down into one or more Assembler statements. Could we catalog these Assembler "groups", scan for matches and spit out corresponding PBP?
Or am I missing something obviously more complicated?
Robert
![]()
That is EXACTLY what I need! I have an auto-acquire satellite dish system that is run by a PIC32, and I need it to shift itself just a few degrees left, and possibly a couple up or down, of where it wants to be now... that's it. Depending on how it's coded now, and what I can learn, I can either re-write it to lock onto the proper satellite, or lock onto the current satellite, and move to the desired satellite from that point. Either way, the changes I need to make are relatively minute....
Ok, this is a PIC32MX440F256H.... Does this make it more complicated somehow?
Bookmarks