Sorry but I cannot reproduce the problem.
I tried on Mint 17 64 bit, which is based on Ubuntu.
Was the compilation successful?
Did you build after updating from a previous release of opgui?
In that case you should first do "make clean".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2015-01-05
Alberto, Happy NewYear.
Thank you for quick answer.
I recompiled opgui.Haved some warnings..but binary worked some.
Newly compiled Opgui terminated with bufer overflow after 20-25 sec
i tryed IO-pin tested.
This is compilation procedure log.
@megaded:/usr/local/opgui# make
gcc -Wall -Os -s pkg-config --libs --cflags gtk+-2.0 -c opgui.c
opgui.c: In function 'ICDHelp':
opgui.c:832:34: warning: format not a string literal and no format arguments [-Wformat-security]
opgui.c: In function 'HexSave':
opgui.c:1803:4: warning: format not a string literal and no format arguments [-Wformat-security]
opgui.c: In function 'main':
opgui.c:1943:3: warning: format not a string literal and no format arguments [-Wformat-security]
opgui.c:1961:3: warning: format not a string literal and no format arguments [-Wformat-security]
opgui.c:2512:3: warning: format not a string literal and no format arguments [-Wformat-security]
opgui.c: In function 'MsgBox':
opgui.c:2535:34: warning: format not a string literal and no format arguments [-Wformat-security]
gcc -Wall -Os -s pkg-config --libs --cflags gtk+-2.0 -c deviceRW.c
gcc -Wall -Os -s pkg-config --libs --cflags gtk+-2.0 -c progP12.c
gcc -Wall -Os -s pkg-config --libs --cflags gtk+-2.0 -c progP16.c
progP16.c: In function 'PIC16_ID':
progP16.c:223:4: warning: format not a string literal and no format arguments [-Wformat-security]
gcc -Wall -Os -s pkg-config --libs --cflags gtk+-2.0 -c progP18.c
gcc -Wall -Os -s pkg-config --libs --cflags gtk+-2.0 -c progP24.c
gcc -Wall -Os -s pkg-config --libs --cflags gtk+-2.0 -c progEEPROM.c
progEEPROM.c: In function 'WriteOneWireMem':
progEEPROM.c:1743:3: warning: format not a string literal and no format arguments [-Wformat-security]
gcc -Wall -Os -s pkg-config --libs --cflags gtk+-2.0 -c progAVR.c
gcc -Wall -Os -s pkg-config --libs --cflags gtk+-2.0 -c fileIO.c
fileIO.c: In function 'Load':
fileIO.c:405:7: warning: variable 's' set but not used [-Wunused-but-set-variable]
fileIO.c:404:45: warning: variable 'empty' set but not used [-Wunused-but-set-variable]
gcc -Wall -Os -s pkg-config --libs --cflags gtk+-2.0 -c I2CSPI.c
gcc -Wall -Os -s pkg-config --libs --cflags gtk+-2.0 -c coff.c
coff.c: In function 'analyzeCOFF':
coff.c:28:7: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
coff.c:32:8: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
coff.c:33:8: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
coff.c:39:8: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
coff.c:44:7: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
coff.c:47:7: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
coff.c:120:9: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
coff.c:134:36: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
coff.c:148:9: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
coff.c:149:9: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
coff.c:150:9: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
coff.c:175:9: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
gcc -Wall -Os -s pkg-config --libs --cflags gtk+-2.0 -c icd.c
gcc -Wall -Os -s pkg-config --libs --cflags gtk+-2.0 -c strings.c
echo "#include <gtk gtk.h="">" > icons.c
gdk-pixbuf-csource --extern --build-list write_icon write.png read_icon read.png \
system_icon sys.png go_icon go.png halt_icon halt.png step_icon step.png \
stepover_icon stepover.png stop_icon stop.png >> icons.c
gcc -Wall -Os -s pkg-config --libs --cflags gtk+-2.0 -c icons.c
gcc -Wall -Os -s opgui.o deviceRW.o progP12.o progP16.o progP18.o progP24.o progEEPROM.o progAVR.o fileIO.o I2CSPI.o coff.o icd.o strings.o icons.o pkg-config --libs --cflags gtk+-2.0 -o opgui
Press any key to continue...
Thank you very much for your large work!
Pic16F626 and 16F84 read and write right.
ATmega8 readed quait right
Btw, i have other problems:
- When i attempt reading AT90S2313 in 28 socket alligned pin1
"(Programmer detected on /dev/usb/hiddev0
Firmware version 0.9.0
Hardware ID: 0.0.1 (18F2550)
Synchronization error"
and PIC18F458 not recognised( unknown) and readed only with all 0000 but
one have Bootloader saved...
On Windows under PICPGM in some socket it readed right.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've the same issue. Tried on Mint 13 (ubuntu 12.04).
opgui 0.9.1, exit with "buffer overflow" after some time in I/O testing mode.
And, cannot recognize an ATMEGA644P , give as result
ID 00000
And unknow device, then it read the correct lengt of data, but haven't verified if the data are correct.
The same hardware configuration works well with opgui 0.9.0
How can i log the opgui operations?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After some testing i can confirm that opgui 0.9.1 cannot read / Identify an ATMEGA328.
As for the ATMEGA644, it report ID 00000, and readed data arent correct.
OPGUI0.9.0 works well
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK. It was setting as from the factory. (I suppose 1Mhz internal)
I've another parallel programmer to test, so, if you want i can test whit any fuses configuration you want.
Just to remember you, opgui 0.9.0 work well.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello all!
I-ve Open programmer seting on Ubuntu 12.04 LTS 64 bit platform.
Then i tryed to test I/O and pins of programmer (seting pin to logical "0" or to logical "1")
Opgui terminated with bufer overflow:
this is log fragment:
buffer overflow detected : opgui terminated
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(fortify_fail+0x37)[0x7fd8e7301e67]
/lib/x86_64-linux-gnu/libc.so.6(+0x109d60)[0x7fd8e7300d60]
/lib/x86_64-linux-gnu/libc.so.6(+0x108c33)[0x7fd8e72ffc33]
opgui[0x40e55d]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x488db)[0x7fd8e781b8db]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x133)[0x7fd8e781ad13]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x48060)[0x7fd8e781b060]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0x6a)[0x7fd8e781b45a]
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(gtk_main+0xa7)[0x7fd8e82b4397]
opgui[0x408823]
/lib/x86_64-linux-gnu/libc.so.6(libc_start_main+0xed)[0x7fd8e721876d]
opgui[0x408975]
What's happened?
Thanks,
Qgs
Sorry but I cannot reproduce the problem.
I tried on Mint 17 64 bit, which is based on Ubuntu.
Was the compilation successful?
Did you build after updating from a previous release of opgui?
In that case you should first do "make clean".
Alberto, Happy NewYear.
Thank you for quick answer.
I recompiled opgui.Haved some warnings..but binary worked some.
Newly compiled Opgui terminated with bufer overflow after 20-25 sec
i tryed IO-pin tested.
This is compilation procedure log.
@megaded:/usr/local/opgui# make
gcc -Wall -Os -s
pkg-config --libs --cflags gtk+-2.0
-c opgui.copgui.c: In function 'ICDHelp':
opgui.c:832:34: warning: format not a string literal and no format arguments [-Wformat-security]
opgui.c: In function 'HexSave':
opgui.c:1803:4: warning: format not a string literal and no format arguments [-Wformat-security]
opgui.c: In function 'main':
opgui.c:1943:3: warning: format not a string literal and no format arguments [-Wformat-security]
opgui.c:1961:3: warning: format not a string literal and no format arguments [-Wformat-security]
opgui.c:2512:3: warning: format not a string literal and no format arguments [-Wformat-security]
opgui.c: In function 'MsgBox':
opgui.c:2535:34: warning: format not a string literal and no format arguments [-Wformat-security]
gcc -Wall -Os -s
pkg-config --libs --cflags gtk+-2.0
-c deviceRW.cgcc -Wall -Os -s
pkg-config --libs --cflags gtk+-2.0
-c progP12.cgcc -Wall -Os -s
pkg-config --libs --cflags gtk+-2.0
-c progP16.cprogP16.c: In function 'PIC16_ID':
progP16.c:223:4: warning: format not a string literal and no format arguments [-Wformat-security]
gcc -Wall -Os -s
pkg-config --libs --cflags gtk+-2.0
-c progP18.cgcc -Wall -Os -s
pkg-config --libs --cflags gtk+-2.0
-c progP24.cgcc -Wall -Os -s
pkg-config --libs --cflags gtk+-2.0
-c progEEPROM.cprogEEPROM.c: In function 'WriteOneWireMem':
progEEPROM.c:1743:3: warning: format not a string literal and no format arguments [-Wformat-security]
gcc -Wall -Os -s
pkg-config --libs --cflags gtk+-2.0
-c progAVR.cgcc -Wall -Os -s
pkg-config --libs --cflags gtk+-2.0
-c fileIO.cfileIO.c: In function 'Load':
fileIO.c:405:7: warning: variable 's' set but not used [-Wunused-but-set-variable]
fileIO.c:404:45: warning: variable 'empty' set but not used [-Wunused-but-set-variable]
gcc -Wall -Os -s
pkg-config --libs --cflags gtk+-2.0
-c I2CSPI.cgcc -Wall -Os -s
pkg-config --libs --cflags gtk+-2.0
-c coff.ccoff.c: In function 'analyzeCOFF':
coff.c:28:7: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
coff.c:32:8: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
coff.c:33:8: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
coff.c:39:8: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
coff.c:44:7: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
coff.c:47:7: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
coff.c:120:9: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
coff.c:134:36: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
coff.c:148:9: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
coff.c:149:9: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
coff.c:150:9: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
coff.c:175:9: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
gcc -Wall -Os -s
pkg-config --libs --cflags gtk+-2.0
-c icd.cgcc -Wall -Os -s
pkg-config --libs --cflags gtk+-2.0
-c strings.cecho "#include <gtk gtk.h="">" > icons.c
gdk-pixbuf-csource --extern --build-list write_icon write.png read_icon read.png \ system_icon sys.png go_icon go.png halt_icon halt.png step_icon step.png \ stepover_icon stepover.png stop_icon stop.png >> icons.c
gcc -Wall -Os -s
pkg-config --libs --cflags gtk+-2.0
-c icons.cgcc -Wall -Os -s opgui.o deviceRW.o progP12.o progP16.o progP18.o progP24.o progEEPROM.o progAVR.o fileIO.o I2CSPI.o coff.o icd.o strings.o icons.o
pkg-config --libs --cflags gtk+-2.0
-o opguiPress any key to continue...
Thank you very much for your large work!
Pic16F626 and 16F84 read and write right.
ATmega8 readed quait right
Btw, i have other problems:
- When i attempt reading AT90S2313 in 28 socket alligned pin1
"(Programmer detected on /dev/usb/hiddev0
Firmware version 0.9.0
Hardware ID: 0.0.1 (18F2550)
Synchronization error"
one have Bootloader saved...
On Windows under PICPGM in some socket it readed right.
Warnings are normal.
90S2313 may have serial read disabled.
Also make sure GND is at GND.
18F458 should work; send a log, please.
View and moderate all "Open Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I've the same issue. Tried on Mint 13 (ubuntu 12.04).
opgui 0.9.1, exit with "buffer overflow" after some time in I/O testing mode.
And, cannot recognize an ATMEGA644P , give as result
ID 00000
And unknow device, then it read the correct lengt of data, but haven't verified if the data are correct.
The same hardware configuration works well with opgui 0.9.0
How can i log the opgui operations?
View and moderate all "Open Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Under Options, enable log file.
The log file is cleared before read or write.
View and moderate all "Open Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
After some testing i can confirm that opgui 0.9.1 cannot read / Identify an ATMEGA328.
As for the ATMEGA644, it report ID 00000, and readed data arent correct.
OPGUI0.9.0 works well
What oscillator type are you using (before writing)?
View and moderate all "Open Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
mmm Don't understand your question. For the ATMEGA i use no XTAL. For the programmer i use 12Mhz xtal.
I mean, before programming what is the oscillator configuration in the ATMEGA?
View and moderate all "Open Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
OK. It was setting as from the factory. (I suppose 1Mhz internal)
I've another parallel programmer to test, so, if you want i can test whit any fuses configuration you want.
Just to remember you, opgui 0.9.0 work well.
View and moderate all "Open Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Can you save a log of your write attempt?
0.9.1 has an adaptive entry algorithm.