Support for some kind of large screen

Please add any feature requests for Flowcode version 7 here

Moderator: Benj

Post Reply
PicoPuls
Posts: 111
Joined: Wed Mar 02, 2016 11:26 am
Has thanked: 43 times
Been thanked: 22 times
Contact:
Contact PicoPuls

Support for some kind of large screen

Post by PicoPuls »

I am looking for a large screen solution for a coming project.
VGA would be great or a 10" TFT

There is an e-block VGA card, EB033, with no high level functionality at all
and it will probably keep the processor occupied at 100%. (Just a guess)
http://www.matrixtsl.com/webshop/e-bloc ... board.html

Recently there was a high level VGA e-board available, EB071, and I bought a couple of them,
as they seemed to be the best alternative. But that product seems to be discontinued now
and can not be found on the matrix website

Here it is http://uk.rs-online.com/web/p/interface ... s/8892876/

Basically, I want to draw lines and make a 4 channel oscilloscope for a slow process,
approx 2 Hz sweep

As a feature request I would look forward to further Flowcode 7 support in the VGA direction.
It is always possible to find a VGA screen, making the processor board cheap.
A large screen, easy to connect, at almost no cost for diagnosis , must be very interesting for many projects.
Top
User avatar
Benj
Matrix Staff
Posts: 15312
Joined: Mon Oct 16, 2006 10:48 am
Location: Matrix TS Ltd
Has thanked: 4803 times
Been thanked: 4314 times
Contact:
Contact Benj

Re: Support for some kind of large screen

Post by Benj »

Hello,

I see there is a uVGA III module available from 4D systems now.

They dropped support for the uVGA II module a while back which is why we stopped selling the EB071 hardware.

The uVGA III should already work with the 4D Picaso component in Flowcode so hopefully this is an option for you.
Top
Brendan
Posts: 243
Joined: Tue Nov 27, 2012 12:53 pm
Location: Cambridge, UK
Has thanked: 140 times
Been thanked: 118 times
Contact:
Contact Brendan

Re: Support for some kind of large screen

Post by Brendan »

A big thumbs-up for 4D products from me too. We've used their 4.3" capacitive touch displays for stand-alone test equipment featuring VI's and touch keyboards. Their Picaso processors (and faster Diablo if needed) are just the ticket for working with small MCUs as they off-load screen driving requirements from your micro.

The 4D workshop software also offers the ability to compile in the WYSIWYG environment and export 4D firmware created from included form templates and components (oscilloscopes are included), or you can code in native 4DGL language if you want for anything more customised or specific to your needs. Their graphical templates are quite extensive though, so development is quite straightforward and leaving you only having to stream serial form-control data from your micro to the 4D chip.

All the best,

Brendan
Top
PicoPuls
Posts: 111
Joined: Wed Mar 02, 2016 11:26 am
Has thanked: 43 times
Been thanked: 22 times
Contact:
Contact PicoPuls

Re: Support for some kind of large screen

Post by PicoPuls »

Hi.
Nice that uVGA III is available, but I still want to evaluate with the "old" uVGA II = EB071
as I have two of them on my lab.

To evaluate EB071 the EB071 test routine for Fc6 was loaded into Fc7
It resulted in the following errors (the same in Fc6 )

Compiler Messages
Errors when generating C source code:
VGA_v7.c : 1 : error: Unknown or missing component: v5_custom20::SetVGADisplaySize Picaso
VGA_v7.c : 1 : error: Unknown or missing component: v5_custom20::DrawGrcle
VGA_v7.c : 1 : error: Unknown or missing component: v5_custom20::PlayAudio From File Picaso
VGA_v7.c : 1000 : error: Unknown or missing component: v5_custom20::SetVGADisplaySizePicaso
VGA_v7.c : 1020 : error: Unknown or missing component: v5_custom20::DrawGrcle
VGA_v7.c : 1029 : error: Unknown or missing component: v5_custom20::PlayAudioFromRlePicaso
FINISHED

