¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. ATU100
  2. Topics

Programming failed at Program Memory address 0x000001 #atu-100

 

Hi all -?

This is a fun little project!

Just finished my build and realized that there is a newer firmware.? I ordered a PickKit 3 clone from ebay and downloaded the programmer software from the MicroChip archive - PiCkit 3 Progammer V 3.10

The programmer detects the correct MCU and I was able to load the ATU version 3.2 hex file and change the eeprom setting for the display,? However every time I try to write the firmware to the board I get a Programming Failed error and when I try to Verify that fails.? ? When I try to read the device at all it looks like its not reading.

All that said - after loading the firmware and getting the "Program failed..." message I reconnected the display and it booted up.? I tried the test mode and can step through the relays with a satisfying "click".

So any idea what may be going on? Faulty programmer?? Faulty operator?? It feels kind of odd to have a device that is working after a 'failed' programming update.? ?

I really like this kit - its a good one for inexperienced builders.? I may do this as group buildathon with our club's Maker's group.

73,
Dean
KK4DAS
 

Sounds to me you might have forgotten to "release" after programming. I don't know how the windows interface looks like but look for reset / release after the write sequence.?

Best regards Onno

Op vr 19 nov. 2021 07:10 schreef Dean Souleles <dsouleles@...>:

Hi all -?

This is a fun little project!

Just finished my build and realized that there is a newer firmware.? I ordered a PickKit 3 clone from ebay and downloaded the programmer software from the MicroChip archive - PiCkit 3 Progammer V 3.10

The programmer detects the correct MCU and I was able to load the ATU version 3.2 hex file and change the eeprom setting for the display,? However every time I try to write the firmware to the board I get a Programming Failed error and when I try to Verify that fails.? ? When I try to read the device at all it looks like its not reading.

All that said - after loading the firmware and getting the "Program failed..." message I reconnected the display and it booted up.? I tried the test mode and can step through the relays with a satisfying "click".

So any idea what may be going on? Faulty programmer?? Faulty operator?? It feels kind of odd to have a device that is working after a 'failed' programming update.? ?

I really like this kit - its a good one for inexperienced builders.? I may do this as group buildathon with our club's Maker's group.

73,
Dean
KK4DAS
 

On Fri, Nov 19, 2021 at 03:56 AM, Onno PA1AP wrote:
Sounds to me you might have forgotten to "release" after programming
Hi Onno,

Thank you.? The Windows software does a verify after write by default.? I click the "write' button and it writes but the verify fails.? It's intermittent where it fails.? Not always at address 1.? And if I just perform a "read' it's clearly not reading properly... Just glancing at the results and I can tell it hasn't read properly. Lots of zeros, even the eeprom read is clearly not working right.

73,
Dean
KK4DAS
 

Not sure unfortunately. I am using Linux and pickit 4 and it works without changing settings.?

It could have to do with timing and the programmer being to fast. There is an option in my settings to use slow writing. Not sure if it exists within windows. Alternative is to use another USB cable since it have found this sometimes causes issues too.?

Hope you can get it to work. Regards Onno

Op vr 19 nov. 2021 12:43 schreef Dean Souleles <dsouleles@...>:

On Fri, Nov 19, 2021 at 03:56 AM, Onno PA1AP wrote:
Sounds to me you might have forgotten to "release" after programming
Hi Onno,

Thank you.? The Windows software does a verify after write by default.? I click the "write' button and it writes but the verify fails.? It's intermittent where it fails.? Not always at address 1.? And if I just perform a "read' it's clearly not reading properly... Just glancing at the results and I can tell it hasn't read properly. Lots of zeros, even the eeprom read is clearly not working right.

73,
Dean
KK4DAS
 

Thanks again Onno,

I verified this morning that it reads ok.? I did a read and then a verify and it is 100%.? I loaded the 3.02 Hex file and did a verify and the Program Memory verifies just fine.??

So it looks like as if my issue is an inconsistent behavior on write.? I did see it succeed on write once or twice - but as you do when you are trying things multiple times you start doubting what you saw.

Thanks again and 73,
Dean
KK4DAS

1 - 5 of 5