Matrix user forums

@Ben @Martin,

Many thanks for the explanation and fixes.

Hi Martin,

I don't recognize the file type fcdx. My Flowcode project files are type fcfx.

Okay, thanks again. I'll report back how it goes.

Hi Martin, Many thanks for that confirmation. With microcontrollers, I rely on Flowcode simulation testing as much as possible before committing to hardware. As your bug report confirms that the INT0 interrupt does work with the hardware as documented, I'll plow ahead with a prototype on that basis....

Flowcode v 6.1.2.0 The attached trivial program using target PIC12F609 fails to compile. It returns the infamous error code 1. Note: Exactly the same Flowcode environment used for many other successful compilations using other PIC chips. Launching the compiler... C:\Program Files\Flowcode 6\compiler...

So far I have found that internal interrupts, such as those based on timers, don't work in simulation, however with the 16F88 chip I had no problem in simulation with a simple external interrupt such as INT0 on RB0, so I expected to have a similar experience with the 12F617 chip simulation using INT...

At this stage, I am referring to Flowcode's simulation. I can get the GPIO change interrupt option (IOC GPIO) to work in simulation, but GPIO change is not what I want. I only want an external interrupt via GP2. It's INT0 in simulation for this chip that I can't get to work. (Had no problem with INT...

Hi,

I should have mentioned that I did try INT0, but it was not recognized. That is, the interrupt routine was not called.

I have a momentary push-button (active high) attached to GP2. I see the GP2 pin go red on the chip emulator, but for some reason the INT0 routine is not being triggered.

Using Flowcode version: 6.1.2.0 According to Microchip's datasheet for the 12F617, the OPTION register is a readable and writable register, which contains various control bits to configure: • Timer0/WDT prescaler • External GP2/INT interrupt • Timer0 • Weak pull-ups on GPIO So, apart from the WDT, t...

Thanks, good idea.

Can a Flowcode DELAY be terminated via a hardware interrupt? I want to be able to bail out of a long delay via a hardware interrupt (using the INT0 pin on a PIC16F88). The application is a fairly trivial timer, so the simple DELAY function is quite suitable rather than having to use a timer macro ba...

Sorry, just noticed your reply.

No it's the same with all components. I think it may be related related to my screen size setting, which is 1280 x 1024 on a 17 inch monitor.

Also I'm still on XP-Pro (yes, I know ...)

Many thanks indeed for solving the case of the incredible shrinking LED. I wasn't aware of that trick with Panel Properties. As for the shrunken LED, I think that may have been caused by anther issue that I've been meaning to raise: sometimes Flowcode will not allow me to grab the resize points of a...

Occasionally, Flowcode decides that "one or more pins" of a component are not connected, when in fact that is NOT the case. I have attached a trivial program which flashes an LED. Flowcode insists that the LED is unconnected, yet it is connected to port B5, and it does run correctly in simulation. I...

Benj wrote:Or you could go for the 1:256 and alternate between counting up to 30 and counting to 31 to give 0.018 error.

Great idea. Thanks.

Anybody?

Repair process seems to have done the trick.

Okay, thanks. I see you were referring to Windows Control Panel.

I have set the repair process going, but it's taking a very long time to run ... so far.

Benj wrote:You could try repairing the product via the programs control panel

Thanks for the reply. I'll try the repair process first, but cannot see it mentioned. Where is it exactly?

Flowcode v6.1.2.0 reported a runtime error and told me to save my project. I clicked SAVE but Flowcode went into a loop thrashing the hard drive. Eventually I had to terminate Flowcode via the Task Manager. Now when I load any project, I get basically a blank screen with a blank Dashboard Panel and ...

When using Timer 0 as a timer to count elapsed seconds as a 'background' process, I guess it's sensible to run the clock at a rate that minimizes the interrupts per second and thereby minimizes interference with the 'foreground' process, but which clock speed is best? Given that the target chip (PIC...

Hello, The option specifies if the config settings are added to the output hex file or not. If they are not added then the current config settings will be retained when reprogramming your device. Thank you. So for a PIC device (e.g. 16F88), if I don't tick that box, then no config settings will be ...

Version 6.1.2.0

In Project Options --> Configure there's a tick box for "Write config on download", which appears to be unticked by default.

What does that do, and when should I use it?

(No mention of this feature in the associated Wiki page text, only a screenshot showing it ticked.)

Version 6.1.2.0

I can only get breakpoints to be recognized when simulation speed is set to Normal. At any simulation speed less than Normal, the breakpoints are ignored.

There is no specific mention of simulation speed regarding Breakpoints in the Wiki, so is this a bug?

Thank you for explanation.