To test the factory hex test, I followed the instructions in EB071-12-1.doc
Send the hex to EB006 with PPP
But PPP couldn't find EB006
With mLoader.exe it worked, but still no VGA action to observe

Am I doing some mistake here ?

Best regards
Bengt
Top
PicoPuls
Posts: 111
Joined: Wed Mar 02, 2016 11:26 am
Has thanked: 43 times
Been thanked: 22 times
Contact:
Contact PicoPuls

Re: Support for some kind of large screen

Post by PicoPuls »

I have to add...

After building different example files with Flowcode6,
at last I found one example that worked and draw simple graphics on screen,
This works under Fc7 also, Now there is hope indeed !

Just an additional question:
If a slow graph like an oscilloscope shall be drawn,
what would the best approach be to erase the first graph when the second is about to appear ?
If it is not erased all the graphs will probably accumulate on screen
Clear the entire screen will probably cause flicker
Any idea ?

Best regards
Bengt
Top
PicoPuls
Posts: 111
Joined: Wed Mar 02, 2016 11:26 am
Has thanked: 43 times
Been thanked: 22 times
Contact:
Contact PicoPuls

Re: Support for some kind of large screen

Post by PicoPuls »

The example2 that is loading images on VGA works under Flowcode6 but gives errors under Flowcode7

Code: Select all

Example2_v7_error.c:
   196:	rom char *xlut = {120,125,130,135,140,145,149,153,157,160,163,165,167,168,169,170,169,168,167,165,163,160,157,153,149,145,140,135,130,125,120,114,109,104,99,95,90,86,82,79,76,74,72,71,70,70,70,71,72,74,76,79,82,86,90,95,99,104,109,114};
	    ^ (374) missing basic type; int assumed (warning)
	    ^ (314) ";" expected
	                     ^ (357) illegal conversion of integer to pointer (warning)
	  (316) "}" expected ^
	   (314) ";" expected ^
   197:	rom char *ylut = {110,110,111,112,114,116,119,122,126,130,135,139,144,149,154,160,165,170,175,180,185,189,193,197,200,203,205,207,208,209,210,209,208,207,205,203,200,197,193,189,185,180,175,170,165,160,154,149,144,139,135,130,126,122,119,116,114,112,111,110};
	    ^ (374) missing basic type; int assumed (warning)
	    ^ (314) ";" expected
	                     ^ (357) illegal conversion of integer to pointer (warning)
	  (316) "}" expected ^
	   (314) ";" expected ^
(908) exit status = 1
(908) exit status = 1
C:\Program Files (x86)\Flowcode 7\compilers\pic\bin\xc8.exe reported error code 1


Can anyone explain how to make it work under Flowcode7 ?
The file is Example2.fcf in uploaded zip
Attachments
EB071_Test_Files.zip
(208.23 KiB) Downloaded 284 times
Top
PicoPuls
Posts: 111
Joined: Wed Mar 02, 2016 11:26 am
Has thanked: 43 times
Been thanked: 22 times
Contact:
Contact PicoPuls

Re: Support for some kind of large screen

Post by PicoPuls »

When using the example 2 for EB071 everything works well on 16F887
But I need to go over to the more powerful dsPIC33EP512MU810

It was not possible just to transfer the code to an other chip on port C

Error message when changing chip says:

Pin 0 of component v5_glcd0 is connected to bit 5 of port C but this
port / bit does not exist on the new microcontroller.

As I am new to UART, can anybody give me an idea how to find the right pins ?

Thanks & Best regards
Bengt
Attachments
noexcist3.jpg
noexcist3.jpg (47.42 KiB) Viewed 14163 times
Top
User avatar
QMESAR
Valued Contributor
Valued Contributor
Posts: 1287
Joined: Sun Oct 05, 2014 3:20 pm
Location: Russia
Has thanked: 384 times
Been thanked: 614 times
Contact:
Contact QMESAR

