Hi Joe,

> Any plans to support the 18x instruction set?  (In particular, the 18C442)
:^)
A new version will be released in the middle of September with a new look
and feel and new devices (slider, serial eeprom, oscillo...). but without
the 18x core :(
The next major steps are for us (3 developers)
1. to develop the complete I2C/SPI core (master and slave) in order to
support the 16F877 and co
2. add logical / analog devices
3. Start the development of the 18x core. For this we need to complete at
least the first step. We do not want to propose an half implementation of a
microcontroller :).
4. C compiler support. Necessary for the 18xx core.

We perform a big release every two months so the 18xx core will be normaly
available at the end of this year :(.
Do not hesitate to contact us if you have any questions / pbs

Regards,
Nicolas




> Any plans to support the 18x instruction set?  (In particular, the 18C442)
:^)
>
> Looks AWESOME, tho.  I will definitely be installing it and using it!
>
> --Joe
>
> On Tue, 24 Aug 2004 21:07:18 +0200, Colombain Nicolas
> <colombain.nicolas@wanadoo.fr> wrote:
> > Hi Robin,
> >
> > As already said by Randy, you can try Microdev which is a free
development
> > environment for PIC. You can connect as many pics as you want together
and
> > for each of them edit, debug their code. This product is still in beta
> > version so .... :)
> > Let me know if you need some support or a new component.
> > Nicolas
> >
> >
> >
> >
> > > You might want to try MicroDev - http://perso.wanadoo.fr/udev/
> > >
> > > I think it supports multiple PICs.
> > >
> > > On Mon, 23 Aug 2004 15:08:16 +0100, robin.bussell@axa-sunlife.co.uk
> > > <robin.bussell@axa-sunlife.co.uk> wrote:
> > > > Hi Folks,
> > > >                 I've managed to break my previously working  bit
banged
> > async
> > > > comms
> > > > code whilst "improving" it (and trying to cram some more tasks
> > > > into the pic ... more of a rewrite really ) .
> > > >
> > > > The project has a pic with an rs232 link to a pc that then puts out
> > commands on
> > > > an rs485 bus to
> > > > other pic nodes and routes back replies to the rs232.
> > > > The rs232 works but now I'm getting no reply back from nodes out on
the
> > 485 bus
> > > > with the new code (still works with the old code)
> > > >
> > > > My development environment is of the cheap "churn and burn" variety,
no
> > ICD but
> > > > at least I have ICSP and a scope (non storage).
> > > >
> > > > I'm sitting here at work (day job, supporting IT in insurance ..
yawn)
> > wondering
> > > > how
> > > > to proceed debugging this tonight, ideally I'd like to simulate the
code
> > to see
> > > > what's going on, otherwise it looks like a long round of putting in
led
> > flashes
> > > > etc to debug
> > > > where the code gets to, or doing a "human pic simulator" act which
is
> > somewhat
> > > > error
> > > > prone in my experience :)
> > > >
> > > > Is there any way I can run two instances of a pic simulator and
> > virtually
> > > > connect
> > > > the tx and rx pins together as stimuli?
> > > >
> > > > Also can anyone recommend a free "turn your pc with soundcard into a
low
> > > > bandwidth
> > > > (dual input) storage scope good enough for looking at slow (9600)
acsync
> > comms"
> > > > type program?
> > > >
> > > > Cheers,
> > > >             Robin.
>

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics