Keyboard Shortcuts
Likes
Search
PIC16f1938 and changing eeprom
Hi,
Hope someone has experience with the following; Ubuntu OS, pickit 2 and pk2cmd. That's the current environment I have available. I am able to program the PIC CPU but it seems I am doing something wrong with the upload of eeprom.? I had a working (default) atu-1000. (Kw) but wanted to change some parameters as well upgrade the firmware. It was my understanding the hardware is wired the same as atu-100.? How do you flash the eeprom to the pic normally and what settings are used??? Hope someone already figured out pk2cmd and changing settings for the atu-100.? Unfortunately I lost the eeprom settings of the original flashed content. Perhaps someone in the group has as working hex file?? Thanks very much in advance! Best regards Onno |
toggle quoted message
Show quoted text
|
I hope someone has experience updating the pic processor using command line instead of installing an ide to just push the bytes to the processor.?
I can access the pic processor, read the data and write data to the processor. It even works a little bit I expect I'm doing something wrong updating the eeprom. But I don't know what to look for or check. |
I have tried with various approaches so far but none is working. I even installed VMware and valid windows XP os and still it did not work because of the USB interface.?
I surrendered and ordered a pickit 4. It's multiple times expensive than the target hardware. Once I got it running (I hope it will) I will think about a possibility to change settings through knob sequence instead of the need for a programmer device. The current approach to change eeprom settings is not user friendly imho.? |
Today I have received the pickit 4 and it really works well on Linux. Just unfortunate it is needed to change a few parameters within the eeprom.?
I'm going to investigate over the next couple of Weeks the following; 1-tuner efficiency 2- how to implement key sequence to adjust eeprom settings without the need for an expensive programmer device.? Regards onno |
Hi, FYI a pickit2 works fine with the? 1938... The device just need to be updated once with the latest available firmware, and the pic is recognized w/o probs... Software to use is "Pickit 2 V 2.61", and the device update is made trough this sw. Is then possible to read and program the ATU with a new HEX or change the available options. KR ? ? ? |
Hi, That's good to hear! Which operating system did you use?? I could program the pic controller using a Linux tool but whatever I tried I could not use the microchip programmer software. I have tried emulators, virtual box and even windows 10 on a separate disk. None was working.? In the end I bought a pickit 4 which has drivers for Linux too. Works really well.? Best regards Onno Op zo 12 dec. 2021 02:34 schreef Gio_iz3lit <iz3lit@...>:
|
Hi, The thing has been used on 2 systems, windows 7 64bit and windows 10 64bit. The other interesting detail is the programmer (pickit2) can handle easily the 1938 pic whether if if powered or not powered. No hassle then to do the job and program the options. I'm quite satisfied being able to use my "old" stuff, as I wasn't so motivated to buy other hardware just for that job. Last but not least, the the pickit2 can be used to program as well AVR chips (i.e. arduino boards), so definitely this small "old" programmer is an interesting piece of hardware to have and use.(and quite cheap now to buy now)
? ? |
Hi Onno,
I am experimenting with the atu-100 now (100W version) and I made a backup of the hex file with pk2cmd and a PICKIT2 as follows: pk2cmd -PPIC16F1938 -A5 -T -R -J -GFN7DDC.hex I can send you my backup file if you like. I am currently looking into reading the EEPROM, no luck so far. It should be something like: pk2cmd -PPIC16F1938 -R -J -GE00-3F But I get all zero's: Read successfully.?????????? ? EEData Memory 0000 00? 00? 00? 00? 00? 00? 00? 00 ? 0008 00? 00? 00? 00? 00? 00? 00? 00 ? 0010 00? 00? 00? 00? 00? 00? 00? 00 ? 0018 00? 00? 00? 00? 00? 00? 00? 00 ? 0020 00? 00? 00? 00? 00? 00? 00? 00 ? 0028 00? 00? 00? 00? 00? 00? 00? 00 ? 0030 00? 00? 00? 00? 00? 00? 00? 00 ? 0038 00? 00? 00? 00? 00? 00? 00? 00 ? Operation Succeeded 73 Joop PG4I |
I tried microchip IPE on macOS, but it was really unstable. Switched to Linux (Parrot) and all works fine. Parrot is Debian-based so similar to Ubuntu. I¡¯m using a cloned 3. @Jo - The zero values are probably because the original burn was read protected - look in the config info. The only way around that is to erase and reprogram (make sure you uncheck the protection flag).? You might find that you need to play around with the voltage. Initially I had to go down to 2.75v, but seems to work okay on 5v now.? |
If it's a Chinese kit you'll probably find that they read protected the PIC. The vendor I got my ATU-1000 from told me the factory does that on all of them. There's a thread on here somewhere about someone else having that same issue.
toggle quoted message
Show quoted text
Vince - K8ZW. On 02/22/2022 07:10 AM, Jo PG4I wrote:
Hi Onno, --
Michigan VHF Corporation -- nobucks dot net K8ZW - |
Hey Vince: I saw your post on groups.io How will these "Chinese protected" PICs affect us with our 1 kW kits? Will we just be able to write over the existing software and not even worry about it?? My toroid cores are on their way from "DIZ" but I did receive my Pickit3 programming setup already. 73, -Dennis? W1LJ
On Tuesday, February 22, 2022, 12:47:13 PM MST, Vince Vielhaber <vev@...> wrote:
If it's a Chinese kit you'll probably find that they read protected the PIC.? The vendor I got my ATU-1000 from told me the factory does that on all of them.? There's a thread on here somewhere about someone else having that same issue. Vince - K8ZW. On 02/22/2022 07:10 AM, Jo PG4I wrote: > Hi Onno, > > I am experimenting with the atu-100 now (100W version) and I made a > backup of the hex file with pk2cmd and a PICKIT2 as follows: > > *pk2cmd -PPIC16F1938 -A5 -T -R -J -GFN7DDC.hex > * > I can send you my backup file if you like. > I am currently looking into reading the EEPROM, no luck so far. It > should be something like: > > *pk2cmd -PPIC16F1938 -R -J -GE00-3F* > > But I get all zero's: > *Read successfully.? ? ? ? ? ? * > > *EEData Memory* > *0000 00? 00? 00? 00? 00? 00? 00? 00? * > *0008 00? 00? 00? 00? 00? 00? 00? 00? * > *0010 00? 00? 00? 00? 00? 00? 00? 00? * > *0018 00? 00? 00? 00? 00? 00? 00? 00? * > *0020 00? 00? 00? 00? 00? 00? 00? 00? * > *0028 00? 00? 00? 00? 00? 00? 00? 00? * > *0030 00? 00? 00? 00? 00? 00? 00? 00? * > *0038 00? 00? 00? 00? 00? 00? 00? 00? * > > *Operation Succeeded* > > 73 Joop PG4I > -- ? ? ? ? Michigan VHF Corporation -- nobucks dot net ? ? ? ? ? ? ? K8ZW - |
You can reprogram them just fine. You just can't read what's currently in it. After the reprogram, you'll be able to read it without a problem.
toggle quoted message
Show quoted text
Now somehow I managed to wipe out what's in my PIC, so I'll be re-writing it sooner than planned and might as well rewind them things now. Got the desoldering iron all warmed up to pull the old ones. Vince - K8ZW. On 02/22/2022 05:45 PM, Diogenio via groups.io wrote:
Hey Vince: --
Michigan VHF Corporation -- nobucks dot net K8ZW - |