Re: Support for some kind of large screen

Post by QMESAR »

The dsPIC33EP has remap able pins therefore the FC flowchart for the PIC16 can never directly be used with the dsPIC33

To change the Reset pin just click on the &PORTC.5 (for exqmple) in the properties window of the glcd and the Micro View port will open you can then select any pin you want secondly for the RX and TX pins to work you need to click on the arrow behind the RX or TX pin and select the pin you want to remap to just take care and check the datasheet too which pins the mcu allows you to remap too as it is not possible to just remap to any pin
Attachments
2.JPG
2.JPG (33.39 KiB) Viewed 14158 times
1.JPG
1.JPG (64.41 KiB) Viewed 14158 times
Top
PicoPuls
Posts: 111
Joined: Wed Mar 02, 2016 11:26 am
Has thanked: 43 times
Been thanked: 22 times
Contact:
Contact PicoPuls

Re: Support for some kind of large screen

Post by PicoPuls »

Thanks Qmesar for instructions,

I have Flowcode7 but one complication is that
Fc7 can't build the eblock EB071 test file
so I just have to use Fc6

I have also searched the 622 pages and printed out some pages regarding remapping of pins
http://ww1.microchip.com/downloads/en/D ... 70616g.pdf
without finding a clear conclusion about possible UART reset pins.

When I try to pick UART reset pin, I sure see the chip pins, but whatever I pick, the RX and RX remain unconnected.
See image

It is the first time I use UART on such a big chip and help would be very appreciated
Thanks and best regards
Bengt
Attachments
dsPIC33UARTres.jpg
dsPIC33UARTres.jpg (48.58 KiB) Viewed 14152 times
Top
User avatar
QMESAR
Valued Contributor
Valued Contributor
Posts: 1287
Joined: Sun Oct 05, 2014 3:20 pm
Location: Russia
Has thanked: 384 times
Been thanked: 614 times
Contact:
Contact QMESAR

Re: Support for some kind of large screen

Post by QMESAR »

Well you have to click on the TX Remap and RX Remap pins just below the High speed tab
below is with me in FC6 I have set the UART pins to PORTF.12 and F13 for example you will see then the TX and RX pins are connected
to what ever you selected in the Remap position

:D
Attachments
1.JPG
1.JPG (52.65 KiB) Viewed 14150 times
2.JPG
2.JPG (76.45 KiB) Viewed 14150 times
Top
PicoPuls
Posts: 111
Joined: Wed Mar 02, 2016 11:26 am
Has thanked: 43 times
Been thanked: 22 times
Contact:
Contact PicoPuls

Re: Support for some kind of large screen

Post by PicoPuls »

After playing around, I probably got an acceptable UART setting. See bottom image
If this is OK, I am deeply impressed how Flowcode simplifies all this complexity

But now, also Flocode 6 generates a lot of errormessages, where the same code was free from problems with PIC16F887
Only chip and UART pins have been changed

Code: Select all

