ICD Mode part 1a

[saschech@gmx.de]

Hello Matrix Team

To day i connect the display on the EB006 V7 to PD , build "v4 anz_test_flow_PD" , compile to chip workΒ΄s well.

In praxis , change all connections for work V4 correctly, i cannot and i want not do these!

Please give a respond what you think to do about problem " display and PA"

Regards Wolfgang

[Benj]

Hello Wolfgang

Please can you resend in your V3 and V4 C code files again and I will go over the files again. I have noticed that in your programs you are outputting to both portA and portB. Maybe you could create a simpler test program. Eg one that simply starts the LCD and prints HI. This would be far easier to troubleshoot and would also help to pinpoint the problem in your larger program.

[saschech@gmx.de]

Hello Benj

Here the 2 files:

v3_print_HI_PA compile to chip with v3 workΒ΄s

v4_print_HI_PA compile to chip with v4 dont work

Regards Wolfgang

[saschech@gmx.de]

here the c-files

[Steve]

The v4 C file has embedded configuration data, whereas the v3 program does not. Are the config settings (clock, watchdog, etc) appropriate for your hardware?

[saschech@gmx.de]

Hello Steve

I think so.

Regards Wolfgang

[Steve]

Your clock setting might not be appropriate - if you are using a 19.6608 MHz crystal, you need the normal "HS" setting.

The LCD is time-sensitive. When you get problems displaying test on it, you should confirm that the clock speed setting set within Flowcode corresponds to the clock speed of your actual hardware. The best way to do this is with a simple LED flasher program (e.g. flash on and off every second).

[saschech@gmx.de]

Hello Steve

Here 2 c-files with all correct settings

[saschech@gmx.de]

I now , these but with 39.321600 the same ,v3 work v4 dont work

[Steve]

The clock speed still does not look correct, and the v3 program still does not have any config information in it.

Have you done an LED flash test to confirm that the hardware is running at the same speed as defined in Flowcode? This is the only reliable way of confirming that the clock speed settings are correct.

[saschech@gmx.de]

Hello Steve

I am shortly before spin.
I do these any time but with these data i compile to chip is not work on port a

Regards Wolfgang

[Benj]

Hello Wolfgang

OK I have tested the device using the LCD on PortA and a 7.3728MHz crystal. I set the clock speed as 4 x the crystal speed in the Flowcode project options and used your configuration settings from the attached file.

My program is running correctly on the device and the LCD is working as expected on PortA.

I would try Steve's suggestion of creating a 1 second flasher program as it will take you 5 minutes to complete and will confirm once and for all if you have your clock set up correctly.

If the clock settings are correct and your one second flasher program flashes every second as expected then I am at a loss as to why this is not working for you.

[Benj]

Hello Wolfgang

Ok I have now retested this on a fresh copy of V4.1 just to make sure my LCD component had not changed and therefore explained the reason for it working.

The fresh copy of V4.1 also ran the LCD fine on Port A.

[saschech@gmx.de]

Hallo Benj

I deinstall flowcode v3 and v4.
I download new copy of v3 and v4.
I install v3 and v4 new.
I change my chrystal to10MHZ so my hardware works @ 40.MHZ.

open V3

I build a " v3\count_down" file > 60 to 0 @ 1min. (works ok > after 1min count down to 0)
compile to chip with v3 > display works well.

I copy the v3 folder to v3_Kopie

open v4
open the " v3_Kopie\count_down" file ; !! do nothing inside the file !! ; compile to chip with v4 > display dont work.

So i have the realize , to work with v3 i have enough in my head but not for work with v4.

Regards Wolfgang

[Steve]

Wolfgang,

We've tested your program here and it works fine in V4. We had to set the configuration word correctly because we did not have the appropriate crystal. We used a 7.3278MHz crystal with the 4xPLL setting, so we put in 29311200 as the clock speed within Flowcode. We've tried this with V4.1 and 4.2 versions of Flowcode. We've also tried using PPP to program the device and PICkit to program the device. In every case, it has worked ok.

You can try sending us the V3 HEX file that works and the V4 HEX file that doesn't and we'll check the embedded config data in it to make sure it's ok. We can even try loading these HEX files into our hardware to see if they work.

Did you try an LED flasher to confirm that the configuration data was being loaded into the chip correctly?

[saschech@gmx.de]

Hello Steve

Ok i see its a little problem between flowcode and external hardware (my board);
but for my self , i dont understand why the v4 code works on my real hardware on portB,portD and not on portA ; and v3 have no problems.

So i build my one "display-code" ,which work on all ports .

Thanks for help wolfgang