Matrix user forums

If you have updated to 6.1 you will need to download the fixed PIC_CAL_I2C.c file from this thread: http://www.matrixtsl.com/mmforums/viewtopic.php?f=54&t=15416 You may want to remove/comment out the 10 msec delays in the I2C Master Stop function in that file if speed is a concern. You may be able t...

Toggling the SCL pin until the SDA line is released by the slave also seems to do the trick. This is done prior to I2C initialization. This bit of code worked for me...... So I will be using both hardware and software methods.

Software control of power to the slaves fixed this. Another method might be to add some code to the I2C initialization to check for and clean up these I2C "stuck" situations.

edit: found this: http://www.analog.com/static/imported-f ... N686_0.pdf

Hello I have come across some odd behaviour usung MCLR with my program. Sometimes the program will not restart on the first MCLR reset, other times I can hit the switch 20+ times before this happens. A user would rarely use MCLR, but I would like it to be reliable. Once it does happen the program wi...

kersing wrote:After you activate again the correct license should be available.

It seems that I have more than 1 account. Activation now completes successfully with the correct account name.

I can no longer compile to hex after installing the 6.09 patch. License info is now showing only "Home" Version, whereas it should be "Professional." Compiler Messages: Registered to: XXXXXXXXXX Licence key: XXXXXX NOT FOR COMMERCIAL USE http://www.matrixtsl.com Launching the compiler... C:\Program ...

Thanks. Seems I did not have the asm code to test the WDT reset flag quite right to keep BoostC happy. It compiles OK now. Not certain that I need the backslash to separate the asm lines...I think I read it somewhere in the BoostC manual. It seems to compile the same with or without it.

Thanks Benj. Will the code I have added at the beginning of the following example work to set a flag in my program if a WD time-out has occurred? Or is there a better way?

I would like to implement the watchdog timer of a 18F14K50 ( http://ww1.microchip.com/downloads/en/DeviceDoc/41350E.pdf ) for only the main loop of my code. Config settings in my USB bootloader have the WDT disabled and the postcaler set to 1. My main loop cycles at about 5 kHz. Will adding the code...

Oops! A loop count was changed to 256 (=0), effectively placing a code end at point.

I was have having some trouble getting my code to run on chip last night, then I noticed this: When compiling there is the usual long list of unreferenced functions that are removed. This is followed by second "Unreferenced Functions Removed" list that includes functions used in my code. Today it is...

I am running on Win 7/64. I reduced the value of TMR_Max so that I would not be waiting all day and let the count run up to 145 before I stopped the simulation.

I do not receive any error messages when I run your code in simulation on Win7.

Grant

Just to update, the 2 line display with above backpack is also working properly with the I2C LCD component. I also have a couple of other backpacks to test when my LCDs arrive.

The ADC Dial component has gone missing for PIC 18. The I2C LCD component still needs these fixes: (see the last posts in these threads) http://www.matrixmultimedia.com/mmforums/viewtopic.php?f=54&t=14397&p=57234&hilit=lcd#p57234 http://www.matrixmultimedia.com/mmforums/viewtopic.php?f=54&t=14372&p=...

All the best in your future endeavors!

Grant

Thanks Benj. Both were disabled.

Curiously, although I was able to reproduce the above behavior multiple times yesterday, on 2 different circuit boards, the same hex files seem to behave properly when programmed on the same hardware today. I assume this is somehow an issue with the Pickit 3 hardware/software which is now more coope...

Hi Not sure where to put this....... I just noticed that if I select an I2C Master component baud rate of 1 MHz rather than 100kHz or 400 kHz my LEDs are flashing at least twice as fast. This is with a 18F14K50, 12MHz res, 4xPLL, no CPU divide. I did a compare of the 2 ASM files and the only differe...

Hi Benj, My observations after a bit of testing: The config bits/hex values derived now match those produced via V5. There are no error messages when programming with the Pickit3 and standalone Pickit3 app. For new projects the hex values all start as 0x00 and are updated as selections are made. Aft...

Thanks Benj.

I will let you know once I have a chance to play with it.

Grant

Well, I guess it is in a way a programming issue. It appears that V6 writes "1" for unimplemented config bits whereas V5 writes "0". This seems to be what the Pickit3 does not like, resulting in the verification failure. Looking at my CONFIG1L (for this register the unimplemented bits are 7,6,2,1,0)...

I compiled the attached V5 and V6 test programs with the same config settings selected for both, yet different values appear in the compiled ASM code. The values for the V5 code do match those shown in PPP. If I edit the V6 ASM file with the correct config values as copied from V5, then build a new ...

If I try to program my chip with a Pickit3 using the standalone application I get the following error for hex files built with V6. I do not receive this message if programming V5 files. I believe this is the first time I have attempted to load a V6 program without already having a bootloader on chip.

Now that I look back here it appears that I experienced the same issues as Acestu with the I2C display I purchased http://www.ebay.com/itm/New-Blue-IIC-I2C-TWI-2004-20x4-Serial-LCD-Module-Display-for-Arduino-/281141014288?pt=LH_DefaultDomain_0&hash=item41754f6f10 . So the component should also work ...