Example2_v6_ok_0000004_ds33_err.c:341: error: syntax error before 'char'
Example2_v6_ok_0000004_ds33_err.c:341: warning: initialization makes pointer from integer without a cast
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:341: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:341: warning: (near initialization for 'xlut')
Example2_v6_ok_0000004_ds33_err.c:342: error: syntax error before 'char'
Example2_v6_ok_0000004_ds33_err.c:342: warning: initialization makes pointer from integer without a cast
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c:342: warning: excess elements in scalar initializer
Example2_v6_ok_0000004_ds33_err.c:342: warning: (near initialization for 'ylut')
Example2_v6_ok_0000004_ds33_err.c: In function 'FCD_0f051_v5__glcd0__PrintNumber':
Example2_v6_ok_0000004_ds33_err.c:840: warning: pointer targets in passing argument 2 of 'FCI_TOSTRING' differ in signedness
Example2_v6_ok_0000004_ds33_err.c: In function 'FCD_0f051_v5__glcd0__DrawLine':
Example2_v6_ok_0000004_ds33_err.c:866: warning: unused variable 'FCL_XINC'
Example2_v6_ok_0000004_ds33_err.c:865: warning: unused variable 'FCL_YINC'
Example2_v6_ok_0000004_ds33_err.c:864: warning: unused variable 'FCL_PIXELY'
Example2_v6_ok_0000004_ds33_err.c:863: warning: unused variable 'FCL_PIXELX'
Example2_v6_ok_0000004_ds33_err.c:862: warning: unused variable 'FCL_D1'
Example2_v6_ok_0000004_ds33_err.c:861: warning: unused variable 'FCL_M1'
Example2_v6_ok_0000004_ds33_err.c:860: warning: unused variable 'FCL_C1'
Example2_v6_ok_0000004_ds33_err.c: In function 'FCD_0f051_v5__glcd0__G4D_DisplayImageFromFilePicaso':
Example2_v6_ok_0000004_ds33_err.c:920: warning: pointer targets in passing argument 1 of 'FCI_SHEAD' differ in signedness
Example2_v6_ok_0000004_ds33_err.c:920: warning: pointer targets in passing argument 3 of 'FCI_SHEAD' differ in signedness
Example2_v6_ok_0000004_ds33_err.c:920: warning: pointer targets in passing argument 5 of 'FCI_SHEAD' differ in signedness
Example2_v6_ok_0000004_ds33_err.c: In function 'FCD_0f051_v5__glcd0__Print':
Example2_v6_ok_0000004_ds33_err.c:1427: warning: pointer targets in passing argument 1 of 'FCI_GETLENGTH' differ in signedness
Example2_v6_ok_0000004_ds33_err.c: In function 'FCD_0f051_v5__glcd0__ClearDisplay':
Example2_v6_ok_0000004_ds33_err.c:1574: warning: unused variable 'FCL_X'
Example2_v6_ok_0000004_ds33_err.c:1573: warning: unused variable 'FCL_Y'
Example2_v6_ok_0000004_ds33_err.c: In function 'FCD_0f051_v5__glcd0__SetBackgroundColour':
Example2_v6_ok_0000004_ds33_err.c:1602: warning: unused variable 'FCL_COLOUR'
Example2_v6_ok_0000004_ds33_err.c: In function 'FCD_0f051_v5__glcd0__SetForegroundColour':
Example2_v6_ok_0000004_ds33_err.c:1683: warning: unused variable 'FCL_COLOUR'
Example2_v6_ok_0000004_ds33_err.c: In function 'FCD_0f051_v5__glcd0__G4D_PlayAudioFromFilePicaso':
Example2_v6_ok_0000004_ds33_err.c:1765: warning: pointer targets in passing argument 1 of 'FCI_SHEAD' differ in signedness
Example2_v6_ok_0000004_ds33_err.c:1765: warning: pointer targets in passing argument 3 of 'FCI_SHEAD' differ in signedness
Example2_v6_ok_0000004_ds33_err.c:1765: warning: pointer targets in passing argument 5 of 'FCI_SHEAD' differ in signedness
Example2_v6_ok_0000004_ds33_err.c: In function 'FCD_0f051_v5__glcd0__DrawRectangle':
Example2_v6_ok_0000004_ds33_err.c:1832: warning: unused variable 'FCL_YMAX'
Example2_v6_ok_0000004_ds33_err.c:1831: warning: unused variable 'FCL_YMIN'
Example2_v6_ok_0000004_ds33_err.c:1830: warning: unused variable 'FCL_XMAX'
Example2_v6_ok_0000004_ds33_err.c:1829: warning: unused variable 'FCL_XMIN'
Example2_v6_ok_0000004_ds33_err.c: In function 'FCD_0f051_v5__glcd0__Initialise':
Example2_v6_ok_0000004_ds33_err.c:1976: warning: right shift count >= width of type

