HEW hangs with FoUSB

I have been working on a project using a M16/Tiny 026F8.  To debug the project, I took a QSK26A and removed the 026F8 from the board.  I then added a 14 pin header to the board and to that header attached the needed lines to control an outboard 026F8.  Specifically:

Pin #   M37641F8HP    026F8

Pin 1    pin 29              pin 28 (P6-5)

Pin 2      gnd                      gnd

Pin 3    pin 59              pin 4 (CNVss)

Pin 4    n/c                   n/c

Pin 5   pin 28,56           pin 26 (P6-7)

Pin 6     gnd                        gnd

Pin 7   pin 57                pin 6 (P8-6)

Pin 8   Vcc                     Vcc

Pin 9  pin 61                  pin 29 (P6-4)

Pin 10  gnd                     gnd

Pin 11  pin 27                pin 27 (P6-6)

Pin 12  gnd                      gnd

Pin 13  pin 62                pin 7 (*reset)

I built a prototype PCB and had it working with HEW.  I had a production run of the PCB's done and they do not work.  I have checked for errors, but the boards ring out identical to the prototype PCB.

I can open up FoUSB and it says it downloads the program and verifys it - but the board does not work when power is applied away from the QSK26A.

In HEW, it recongnizes the board on startup for debugging, and also allows me to download a program. (It does pause for a few seconds after reaching 100% which seems strange)  When I start the program in HEW, nothing seems to happen - breakpoints do not work.  Clicking on the stop button gives the "Communication protocol error (Argument error)(16230)" and I have to use Task Manager to close HEW.

One difference I just thought of is that I am running WIn7 now where I was running Vista before.

If needed, I can post the schematic on my website.

I would really like to get these items on the market, so any help you can provide would be appreciated!

Thanks,

David

Parents
  • Hi David - notice that you have had 30 views in over 24 hours and no answers to your question - kind of sad.

    I thought I would update myself on the latest efforts to make the production boards work - I have an E8 so I loaded the software for it and tried running HEW and my program with the production board with the E8 to see if it would work. It does not - the E8 times out.

    I realize that using the QSK26 the way I did was not "standard" and why Renesas (if they read the forum) would not reply - thus the effort with the E8. But why bother using the QSK26 if you have an E8 available? Simply - the E8 does not provide all the functionality of the QSK26 debugger. As I recall a conversation with Renesas, you have to buy the E10 to have software breakpoints - yet the QSK26 provides software breakpoints with HEW!

    Working with Renesas products for the past 5 years has been a definite love/hate relationship. I love the products - I have used the 26A and 62P on a number of successful projects with the QSK boards. But trying to get the microcontrollers to talk to a debugger with custom hardware has proven to be almost impossible - once with a 26A and once with a 62P. The support received via the forum has been almost non-existent.  I realize I am not a major source of income for Renesas – but I feel that there should still be some sort of support for us small guys.

    I have been designing with and programming microprocessors longer than some of the staff of Renesas has probably been alive (35 years).  So it is not like I do not have a clue as to what I am doing.

    Perhaps the time has come for me to accept a $150 loss on the production boards and another $200 loss on 0260F8 and 62P processors and move on to a different platform

    Not looking for sympathy - or expecting a reply.

    A very frustrated David

Reply
  • Hi David - notice that you have had 30 views in over 24 hours and no answers to your question - kind of sad.

    I thought I would update myself on the latest efforts to make the production boards work - I have an E8 so I loaded the software for it and tried running HEW and my program with the production board with the E8 to see if it would work. It does not - the E8 times out.

    I realize that using the QSK26 the way I did was not "standard" and why Renesas (if they read the forum) would not reply - thus the effort with the E8. But why bother using the QSK26 if you have an E8 available? Simply - the E8 does not provide all the functionality of the QSK26 debugger. As I recall a conversation with Renesas, you have to buy the E10 to have software breakpoints - yet the QSK26 provides software breakpoints with HEW!

    Working with Renesas products for the past 5 years has been a definite love/hate relationship. I love the products - I have used the 26A and 62P on a number of successful projects with the QSK boards. But trying to get the microcontrollers to talk to a debugger with custom hardware has proven to be almost impossible - once with a 26A and once with a 62P. The support received via the forum has been almost non-existent.  I realize I am not a major source of income for Renesas – but I feel that there should still be some sort of support for us small guys.

    I have been designing with and programming microprocessors longer than some of the staff of Renesas has probably been alive (35 years).  So it is not like I do not have a clue as to what I am doing.

    Perhaps the time has come for me to accept a $150 loss on the production boards and another $200 loss on 0260F8 and 62P processors and move on to a different platform

    Not looking for sympathy - or expecting a reply.

    A very frustrated David

Children
No Data