From: Jan Panteltje on
On a sunny day (Thu, 10 Jun 2010 07:39:58 +1000) it happened Grant
<omg(a)grrr.id.au> wrote in <5s10165g88l18dhge1o1k3d3soq3kvrtgf(a)4ax.com>:

>I've just started using PICs, programmed enough (RTC, HD44780 LCD module
>controller, multitasking timebase) to know they're okay for what I want.
>I return to microcontrollers for first time since '93 when PICs were becoming
>popular but I was using 'HC05 series controllers (C8, J2, K1). So I've
>seen the RISC and can get the assembler to put multi-module code where I
>expect it now.
>
>Yet to do user input, I'm more interested in standalone operation than
>serial interface, so not done rs232 or inter-chip comms yet.
>
>So many things I'd like to try :) Even bought a 192x128 LCD graphics
>display to try driving one day -- the sort without a char gen, so I'd
>have to work in a char pattern memory for text on that too. Done that
>back in '80s with little 8085 box, in assembler.
>
>Grant.

There are a few PIC project on my site:
http://panteltje.com/panteltje/pic/
All of the features you mention are covered there, all asm.

I could not write the soft without the serial interface.
It is the first thing I always get working, plus some routines
to print 8 bits, 16 bits and sometimes 32 bits numbers as ASCII to the RS232.
So I can debug my programs, see what is happening.
Also I always add test commands, for example 'b' to print a buffer, things like that.

When starting a new project that basic code is cut and paste, including the chip initialisation.
Speeds up thing a thousand times.
The scope_pic project has my own character generator in it:
http://panteltje.com/panteltje/pic/

From: John Larkin on
On Wed, 09 Jun 2010 14:18:42 GMT, Jan Panteltje
<pNaonStpealmtje(a)yahoo.com> wrote:

>A multi processor PIC computer :-)
> ftp://panteltje.com/pub/multi_processor_PIC_LED_color_controller_hardware_img_2002.jpg
>
>I modified my LED color controller a bit so it has 3 independent hardware PWM channels.
>One PIC is the master, is controlled via ethernet, and its PWM unit drives blue.
>It forwards the other color levels via very fast RS232 to 2 other PICs,
>one does the red pwm, and the other one does the green PM thing.
>
>There are 4 clocks in this system, 25 MHz for the ethernet controller,
>and 3 x 64 MHz internal clocks for the PICs.
>
>I was watching the LED strips for interference, you can see it on the scope,
>but not in the light output....
>PWM is about 15 kHz, 8 bits resolution, probably with harmonics up to......
>Anyways, multi-processor PIC is here :-)
>

We just got the first bare board of a VME module that has 13 ARM
processors on it, one per i/o channel and one overall manager. The
channels are electrically isolated, so we couldn't use a
multi-processor chip or a single higher-power uP. An ARM with flash,
mux'd ADC, DAC, parallel ports, SPI, timers UARTS... is a lot of stuff
for $4. We're throwing away the Ethernet port!

Multiple CPUs on a chip will be common in all systems some day soon,
embedded included. We don't need no stinkin' RTOS... just run
bare-metal code on each CPU.

John

From: krw on
On Wed, 09 Jun 2010 18:28:43 -0700, John Larkin
<jjlarkin(a)highNOTlandTHIStechnologyPART.com> wrote:

>On Wed, 09 Jun 2010 14:18:42 GMT, Jan Panteltje
><pNaonStpealmtje(a)yahoo.com> wrote:
>
>>A multi processor PIC computer :-)
>> ftp://panteltje.com/pub/multi_processor_PIC_LED_color_controller_hardware_img_2002.jpg
>>
>>I modified my LED color controller a bit so it has 3 independent hardware PWM channels.
>>One PIC is the master, is controlled via ethernet, and its PWM unit drives blue.
>>It forwards the other color levels via very fast RS232 to 2 other PICs,
>>one does the red pwm, and the other one does the green PM thing.
>>
>>There are 4 clocks in this system, 25 MHz for the ethernet controller,
>>and 3 x 64 MHz internal clocks for the PICs.
>>
>>I was watching the LED strips for interference, you can see it on the scope,
>>but not in the light output....
>>PWM is about 15 kHz, 8 bits resolution, probably with harmonics up to......
>>Anyways, multi-processor PIC is here :-)
>>
>
>We just got the first bare board of a VME module that has 13 ARM
>processors on it, one per i/o channel and one overall manager. The
>channels are electrically isolated, so we couldn't use a
>multi-processor chip or a single higher-power uP. An ARM with flash,
>mux'd ADC, DAC, parallel ports, SPI, timers UARTS... is a lot of stuff
>for $4. We're throwing away the Ethernet port!

Use the Ethernet port for your interprocessor communications. Using its
transformer coupling, all the real work is done.