Error returned from [pic30-gcc.exe]
.
Completed compilation, return = 1
Also in the original & working TestFile the resetpin was $PORTC0.5
Does the zero have a meaning or was it just a mistake?
Attachments
This is the original testfile
This is the original testfile
originaluart.jpg (13.29 KiB) Viewed 14148 times
This is the UART for dsPIC33EP512MU810<br />Probably acceptable UART setting (?)
This is the UART for dsPIC33EP512MU810
Probably acceptable UART setting (?)
dsPIC33UARTres2.jpg (13.68 KiB) Viewed 14148 times
Top
User avatar
QMESAR
Valued Contributor
Valued Contributor
Posts: 1287
Joined: Sun Oct 05, 2014 3:20 pm
Location: Russia
Has thanked: 384 times
Been thanked: 614 times
Contact:
Contact QMESAR

Re: Support for some kind of large screen

Post by QMESAR »

from the datasheet page 210 the UART1 is tied to RPI pins such as PORTA.2 and the UART1 TX is tied to a RP pin
You have to make sure you us the correct pins see datasheet peripheral pin select from page 210 you can for example use PRI52 for RX which is RC4 and PR85 for TX which is RE5

RD6 and 7 will work for the TX pin however you have to select a RPI pin for RX
Top
User avatar
QMESAR
Valued Contributor
Valued Contributor
Posts: 1287
Joined: Sun Oct 05, 2014 3:20 pm
Location: Russia
Has thanked: 384 times
Been thanked: 614 times
Contact:
Contact QMESAR

Re: Support for some kind of large screen

Post by QMESAR »

Can you please post the example code you are using that I can try it with my FC6 :D
Top
PicoPuls
Posts: 111
Joined: Wed Mar 02, 2016 11:26 am
Has thanked: 43 times
Been thanked: 22 times
Contact:
Contact PicoPuls

Re: Support for some kind of large screen

Post by PicoPuls »

Sure,
The Matrix Example2 is only changed in 2 ways
1. New chip
2. One single jpg image, but it is on the SD card and doesn't influence on build
Thanks and Best Regards Bengt
Attachments
Example2_v6_ok_0000004_ds33_err.fcfx
(6.96 KiB) Downloaded 169 times
Top
User avatar
QMESAR
Valued Contributor
Valued Contributor
Posts: 1287
Joined: Sun Oct 05, 2014 3:20 pm
Location: Russia
Has thanked: 384 times
Been thanked: 614 times
Contact:
Contact QMESAR

Re: Support for some kind of large screen

Post by QMESAR »

The Example code shows many errors with me as well however i just made a new project of my own placed the component call blocks and set
the function as in the Example code and it compilers fine in FC6 and in FC 7 if this was my project i would only us the example to see the function calls and make my own project draw the flowchart and compile and get the gLCD running not wasting time to fine out if the example is somehow corrupted
Attachments
1.JPG
1.JPG (38 KiB) Viewed 14124 times
Top
PicoPuls
Posts: 111
Joined: Wed Mar 02, 2016 11:26 am
Has thanked: 43 times
Been thanked: 22 times
Contact:
Contact PicoPuls

Re: Support for some kind of large screen

Post by PicoPuls »

Than's good news.

Can you please post the example code created
If it works under Fc7 as well, I would be very happy

Thanks and best regards
Bengt
Top
User avatar
QMESAR
Valued Contributor
Valued Contributor
Posts: 1287
Joined: Sun Oct 05, 2014 3:20 pm
Location: Russia
Has thanked: 384 times
Been thanked: 614 times
Contact:
Contact QMESAR

Re: Support for some kind of large screen

Post by QMESAR »

Here is the FC7 project :D
Attachments
glcd.zip
(78.63 KiB) Downloaded 177 times
Top
PicoPuls
Posts: 111
Joined: Wed Mar 02, 2016 11:26 am
Has thanked: 43 times
Been thanked: 22 times
Contact:
Contact PicoPuls

