Hardware and software settings mismatch

Go To Last Post
11 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'm using the ATF15XX-DK3-U version 1.2 development kit with Atmel ATDH1150USB-K USB interface and WinCUPL version 5.30.4 compiler and ATMISP version 7.2 programming environment. With the kit I received one ATF1502AS-10AU44 CPLD and a ATF1504ASV-15AU44 CPLD.

 

I went through the WINCUPL Tutorial1.pdf and the ATMISP QSTutor.pdf Quick Start Tutorial. There's a bunch of different .PLD project files in the Examples subfolder that came with the WinCUPL software I believe. One of the files called GATES.PLD is used in the WinCUPL tutorial, which tells you to change "signal nand" from Pin 15 to Pin 20.

 

So I compile and program the 1504ASV and everything seems fine, although the device on the evaluation board doesn't seem to light up the correct LEDS and 7-segment displays or respond to the pushbuttons correctly. At this point I didn't realize I had the evaluation board jumpers still set to +5V and the 1504ASV is a 3.3V device. So I try changing the code and reprogramming the device, but when I give a command to Program/Verify, or Erase, or anything, all I get is an error message: Hardware and software settings mismatch.

 

Seems the ATMISP program doesn't think there's a CPLD device present. The ATMISP program tells me "total number of device(s) set in software: 1. total number of real device(s) found in hardware: 0.

 

So I switch over to using the 1502AS which IS a +5V device. I also noticed that in the Example code for GATES.PLD there's LOTS of pin assignments that don't match up with the evaluation board. So I make a bunch of changes, and I'm able to program the CPLD several times, but it never seems to do what I expect it to do. No big surprise since I'm just starting to learn this new code/language and development tools. So I give it a try at programming the original GATES.PLD file and OOPS! the 1502AS starts behaving like the 1504ASV did. Now, it looks like I zapped the second CPLD because all I get is the "Hardware and software settings mismatch" message.

 

Did I destroy the CPLDs somehow with inappropriate pin assignments in the .PLD file code? Any way I can narrow it down to what it is exactly I did wrong? The supply voltage mismatch would explain why the 1504ASV is non-responsive, but not why the 1502AS would be.

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I know this is a very old thread, but it still comes up on google.
I ran into the same issue. I tried to upload an example for a different chip, and now I get this error.
I had to give up and use a different chip. I'd love to get the first one working again though.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

"This error" does not tell anybody anything!

 

Not many CPLD experts in this forum but maybe someone can help you with more information.

 

Jim

 

 

Until Black Lives Matter, we do not have "All Lives Matter"!

 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I get the same generic error as the original poster.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

mvarrik wrote:
Seems the ATMISP program doesn't think there's a CPLD device present. The ATMISP program tells me "total number of device(s) set in software: 1. total number of real device(s) found in hardware: 0.

 

THis error usually meant that the wiring from teh programmer to teh device(s) is nto correct.

 

What programmer are you using by the way?  I have been searching for one for a few years now.

 

JIm

I would rather attempt something great and fail, than attempt nothing and succeed - Fortune Cookie

 

"The critical shortage here is not stuff, but time." - Johan Ekdahl

 

"Step N is required before you can do step N+1!" - ka7ehk

 

"If you want a career with a known path - become an undertaker. Dead people don't sue!" - Kartman

"Why is there a "Highway to Hell" and only a "Stairway to Heaven"? A prediction of the expected traffic load?"  - Lee "theusch"

 

Speak sweetly. It makes your words easier to digest when at a later date you have to eat them ;-)  - Source Unknown

Please Read: Code-of-Conduct

Atmel Studio6.2/AS7, DipTrace, Quartus, MPLAB, RSLogix user

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I got an ATF15xx-DK3-U from Mouser. I'm using the included ATDH1150USB-K programmer.

The wiring is ok. One chip programs and verifies fine, the other generates "the error". The only variable is the chip. They're both ATF1504ASLs.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Possible you have a bad chip...or a pin in the PLCC leads is bent?

 

JIm

I would rather attempt something great and fail, than attempt nothing and succeed - Fortune Cookie

 

"The critical shortage here is not stuff, but time." - Johan Ekdahl

 

"Step N is required before you can do step N+1!" - ka7ehk

 

"If you want a career with a known path - become an undertaker. Dead people don't sue!" - Kartman

"Why is there a "Highway to Hell" and only a "Stairway to Heaven"? A prediction of the expected traffic load?"  - Lee "theusch"

 

Speak sweetly. It makes your words easier to digest when at a later date you have to eat them ;-)  - Source Unknown

Please Read: Code-of-Conduct

Atmel Studio6.2/AS7, DipTrace, Quartus, MPLAB, RSLogix user

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I was able to program it exactly once (with incorrect pin assignments in the code). Now it won't program anymore.
It seems that what I uploaded has caused this.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

are they programmable more than once? or OTP chips?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

They are able to be programmed more than once. Even if they weren't, I would expect they would respond to a blank-check. This one is currently completely unresponsive.

I'm guessing I inadvertently disabled the JTAG connection. Looks like there's an equivalent to HVP, where a single pin needs 12V, then you can restore the JTAG functionality.
I strumbled on details here:  https://www.hackup.net/2020/01/erasing-and-programming-the-atf1504-cpld/

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

What does the datasheet say?

I cannot imagine that this High voltage programming bit is not mentioned in the datasheet.

Might be a very short note at the description of the Vpp pin.