Breakpoints V6

[stewartbaker]

Hi,
I am finding it difficult to get breakpoints to work in V6.
With ICD disabled a breakpoint is only recognised when the simulation speed is set to normal. In ICD mode it is not recognised at all.

Please find the attached test program.

16F877A_LED_Flash.fcfx

(4.51 KiB) Downloaded 321 times

Stewart

[stewartbaker]

Nothing ?

[Steve001]

have you had a look at this ?

http://www.youtube.com/watch?v=7amNvPWU ... MzZdLILceQ

Steve

[stewartbaker]

Wrong type of Breakpoint Steve...

[Benj]

Hello Stewart,

With ICD disabled a breakpoint is only recognised when the simulation speed is set to normal.

Thanks for the bug spot, we will investigate this. I might expect this mode from the as fast as possible operation but the slower speeds also seem to have a problem which is strange.

In ICD mode it is not recognised at all.

This bug is already on the list to be fixed, basically the ICD breakpoints are not being set in the breakpoint arrays used by the chip during runtime.

[stewartbaker]

Thanks for your reply Benj.

There seem to be quite a lot of bugs in V6 going on the list.

When is the next release of actual fixes ?

Cheers

Stewart

[Benj]

Hi Stewart,

We are aiming for a release later this week which tackles a fairly large number of new features, bugs, improvements and tweaks.

v6 was a complete rip up of both the underlying architecture and the components that sat on top so it is to be expected that there are bugs. We do feel we are now on the road to a stable release with all the major issues tackled but we are not there quite yet.

One of the big problems was that the main C++ coder for v5 and v6 has now left the company so we had to employ a new member of staff and bring him up to speed very quickly. This obviously has had a large impact on the time it takes to get things resolved but hopefully things should start to speed up again as we work through the list.

[stewartbaker]

Hi Benj,
Thank you for your honest heads up...

I hope that comments made regarding bugs and functionality are taken as constructive, helping to make a good product even better.

Obviously with unlimited resources everything could be achieved immediately. However, it might be useful when the new release comes out to highlight what issues have been fixed and those still needing to be addressed. That should remove a lot of tail chasing...

Looking forward to the next release, hopefully this week.

Cheers

Stewart

[stewartbaker]

Bug is still there in V6.1.2.0.

When is it going to be fixed ?

regards

Stewart

[Benj]

Hello Stewart,

Which version of the hardware are you using? I have just tried breakpoints using ICD in the latest build and they are working correctly for me.

We also have recently hired a new programmer who is helping us work through the list of outstanding problems.

[stewartbaker]

Hi Benj,
Thank you for your reply.

At present I am not using ICD, so I am unable to say if the problem still exists in that mode as well.

The problem I am seeing is when using breakpoints to debug a program before it is even burnt into a PIC.

Unless the simulation speed is set to Normal, breakpoints are not recognised.

This is very irritating as, should I wish to debug at a slow rate, first I need to reset the simulation speed to Normal, run
to a breakpoint, then change the speed. If I need to set another breakpoint I need to repeat the process all over again.

The PIC I am using is a 16F877A.

regards

Stewart

[Benj]

Hello Stewart,

Sorry to hear of your frustration. We are working hard to fix issues like this. I will see if we can bump this specific problem up in priority and get it resolved for you.

[stewartbaker]

Thanks Benj,
Much appreciated.

Stewart