Re: Support for some kind of large screen

Post by PicoPuls »

Thank you very much
In builds successfully !

The original Matrix example uses ports 5-6-7 and that's the way the EB071 is wired
Do you think that I could just change the ports in your new example to PORTC.5 PORTC.6 PORTC.7
How do I know that flowcode can map this UART functionality to these pins ?

Best regards
Bengt
Attachments
new_and_original.jpg
new_and_original.jpg (39.56 KiB) Viewed 14096 times
Top
User avatar
QMESAR
Valued Contributor
Valued Contributor
Posts: 1287
Joined: Sun Oct 05, 2014 3:20 pm
Location: Russia
Has thanked: 384 times
Been thanked: 614 times
Contact:
Contact QMESAR

Re: Support for some kind of large screen

Post by QMESAR »

Hi I don't think so as the chip does not have RC6 and 7 you will have to check the schematic on which pins these pins of the EB connects to on the dsPIC and see if they can be mapped to the UART
How do I know that flowcode can map this UART functionality to these pins ?
FC will map to the pins that is allowed by the Remap able registers but you need to know which pins can be mapped and select accordingly in FC,
Flowcode does a lot of hard work in the back ground however you need to understand the micro a bit as well as FC can not do every thing :D
Top
PicoPuls
Posts: 111
Joined: Wed Mar 02, 2016 11:26 am
Has thanked: 43 times
Been thanked: 22 times
Contact:
Contact PicoPuls

Re: Support for some kind of large screen

Post by PicoPuls »

Hi
I have tried in so many ways but dsPIC33EP512MU810 refuses to handle the VGA screen with Eblock EB071
For that reason I now try smaller chips to see if Eblock EB071 works

When I try to use 18F45K22 and build with Flocode7 there is an error:

PIC18F45k22_C567.c:
36:_config('_PROG_CONFIGM. "pic18". 0x4. CbcFF);
A (1504) the PIC 18 extended instruction set was enabled but is not supported by this compiler
(908) exit status = 1

When 18F45K22 + Eblock EB071 is built with Flowcode6 there is no error,

What can a Flowcode user do whit these errors,
Can they be resolved or is the functionality hidden under the hood?
Top
User avatar
QMESAR
Valued Contributor
Valued Contributor
Posts: 1287
Joined: Sun Oct 05, 2014 3:20 pm
Location: Russia
Has thanked: 384 times
Been thanked: 614 times
Contact:
Contact QMESAR

Re: Support for some kind of large screen

Post by QMESAR »

PIC18F45k22_C567.c:
36:_config('_PROG_CONFIGM. "pic18". 0x4. CbcFF);
A (1504) the PIC 18 extended instruction set was enabled but is not supported by this compiler
(908) exit status = 1
This is once again not a FC issue however it is a matter of understanding the chip you are working with ,switch of the extended instruction set in the configuration properties

Also Please can you open a new topic for your problems as we have been hi jacking this post the moderators will go mad on us this has nothing to do with a future request any more
Attachments
1.JPG
1.JPG (49.27 KiB) Viewed 14079 times
Top
PicoPuls
Posts: 111
Joined: Wed Mar 02, 2016 11:26 am
Has thanked: 43 times
Been thanked: 22 times
Contact:
Contact PicoPuls

Re: Support for some kind of large screen

Post by PicoPuls »

The forum has fulfilled its most important goal, I have gained understanding, I am grateful for all the help
and the thread has had a lot of views.

To conclude the feature request:
The 4D Systems VGA-II and III is in my view by far the most interesting way to connect a large screen to a small processor.

My humble suggestion is that Matrix puts the EB071 back in production and adjusts it for the new uVGA-III
and develops the FC7 library further for all the new uVGA-III- features.

Regards
Bengt
Top
Post Reply

Return to “Feature requests”