98.02 feedback

[stan cartwright]

Re add CLC icon by Chris Roper -
;
First download the icon image, “clc.png” that is attached to this post and save it into the C:\GCB@Syn\CLCDesigner
Directory, assuming you used the default install path.===== OK, done.

Now lets add that to the GCBasic Tool Bar.

Right Click on the PPS Icon and select -> Customize toolbar...====Where is the PPS icon?
...

[Chris Roper]

Where is the PPS icon?

It is the icon on the toolbar that says PPS on it.

[stan cartwright]

I looked and ... need new reading glasses.
My other excuse is I fixed the monitor with this pc and didn't get resolution right.
3 caps gone in monitor psu made win10 say no operating system found.
I click add attatchments and goes to top of topics?

[stan cartwright]

After emails from Evan seems my posts about Nextion got over looked.
The first code example Anobium posted here used glcdnexion 320x480.h and glcdprintnexion240x320.
In RC5 there were glcdnexion 320x480.h and glcdnexion 240x320.h
and glcdnextion.h . Note the spelling....I did post about it
These glcdnexion files are in 98.02 but as long as you don't reference them do no harm..just waste space.
It might be easier for Anobium to edit the forum references to nextion/nexion.

[Anobium]

The errant files will be deleted. As they form no function these should not be included in any program, in any way.

These will be around until the next release.

[stan cartwright]

I couldn't add this to a reply to Chris Roper.
Yes it works and sorry for my prescription glasses.

[Gert vd Walt]

Not sure if I am hijacking this thread but having issues starting my own:

Ver 0.98.02 totally ignores "flashthis.bat". is ther a setting I must change?

[Anobium]

Can you please describe what you are doing? Are you using the GCB@SYN IDE? We have a fully integrated programmer interface from this release.

Screen shots will help.

[Gert vd Walt]

I have setup a usb bootloader and edited flashthis.bat to call it and flash the program to the pic via usb. I cant give you screenshots since the only error is "pic kit 2 not found" witch means flashthis.bat is not being run.

[Anobium]

Did you do a full installation?

We are replacing flashthis.bat with the new programmer UI. Have you edited Programmer Preferences Tool?

[Gert vd Walt]

oh, and yes. it is windows 7, gcb@syn. standard instalation

[Anobium]

Can you tell me what USB bootloader please? what are the parameters you had in flashthisbat. Should be very easy to create a new entry in the PPTool.

[Gert vd Walt]

It is this DFU bootloader:
https://github.com/majbthrd/PIC16F1-USB-DFU-Bootloader

I compiled the flash code and put this in flashthis.bat

copy %1 "wrtemp.hex"
"change.exe" wrtemp.hex wrtemp.dfu
"dfu-util.exe" -D wrtemp.dfu

It saves the hes file as wrtemp.hex, then changes it into the dfu standard and calls the dfu util to flash the pic. I put the dfu files in the root of GCB@SYN so as to to have to bother with directories too much

[Anobium]

Can you share you old flashthis.bat please?

[Gert vd Walt]

@echo off
echo *** flashPIC.bat ***
echo.
REM  v0.98.01 - Added chip checking for PicKit2
REM  This batchfile is called from G+Stool.exe if an PIC-chipmodel is detected and
REM  no "FlashThis.bat" is present in the sourcefile-folder.
REM  You can adapt this file to your needs.
REM  %1 is replaced with the hexfile in double quotes i.e. "C:\My Folder\nice file.hex"
REM  %2 is replaced with the chipmodel i.e. 16F688
REM  G+Stool.exe always makes the GCB@Syn root-folder the current folder.


REM  --- Your code here: ---------------------------------------


REM Call XpressLoader for the Xpress Evaluation Board
REM A tool developed as part of Great Cow BASIC
 rem "XpressLoader\XpressLoader.exe" %1


REM Call uploader for TinyBootLoader+ bootloader:
 rem "TinyBootLoader\TinyMultiBootloader+.exe " %1 exit

REM  Call PICpgm-programming software:
 rem "PICPgm\picpgm.exe" -p %1
 rem "PICPgm\picpgm.exe" -delay 1 -if "5PiP" -port COM1 -pic PIC%2 -p %1
 rem "PICPgm\picpgm.exe" -delay 1 -if "JDM Programmer" -port COM1 -pic PIC%2 -p %1
 rem "PICPgm\picpgm.exe" -delay 1 -if "FT232Board-Programmer" -port USB -pic PIC%2 -p %1
 rem "PICPgm\picpgm.exe" -delay 1 -if "FT232Adapter-Programmer" -port USB -pic PIC%2 -p %1

