Skip to main content ↑ ↓

Messages

This section allows you to view all Messages made by this member. Note that you can only see Messages made in areas you currently have access to.

Messages - jamz

31
USB Infrared Toy / Re: IRToyRecPlay v0.7 question
adding -q to the command parameter expects a file that contains filenames of those bin files. The error was likely caused by reading a binary file instead of a text file, because binary files contains unprintable characters which gives unpredictable results even in a console display.

we'll update the irtoy rec and play to include that functionality of single file replay in the next release.

Thanks for the input.
32
USB Infrared Toy / Re: IRToyRecPlay v0.7 question
the app will add the _000.bin, so you don't need to specify the fullname, a parameter -f tester will be ok.
it will play all files found in that directory beginning with 'tester'

I know there was a feature to play a single file by using  a  -q in the parameter, this was done by somebody in the forum, but I haven't tested it yet.

you need to create a textfile example: myqueuefile.txt

myqueuefile.txt may contain 1 bin file per line.
tester_000.bin
tester_010.bin

then call it with irtoy -d com8 -f myqueuefile.txt  -q  -v
Hope that works.
33
CPLD programmable logic / Re: Programming XC2C64A board with linux
[quote author="Georg"]

Ian, maybe you can check if it still works with Windows and put it to the release.
[/quote]

The source file compiles without a problem in windows 7 under codeblocks 10.05 IDE . It compiles also under my debian 5, using codeblocks for debian too, and we can safely ignore the unused param_bytechunks variable.

I Posted it back to svn.

thanks Georg!
35
Bus Blaster JTAG debugger / Re: Compiling urjtag on windows
I have put the compilation process on the wiki.

http://dangerousprototypes.com/docs/Com ... ther_files

It is more complete and has ready to run project files.

I am not sure if we violate some terms because I put a modified copy on the DP svn:
http://dangerous-prototypes-open-hardwa ... g4Windows/

I did not apply the patches for this build but I don't see a problem why it should not compile.

I am not sure if those compilation warnings can affect the exe file.
36
Bus Blaster JTAG debugger / Re: Compiling urjtag on windows
Hello all

I have successfully compiled urjtag build 1872 under codeblocks last week but didn't document it well and I got lost reproducing the same procedure, but now it compiled again. Its almost the same in compiling the released version of urjtag-10, with modified directories.

jtag has 0 errors and 202 warnings while  bsdl2jtag has 0 errors and 200 warnings and I do not yet know it those warnings can be safely ignored. 
I haven't touch the source to fix the warnings, except for the config.h and sysdep.h

You need to place the urjtag files in c:urjtag to succesfully compile. I've attached the project  jtag.cbp  file in codeblocks which should be place  in the C:urjtagsrcappsjtag, and the bsdl2jtag.cbp in C:urjtagsrcappsbsdl2jtag directory. Using this project file along with the config.h and sysdep.h will bypass the procedure of calling the ./configure command under cygwin or linux. The ./configure produces these files.

what I did:
I grab the urjtag files from the latest svn repository at urjtag.  Note that is build 1872.
And since the source  doesn't have the config.h, i need run configure under cygwin  to produce this file.

I created a jtag.cbp project file under codeblocks and rename jtag.c into main.c. I should use the original jtag.c file but codeblocks keep on complaing  with the "_MAIN16" not define thing.
then I have gone through the cycle of:
compile
add search path
compile again
remove some unneeded files from tap and cable directory
compile again
modify config.h or sysdep.h accordingly. ( remarks or #undef some lines that gets in the way)
and repeat same procedure from the start again until it has successfully produced an exe file.

Here's the codeblocks project file configuration for jtag.cbp

project->project build options->search directories: (both debug and release)

c:urjtag
c:urjtaginclude
c:urjtagincludeurjtag
c:urjtagsrcbsdl
c:urjtagsrclib
c:urjtagsrctag
c:CDM20808
c:Program files(x86)CodeblocksMingGWincludeDDK    -> this is for usb.h. remove (x86) if using  winxp. be sure to check for the existence of this file.

at project->project build options->linker settings:

C:CDM20808i386ftd2xx.lib

and removed the following files from project: (right click workspace and remove file or directory).

ice100
jlink
vslink
xpc
ts7800
vision_ep9307
parport
libftdi
parport directory

The bsdl2jtag.cbp is just a copy of jtag.cbp including the .layout file.  I move it in the bsdl2jtag directory and under codeblocks, right click bsdl2jtag project file, under properties, rename the title and in the build targets tabs, changes the output filename to bsdl2jag.exe.

You can bypass the procedure of running the ./configure command under cygwin or linux by using the attached files, by placing each file in the appropriate directories under c:urjtag  and when in codeblocks, just load jtag.cbp from the src/apps/jtag  and compile, switch and then load bsdl2jtag from src/apps/bsdl2jat and compile.  that's all.
37
Bus Blaster JTAG debugger / Re: Compiling urjtag on windows
Thanks Tjtag

I am not yet successful in compiling the latest svn source. The some files in the svn is missing while it exist in the distribution, like the bsdl_config.h and the svf_bison.h and there are lots of compiler warnings and errors. although the latest svn was already updated and compile well in linux and cygwin, using the cross compiler in cygwin gives me problem, while the linux hosted cross compiler works well.

Here's just some additional notes that should keep in mind when compiling urjtag under windows and codeblocks:

For some reason, I still need to put on the search path for the usb.h which can be found under mingw ddk directory. Maybe its because mingw hate directory names with spaces. (like c:program files)
and sometimes  you need to edit long lines that span more than a line in codeblocks if you copy files from cygwin or linux into a windows directory. It always gives me an error regarding a missing ')' when that line looks valid to me.

I have remarked the #define HAVE_LIBUSB but it keeps on compiling libusb.c and libusb.h even though I remove it from the projects.

Also codeblocks can only create one exe file at a time ( I don't dig enough to find some configuration) but I will just create two project files (jtag.cbp and bsdl2jag.cbp).
39
Bus Blaster JTAG debugger / Re: Compiling urjtag on windows
Hello All,

UrJtag-0.10 compiles successfully under native windows (win7) and CodeBlocks 10.05.

This took me so long before I was able to compile urjtag under codeblocks. But Ian was so kind not to give me some task so that I can focus on this. After reading a lot of materials  on the web, I was so surprise that its relatively easy to compile Urjtag under native windows, using only codeblocks with its default Mingw compiler, plus the ftd2xx source.

I decided to concentrate on the latest stable version (0.10, build 1502) since the svn version still gives me troubles (different directories, 2 exe files need to do plus the patches. but I hope to get around that too.)

Despite 34 warnings (see log) , An exe file was created and was running under windows console.
The zip file along with the codeblocks project file is in the svn repository http://code.google.com/p/dangerous-prot ... tail?r=656
 
The .cbp file should compile if you installed urjtag source in c:urjtag-0.10
There were only 3 files that were modified:  config.h, quit.c and safe-ctype.h.

Here are the steps to replicate compilation of urjtag-0.10 build 1502

1. Download urjtag 0.10 from http://sourceforge.net/projects/urjtag/files/ and uncompress to a directory (say c:urjtag-0.10)
2. you need to find a way to run ./configure because we need to create a config.h file. I used cygwin to do this. And I have a copy from my cygwin directory. Its best to just copy the full urjtag-0.10 after running the configure command under cygwin. But once you have the generated config.h, you do not need cygwin anymore.
 
3 Create a C console codeblocks project, (my codeblocks is a fresh install around 73mb)
save the .cbp  and .layout files  and exit.
4. Move the .cbp and .layout files under the src directory where the jtag.c resides. You can copy over jtag.c into main.c
5. open up the .cbp under codeblocks. Right click the project file (urjtag-0.10) and click on "add files recursively" It will check some files that need to be added to the project (default) (.c and .h)

6. Add to codeblocks search directories: 
(project->project build options->search directories->compiler tab)
c:urjag-0.10
c:urjag-0.10include
C:urjtag-0.10srclib
c:CDM20909


7. Modify/add to config.h
#define JTAG_DATA_DIR "DATA"

Disable readline from config.h (REMarked) depends how you run ./configure parameters
this might be disabled already in the file.
// #define HAVE_LIBREADLINE 1
// #define ENABLE_NLS 1
// #define HAVE_LIBUSB 1
// #define HAVE_READLINE_COMPLETION 1
// #undef HAVE_READLINE_H */
// #define HAVE_READLINE_HISTORY 1
// #define HAVE_READLINE_HISTORY_H 1
// #define HAVE_READLINE_READLINE_H 1

8. Remove from project file (  right click file in project dir, remove file).
This cause some errors, but I believe we do not need this things unless you use them.
srcjtag.c if still in the project file.
tapusbconnlibftdi
tapcablets7800.c 
tapcablevision_ep9307.c
tapcablejlink.c
tapcablexpc.c


9. Add #define "config.h" to the following files
cmd/quit.c
lib/safe-ctype.c

10. Add the ftd2xxlib to project build option->linker tab add under link libraries: (use the '...' to locate your ftd2xx library):
C:CDM20808i386ftd2xx.lib

Code: [Select]
Build started on: 04-02-2011 at 02:19.20
Build ended on: 04-02-2011 at 02:20.02
-------------- Build: Release in urjtag10 ---------------
Compiling: bsdlbsdl.c
Compiling: bsdlbsdl_bison.c
Compiling: bsdlbsdl_flex.c
bsdl_flex.c:2533: warning: 'yyunput' defined but not used
bsdl_flex.c:2575: warning: 'input' defined but not used
Compiling: bsdlbsdl_sem.c
C:urjtag-0.10srcbsdlbsdl_sem.c: In function 'create_register':
C:urjtag-0.10srcbsdlbsdl_sem.c:209: warning: unknown conversion type character 'z' in format
C:urjtag-0.10srcbsdlbsdl_sem.c:209: warning: too many arguments for format
Compiling: bsdlvhdl_bison.c
Compiling: bsdlvhdl_flex.c
vhdl_flex.c:2024: warning: 'yyunput' defined but not used
vhdl_flex.c:2066: warning: 'input' defined but not used
Compiling: busau1500.c
Compiling: busavr32.c
C:urjtag-0.10srcbusavr32.c: In function 'avr32_bus_read_end':
C:urjtag-0.10srcbusavr32.c:680: warning: 'data' may be used uninitialized in this function
Compiling: busbcm1250.c
Compiling: busbf533_ezkit.c
Compiling: busbf533_stamp.c
Compiling: busbf537_stamp.c
C:urjtag-0.10srcbusbf537_stamp.c:69: warning: 'bf537_stamp_bus_new' defined but not used
C:urjtag-0.10srcbusbf537_stamp.c:136: warning: 'bf537_stamp_bus_area' defined but not used
C:urjtag-0.10srcbusbf537_stamp.c:220: warning: 'bf537_stamp_bus_read_start' defined but not used
C:urjtag-0.10srcbusbf537_stamp.c:240: warning: 'bf537_stamp_bus_read_next' defined but not used
C:urjtag-0.10srcbusbf537_stamp.c:261: warning: 'bf537_stamp_bus_read_end' defined but not used
C:urjtag-0.10srcbusbf537_stamp.c:285: warning: 'bf537_stamp_bus_write' defined but not used
C:urjtag-0.10srcbusbf537_stamp.c:310: warning: 'bf537_stamp_bus_printinfo' defined but not used
Compiling: busbf548_ezkit.c
Compiling: busbf561_ezkit.c
Compiling: busbscoach.c
Compiling: busbuses.c
Compiling: busejtag.c
Compiling: busejtag_dma.c
Compiling: busfjmem.c
Compiling: busgeneric_bus.c
Compiling: bush7202.c
Compiling: busixp425.c
Compiling: busjopcyc.c
Compiling: buslh7a400.c
Compiling: busmpc5200.c
Compiling: busmpc824x.c
Compiling: busppc405ep.c
Compiling: busppc440gx_ebc8.c
Compiling: busprototype.c
Compiling: buspxa2x0.c
Compiling: busreadmem.c
Compiling: buss3c4510x.c
Compiling: bussa1110.c
Compiling: bussh7727.c
Compiling: bussh7750r.c
Compiling: bussh7751r.c
Compiling: bussharc21065l.c
Compiling: busslsup3.c
Compiling: bustx4925.c
Compiling: buswritemem.c
Compiling: buszefant-xs3.c
Compiling: cmdaddpart.c
Compiling: cmdbit.c
Compiling: cmdbsdl.c
Compiling: cmdbus.c
Compiling: cmdcable.c
Compiling: cmdcmd.c
Compiling: cmddebug.c
Compiling: cmddetect.c
Compiling: cmddetectflash.c
Compiling: cmddiscovery.c
Compiling: cmddr.c
Compiling: cmdendian.c
Compiling: cmderaseflash.c
Compiling: cmdflashmem.c
Compiling: cmdfrequency.c
Compiling: cmdget.c
Compiling: cmdhelp.c
Compiling: cmdidcode.c
Compiling: cmdinclude.c
Compiling: cmdinitbus.c
Compiling: cmdinstruction.c
Compiling: cmdjtag_data_dir.c
Compiling: cmdparse.c
Compiling: cmdpart.c
Compiling: cmdpeekpoke.c
Compiling: cmdpod.c
Compiling: cmdprint.c
Compiling: cmdquit.c
Compiling: cmdreadmem.c
Compiling: cmdregister.c
Compiling: cmdreset.c
Compiling: cmdsalias.c
Compiling: cmdscan.c
Compiling: cmdset.c
Compiling: cmdshell.c
Compiling: cmdshift.c
Compiling: cmdsignal.c
Compiling: cmdsvf.c
Compiling: cmdtest.c
Compiling: cmdusleep.c
Compiling: cmdwritemem.c
Compiling: flashamd.c
Compiling: flashamd_flash.c
Compiling: flashcfi.c
Compiling: flashdetectflash.c
Compiling: flashflash.c
Compiling: flashintel.c
Compiling: flashjedec.c
Compiling: flashjedec_exp.c
Compiling: jimintel_28f800b3.c
Compiling: jimsome_cpu.c
Compiling: jimtap.c
C:urjtag-0.10srcjimtap.c: In function 'jim_init':
C:urjtag-0.10srcjimtap.c:267: warning: unknown conversion type character 'z' in format
C:urjtag-0.10srcjimtap.c:267: warning: too many arguments for format
Compiling: libfclock.c
Compiling: libgetdelim.c
Compiling: libgetline.c
Compiling: liblbasename.c
Compiling: liblrealpath.c
Compiling: libmake-relative-prefix.c
C:urjtag-0.10srclibmake-relative-prefix.c: In function 'save_string':
C:urjtag-0.10srclibmake-relative-prefix.c:105: warning: implicit declaration of function 'malloc'
C:urjtag-0.10srclibmake-relative-prefix.c:105: warning: incompatible implicit declaration of built-in function 'malloc'
C:urjtag-0.10srclibmake-relative-prefix.c: In function 'split_directories':
C:urjtag-0.10srclibmake-relative-prefix.c:143: warning: incompatible implicit declaration of built-in function 'malloc'
C:urjtag-0.10srclibmake-relative-prefix.c:156: warning: implicit declaration of function 'free'
C:urjtag-0.10srclibmake-relative-prefix.c:156: warning: incompatible implicit declaration of built-in function 'free'
C:urjtag-0.10srclibmake-relative-prefix.c: In function 'free_split_directories':
C:urjtag-0.10srclibmake-relative-prefix.c:207: warning: incompatible implicit declaration of built-in function 'free'
C:urjtag-0.10srclibmake-relative-prefix.c: In function 'make_relative_prefix_1':
C:urjtag-0.10srclibmake-relative-prefix.c:242: warning: implicit declaration of function 'getenv'
C:urjtag-0.10srclibmake-relative-prefix.c:242: warning: assignment makes pointer from integer without a cast
C:urjtag-0.10srclibmake-relative-prefix.c:275: warning: implicit declaration of function 'access'
C:urjtag-0.10srclibmake-relative-prefix.c:305: warning: incompatible implicit declaration of built-in function 'free'
C:urjtag-0.10srclibmake-relative-prefix.c:358: warning: incompatible implicit declaration of built-in function 'malloc'
Compiling: libsafe-ctype.c
Compiling: main.c
Compiling: partbsbit.c
Compiling: partdata_register.c
Compiling: partinstruction.c
Compiling: partpart.c
Compiling: partsignal.c
Compiling: svfsvf.c
C:urjtag-0.10srcsvfsvf.c:609: warning: 'sigalrm_handler' defined but not used
Compiling: svfsvf_bison.c
Compiling: svfsvf_flex.c
svf_flex.c:1343: warning: 'yyunput' defined but not used
svf_flex.c:1385: warning: 'input' defined but not used
Compiling: tapcable.c
Compiling: tapcablearcom.c
Compiling: tapcablebyteblaster.c
Compiling: tapcablecmd_xfer.c
Compiling: tapcabledlc5.c
Compiling: tapcableea253.c
Compiling: tapcableei012.c
Compiling: tapcableft2232.c
Compiling: tapcablegeneric.c
C:urjtag-0.10srctapcablegeneric.c: In function 'generic_set_frequency':
C:urjtag-0.10srctapcablegeneric.c:400: warning: unknown conversion type character 'L' in format
C:urjtag-0.10srctapcablegeneric.c:400: warning: format '%u' expects type 'unsigned int', but argument 2 has type 'long double'
C:urjtag-0.10srctapcablegeneric.c:400: warning: too many arguments for format
Compiling: tapcablegeneric_parport.c
Compiling: tapcablegeneric_usbconn.c
Compiling: tapcablejim.c
C:urjtag-0.10srctapcablejim.c:169: warning: initialization from incompatible pointer type
C:urjtag-0.10srctapcablejim.c:170: warning: initialization from incompatible pointer type
Compiling: tapcablekeithkoep.c
Compiling: tapcablelattice.c
Compiling: tapcablempcbdm.c
Compiling: tapcabletriton.c
Compiling: tapcableusbblaster.c
Compiling: tapcablewiggler.c
Compiling: tapcablewiggler2.c
Compiling: tapchain.c
Compiling: tapdetect.c
Compiling: tapdiscovery.c
Compiling: tapidcode.c
Compiling: tapparport.c
Compiling: tapparportdirect.c
Compiling: tapparportppdev.c
Compiling: tapparportppi.c
Compiling: tapregister.c
Compiling: tapstate.c
Compiling: taptap.c
Compiling: tapusbconn.c
Compiling: tapusbconnlibftd2xx.c
Compiling: tapusbconnlibusb.c
Linking console executable: binReleaseurjtag10.exe
Output size is 356.50 KB
Process terminated with status 0 (0 minutes, 42 seconds)
0 errors, 35 warnings

Next task will be  to compile under codeblocks the latest svn version including the  patches into native windows environment.

Jamz
40
USB Infrared Toy / Re: Newbe question, sending pronto codes.
Hi Roland,

thank you for trying the latest rec & play app.

You have the latest firmware already, and the apps has worked too, but fails sometimes.
I think its best to isolate problems: You can try it in another pc, and remove all the connected usb and com devices except for the irtoy. There could be an app or driver that might be interfering with your com or usb ports. An anti-virus or firewall can be a culprit.


I am also using win7 64 bit, but I run this app under an admin account.
42
USB Infrared Toy / Re: Newbe question, sending pronto codes.
There's a new update for the IRtoy. It now display the current firmware used. The protocol version checking is now a little bit relaxed. Although it will attempt to reset the irtoy 10x for a failed protocol version reading, it will simply ignore the extra garbage as long as it can read the 'S01' string.

It was also updated for the linux version for some patches as suggested by forum members, but still the screen display was not good like the windows version. The firmware version sometimes does not display well in the 'release' build but it does in the 'debug' version.
43
USB Infrared Toy / Re: Record and playback under Linux
I have updated the IRtoy rec & play app and its now include a  firmware check on v0.7  and have included some patches as suggested (Thanks atluxity).  But this app screen display is a not  nicely formatted just like the windows compile, but it still works.  And I do not know the difference between an ubuntu compiled version and debian and other flavors of linux.

Also I have notice that the firmware version does not display properly in the 'release' build but it does in the 'debug' build.

Thanks for the suggestion everyone!
44
USB Infrared Toy / Re: Re: Newbe question, sending pronto codes.
V109 is the same as mine. and looks like the hardware is ok. I am out of suggestion for now. I am still wondering why v.05 works and v.06 doesn't.

The problem was that the Irtoy did'nt get the IR protocol version response,which is 'S 0 1', after repeated sending of 'S' command, so it exited. It expects a 3 byte return but it looks like its returning more bytes than expected so it keeps on trying to get a 'cleaner' response.  Version v.05 is a bit more relax, it grabs any response, including the garbage, then proceed.

I am sure Ian and other experts will give more suggestions, but for now v05 works for you, the rec and play functionality of the app is the same as with the latest version, except that the latest  has the ability to change the default resolution (default is 21.333).

Please keep watching this post. I am sure you will got a reply in a few hours.

Jamz

( ! ) Fatal error: Uncaught exception 'Elk_Exception' with message 'Please try again. If you come back to this error screen, report the error to an administrator.' in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
( ! ) Elk_Exception: Please try again. If you come back to this error screen, report the error to an administrator. in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
Call Stack
#TimeMemoryFunctionLocation
10.01642481248session_write_close ( )...(null):0
20.01672612864ElkArte\sources\subs\SessionHandler\DatabaseHandler->write( )...(null):0
30.01672613640Database_MySQL->query( ).../DatabaseHandler.php:119
40.06222752400Database_MySQL->error( ).../Db-mysql.class.php:273