Matrix user forums

This seems strange. I cannot see anything in the RS232 code that would alter the clock settings. If you are still having problems, please send your program to our support email and we'll have a quick look.

It sounds like the drivers have not been installed correctly. You should try the following procedure before reinstalling the course. On the CD there is a program called "F:\ARM Board USB Driver Installer\ARMBoardDriverInstaller.exe". Run this program to install the drivers. Once this has completed s...

So does the "professional" version of v2 (if you download the addon pack).

A simpler method is to use the EEPROM component within FlowCode. This has inbuilt "macros" to read and write to the internal EEPROM.

3 things are required: 1) A 'C' icon at the beginning of your program with "osccon = 0x70;" in it (this will set the internal oscillator to 8MHz). 2) The correct configuration data: - oscillator = INTRC - internal external switch over mode = enabled 3) Specify the appropriate clock frequency within ...

Do you know of any wizard to setup I/O, Timers, UART etc.?

I'm sorry, but I don't. There may be something about this later in the C4ARM course, otherwise you will need to refer to the ARM datasheet.

Peter,

Thank you for being patient and finding the workaround to this problem. It has thrown up problems with our testing procedures that we will correct in future.

A few of our customers have had problems with our ARM programmer board not being recognised when it is plugged into the PC. This is by design: The ARM board does not identify itself to the PC when it is plugged in – it only boots up as a USB device when it is expecting to be reprogrammed. To do th...

I've just had a look at these programs, and I can see why there might be problems. I'm not 100% sure, but the problem could be with these lines: /* if the light is on turn it off */ if (input_pin_port_a(0)) { output_low_port_a(0); } else { /* if the light is off turn it on */ output_high_port_a(0); ...

That's good news that we've found the cause of the problem. Now for the solution... Either add this directory to the path each time you start your computer by creating a batch file and running it whenever necessary, or edit the locations of these tools within Programmers Notepad as described in my p...

Hello Peter, This is quite a new product for us, which is why there are no other posts about it on this forum. But you're not the first user of this kit (but possibly the first one who has found a problem). It looks like Programmer's Notepad cannot find the "make.exe" file on your PC. It should live...

I think this program expects the clock speed to be 3.2768MHz. If you run with a 10MHz crystal, the clock should run approx 3 times too fast. To get the program running closer to "real" seconds, you must change the interrupt frequency in the "interrupt" icon of the "initialise" macro to 25Hz. Unfortu...

I'm not very familiar with this product, but I'll try to help. I've just tried to build a project and I got an error message: ** No rule to make target 'all': stop When I double-click the "main.c" file in Programmer's Notepad to view it, I can then "Build All" successfully. It looks like you need to...

There are a number of different ways to do this. The quickest (but hardest?) way is to use the masking feature of the input icon (entire port... use masking... and tick the bits which your switches are connected to). You would also need to declare a variable (e.g. "State") to accept the result. Then...

There is a trick to see the compilation errors, which might explain more about why the 16F88 program is failing. See this topic: http://matrixmultimedia.com/mmforums/viewtopic.php?t=36 I'd also suggest making sure your program does not access PORTC anywhere (including in the property page for the RS...

We've found an unusual bug with the underlying compiler used by both v2 and v3 of FlowCode. If you have an ampersand (&) character in the path of your flowchart, the compiler will fail. For example, if you saved your file as "C:\My files&stuff\abc.fcf", the compilation would fail. There is no fix fo...

1. Not sure why it won't work with a 16F627 - does it work with the 16F627a? Also note that the UART for the 627 is on port b, not port c as with the 877. And the tx/rx pins are different. Are there any specific error messages? 2. You could create a variable "in" and use it to accept the input from ...

I think it's always a good idea to provide some kind of protection when connecting to a PIC i/o line, mainly because the program you write may accidentally set the pin as an output. If it gets set to output low but the external circuitry is forcing it high, there is a good chance that the micro itse...

This is a common misconception. On the 16F88 chip, outputs A5 to A7 are multiplexed with the MCLR reset and the OSC1/2 external oscillator inputs. On our dev board, these pins are wired directly to the reset button and the oscillator circuitry, and not to the LEDs and switches (SA5-7 and LA5-7). We ...

Sorry, Dave. I know the RS232 component needs some work. I'm hoping to spend some time on it once we've put FlowCode v3 to bed.

Switches (when set to toggle mode) now keep their state (open or closed) when the simulation starts. This should make you happy!

I think you need to call the "AddDefines" macro from within your program - this tells FlowCode that the component is being used and needs to be included in the compiled code.

The current hold-up with FlowCode v3 is because we are waiting for a new release of the underlying C compiler. This should be out very soon (this week or next).

We have also just released the latest BETA for testing, so barring any major problems we should be releasing the product by mid-October.

Hello Dave, I'll ask Ian to dig out the FlowCode file for the RS232 program and send it to you. However, I don't think it's possible to set this to run at 57.6kHz. As for your second question, you should be able to set up a routine that continually monitors for incoming characters. When a comma is r...

Yes, the same advice applies here. In v2 of FlowCode, use the "#defines" component and add an appropriate __CONFIG line as described above. For those using v3 (which is not many yet because it is not quite ready for release!), the configuration data now gets stored in the FlowCode file and should tr...