REM PicKit Device Check
REM Remove the rem's from the next indented section to add PICKIT2 chip test check. Lines 27 thru 35.
 rem         "PicKit2\pk2cmd.exe" -I -b"PicKit2" -pPIC%2 > "PicKit2\pictest.txt"
 rem         findstr /C:"Device Name = PIC%2" "PicKit2\pictest.txt"
 rem         IF ERRORLEVEL 1 goto IncorrectChip
 rem         goto OKChipTest1
 rem         :IncorrectChip
 rem         echo Incorrect Chip Found: Not a %2  with parameters  %1 %2 %3 %4 %5 %6 %7 %8 %9 >"G+Stools\FlashError.txt"
 rem         echo Incorrect Chip Found: Not a %2  with parameters  %1 %2 %3 %4 %5 %6 %7 %8 %9
 rem         goto END
 rem         :OKChipTest1

REM  Call PicKit2 command-line programming Software leaving power on the chip
REM  and always exit with MCLR on. Optionally remove -r for MCLR off
Rem "PicKit2\pk2cmd.exe" -b"PicKit2" -pPIC%2 -f%1 -m -j -t -r

REM  Call PicKit2 command-line programming Software without leaving the power on the chip
REM  and always exit with MCLR on. Optionally remove -r for MCLR off
 rem "PicKit2\pk2cmd.exe" -b"PicKit2" -pPIC%2 -f%1 -m -r

REM Call pk3cmd.exe WITH RELEASE FROM RESET
 rem if exist "MPLAB_IPE\PK3cmd.exe" cd MPLAB_IPE & "PK3cmd.exe"  -P%2 -F%1 -L

REM Call pk3cmd.exe WITH RELEASE FROM RESET
 rem if exist "MPLAB_IPE\IPEcmd.exe" cd MPLAB_IPE & "IPEcmd.exe"   -TPPK3  -P%2 -M -F%1 -OL -Z

REM Call pk3cmd.exe WITH RELEASE FROM RESET - DO NOT PROGRAM EEPROM
REM if exist "MPLAB_IPE\PK3cmd.exe"  "MPLAB_IPE\PK3cmd.exe"  -P%2 -F%1 -L -M PICB



REM  Call PicKit3 command-line programming software:
REM  note, that the Java Runtime Environment (jre) has to be installed!
 rem java -jar "C:\Program Files\Microchip\IPE\ipecmd.jar" -TPPK3 -P%2 -M -F%1

REM  Use PicKit3 Integrated Programming Environment GUI (IPE):
REM  note, that IPE must run and a programmer and a PIC is connected!
 rem  "PicKit3\IPE-Pusher.exe" %1 0

REM  Call uploader for diolan bootloader:
 rem  "Bootloader\picboot" -r %1

REM  Call mikroProgSuitePIC-programming software:
 rem  "C:\WinSpr\mikroProgSuitePIC\mikroProg Suite for PIC.exe" -q -w -pPIC%2 -v -f%1

REM  Call MicroBrn K150 programming software:
 rem "K150\microbrn.exe" %1 %2 /f /Q 1

REM  --- End of your code. -------------------------------------

rem Pushd %~p1

rem path "%Great Cow BASIC\toolsdfu\"
copy %1 "wrtemp.hex"
"change.exe" wrtemp.hex wrtemp.dfu
"dfu-util.exe" -D wrtemp.dfu


rem  "Great Cow BASIC\toolsdfu\change.exe" %~n1%~x1 write.dfu


REM  Creating "G+Stools\FlashError.txt" makes G+Stool to leave the message-window open:
if not errorlevel 1 goto END

 echo ERROR running: %0  with parameters  %1 %2 %3 %4 %5 %6 %7 %8 %9 >"G+Stools\FlashError.txt"
 echo ERROR running: %0  with parameters  %1 %2 %3 %4 %5 %6 %7 %8 %9
:END

[Anobium]

Exactly which folder did the "dfu-util.exe" reside in?
%Great Cow BASIC\toolsdfu\ ?
Or elsewhere?

[Anobium]

And, where is the change.exe residing? which folder?

[Gert vd Walt]

They are both in GCB@SYN so I dont have to worry too much about working directories and such

[Gert vd Walt]

as you might see I put a REM in fromt of the path

[Anobium]

OK. Can you ZIP these utilities for me and attach as a ZIP? This means I can sort in a few moments.

[Anobium]

This should work for you,

Create a new entry in the PPTool. The parameters are very simple.

[Gert vd Walt]

You can also have a look at this video to see how it was implemented:

https://www.youtube.com/watch?v=VrHj6z72PK4

The great cow stuff is about half way through.

Thanks for your time thus far

[Anobium]

Very interesting vidoes!! Good job sir!!

[Anobium]

Is Half-a-Bot an important piece to restain? Or, would DFU be ok?

[Gert vd Walt]

If you can give me the procedure or method to do what I need then I will rename and swop and change as needed. Just have to be pointed in the right direction. So dont worry about names and such teach me how to get-R-done. lol