>Multiple CPUs on a chip will be common in all systems some day soon,
>embedded included. We don't need no stinkin' RTOS... just run
>bare-metal code on each CPU.

I/O is the problem.
From: Spehro Pefhany on
On Wed, 09 Jun 2010 22:30:56 -0500, the renowned
"krw(a)att.bizzzzzzzzzzzz" <krw(a)att.bizzzzzzzzzzzz> wrote:

>On Wed, 09 Jun 2010 18:28:43 -0700, John Larkin
><jjlarkin(a)highNOTlandTHIStechnologyPART.com> wrote:
>
>>On Wed, 09 Jun 2010 14:18:42 GMT, Jan Panteltje
>><pNaonStpealmtje(a)yahoo.com> wrote:
>>
>>>A multi processor PIC computer :-)
>>> ftp://panteltje.com/pub/multi_processor_PIC_LED_color_controller_hardware_img_2002.jpg
>>>
>>>I modified my LED color controller a bit so it has 3 independent hardware PWM channels.
>>>One PIC is the master, is controlled via ethernet, and its PWM unit drives blue.
>>>It forwards the other color levels via very fast RS232 to 2 other PICs,
>>>one does the red pwm, and the other one does the green PM thing.
>>>
>>>There are 4 clocks in this system, 25 MHz for the ethernet controller,
>>>and 3 x 64 MHz internal clocks for the PICs.
>>>
>>>I was watching the LED strips for interference, you can see it on the scope,
>>>but not in the light output....
>>>PWM is about 15 kHz, 8 bits resolution, probably with harmonics up to......
>>>Anyways, multi-processor PIC is here :-)
>>>
>>
>>We just got the first bare board of a VME module that has 13 ARM
>>processors on it, one per i/o channel and one overall manager. The
>>channels are electrically isolated, so we couldn't use a
>>multi-processor chip or a single higher-power uP. An ARM with flash,
>>mux'd ADC, DAC, parallel ports, SPI, timers UARTS... is a lot of stuff
>>for $4. We're throwing away the Ethernet port!
>
>Use the Ethernet port for your interprocessor communications. Using its
>transformer coupling, all the real work is done.

Well, unless you need to guarantee tight timing, in which case the
real work may be just beginning.


Best regards,
Spehro Pefhany
--
"it's the network..." "The Journey is the reward"
speff(a)interlog.com Info for manufacturers: http://www.trexon.com
Embedded software/hardware/analog Info for designers: http://www.speff.com
From: krw on
On Wed, 09 Jun 2010 23:36:45 -0400, Spehro Pefhany
<speffSNIP(a)interlogDOTyou.knowwhat> wrote:

>On Wed, 09 Jun 2010 22:30:56 -0500, the renowned
>"krw(a)att.bizzzzzzzzzzzz" <krw(a)att.bizzzzzzzzzzzz> wrote:
>
>>On Wed, 09 Jun 2010 18:28:43 -0700, John Larkin
>><jjlarkin(a)highNOTlandTHIStechnologyPART.com> wrote:
>>
>>>On Wed, 09 Jun 2010 14:18:42 GMT, Jan Panteltje
>>><pNaonStpealmtje(a)yahoo.com> wrote:
>>>
>>>>A multi processor PIC computer :-)
>>>> ftp://panteltje.com/pub/multi_processor_PIC_LED_color_controller_hardware_img_2002.jpg
>>>>
>>>>I modified my LED color controller a bit so it has 3 independent hardware PWM channels.
>>>>One PIC is the master, is controlled via ethernet, and its PWM unit drives blue.
>>>>It forwards the other color levels via very fast RS232 to 2 other PICs,
>>>>one does the red pwm, and the other one does the green PM thing.
>>>>
>>>>There are 4 clocks in this system, 25 MHz for the ethernet controller,
>>>>and 3 x 64 MHz internal clocks for the PICs.
>>>>
>>>>I was watching the LED strips for interference, you can see it on the scope,
>>>>but not in the light output....
>>>>PWM is about 15 kHz, 8 bits resolution, probably with harmonics up to......
>>>>Anyways, multi-processor PIC is here :-)
>>>>
>>>
>>>We just got the first bare board of a VME module that has 13 ARM
>>>processors on it, one per i/o channel and one overall manager. The
>>>channels are electrically isolated, so we couldn't use a
>>>multi-processor chip or a single higher-power uP. An ARM with flash,
>>>mux'd ADC, DAC, parallel ports, SPI, timers UARTS... is a lot of stuff
>>>for $4. We're throwing away the Ethernet port!
>>
>>Use the Ethernet port for your interprocessor communications. Using its
>>transformer coupling, all the real work is done.
>
>Well, unless you need to guarantee tight timing, in which case the
>real work may be just beginning.

I thought we were just interfacing between multiple processors. ...and John
doesn't like RTOSs, so...
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5 6
Prev: re Goodbye to an era
Next: RF cable connection to board