Comments for ElectricRock Blog

Comment on Updated C30 build script for Ubuntu 10.04 by AMX

AMX — Tue, 12 Apr 2011 16:30:57 +0000

Works here, there were a few 0xff in the file (c-parse.y), I removed them by hand and also ran dos2unix (for safety).
Thanks ilPincy! I think I have a working pic24/30 toolchain by now.

Comment on Updated C30 build script for C30 v3.23b by Ralf Mayet

Ralf Mayet — Tue, 12 Apr 2011 13:19:16 +0000

Hi v66r,

regarding the overflow issue: I have fixed it by compiling all of the pic30-* files using gcc-3.4, not 4.1. Now it seems to work!

Cheers

Comment on New C30 page, now with automated goodness by AMX

AMX — Sun, 10 Apr 2011 16:19:00 +0000

Okay, I found a solution:

in “acme/bfd/targets.c” I removed the “#ifndef”:
//#ifndef PIC30
/* Always support S-records, for convenience. */
&srec_vec,
&symbolsrec_vec,
/* And tekhex */
&tekhex_vec,
/* Likewise for binary output. */
&binary_vec,
/* Likewise for ihex. */
&ihex_vec,
//#endif

Comment on New C30 page, now with automated goodness by AMX

AMX — Sun, 10 Apr 2011 14:09:27 +0000

Hi, I build the 3.23 binutils following your instructions and had to modify the resource.c and cpu-pic30.c in order to get rid of some segfault. Anyway, my version doesn’t seem to know ihex format. Does the pic30-coff target not support ihex?
Otherwise I seem to get valid output, I checked it with “pic30-coff-objdump -D”.

Comment on Building Microchip’s C30 Compiler v3.20 on Ubuntu 9.10 by matt

matt — Wed, 16 Mar 2011 18:43:11 +0000

It’s been a while since I last built/used C30. I think if the c30_device.info isn’t in the $C30INSTALL/info directory, then it might be in the $C30INSTALL/bin directory. If that doesn’t work it may be because microchip removed it from the source package (I’m not sure about this though), but if this is the case you may need to install the windows version of the compiler (e.g., wine if possible) and copy the file from there.

If that doesn’t help let me know, and I’ll look into it further.

Cheers,
Matt

Comment on Building Microchip’s C30 Compiler v3.20 on Ubuntu 9.10 by William

William — Wed, 16 Mar 2011 08:32:02 +0000

Thanks for this tutorial, it is great.

just a troubleshot though, I can compile a test file on the command line without any options. but when I compile a project in piklab for a specific processor I’ve got the error you mentioned in the next step tutorial and tried to solved it as you said:

“pic30-coff-cc1: warning: Provide a resource file
pic30-coff-cc1: error: Invalid -mcpu option. CPU 30F4013 not recognized.
To solve this add -mresource=$C30INSTALL/info/c30_device.info to your GCC command line”

Well my problem is that I do not have this file in this directory, I just have:
cpp.info
cppinternals.info
dir
dir.old

could you tell me where to get this file or alternatively could you give it to me

many thanks,

William

PS: I had to ln -s the files to /usr/bin/ directory to make it visible for piklab.

Comment on Ensoniq Control 16 Undressed by matt

matt — Sat, 05 Mar 2011 10:34:53 +0000

Hey, What tool are you using for sniffing? The communication between the EDS card and the console is RS-422 (so basically a ±5v differential pair in each direction). First you need to work out the baudrate and packet format (one would assume 8N1 as this is typical for serial ports), if you have a scope that would make this a lot easier. Once you have that information, the best thing to do would be to sniff the packets going in both directions simultaneously so that you can record what the EDS card sends to the console while at the same time recording what the console sends back to the card. If you want, I can draw up a schematic for a sniffer that would do this. Cheers

Comment on Ensoniq Control 16 Undressed by mattcelt

mattcelt — Fri, 04 Mar 2011 06:47:19 +0000

Hey Matt, I’m still working on it. I have the EDS cards for the console… what data could I sniff from the wire that would help you get more information? I’m afraid to plug the cable into a sniffer with that 12v connection lurking in there – I just don’t know enough about serial protocols to know if that’s within tolerable limits.

Comment on Ensoniq Control 16 Undressed by matt

matt — Wed, 02 Feb 2011 19:59:33 +0000

That sounds cool. I didn’t document the original protocol as I didn’t have the PCI card that the C16 communicates with, so couldn’t just sniff the communications between the two. However, I imagine a wireless bridge could be built relatively easily without knowing the protocol. Since the signaling is RS422, it would simply be a matter of building or buying a bi-directional wireless bridge for RS-422, or repurposing an RS-232 one. Anyway, it sounds like an interest project, and I’d be keen to hear more if you go ahead with it.

Comment on Ensoniq Control 16 Undressed by mattcelt

mattcelt — Wed, 02 Feb 2011 17:32:05 +0000

Hey Matt, great to see someone working on this. I have a PARIS system I’m still actively using, and I’m actually looking to wirelessly-enable my Control 16 and Control 16 Pro, so your work here is invaluable. Have you made any progress documenting the transmit protocol at all, or is that outside the scope of what you’re doing?

Thanks,
mattcelt