2106 | ADC | ARM7 | Atmel | Bootloader | CAN | CrossStudio | CrossWorks | DDS | ECos | Ethernet | ETM | FIFO | FLASH | FPGA | GCC | GDB | GNU | GNUARM | GPIO | I2C | IAP | IAR | JTAG | Kickstart | LCD | Linux | LPC | LPC-E2294 | LPC2000 | LPC2100 | LPC2104 | Lpc2106 | Lpc210x | LPC2114 | LPC2119 | LPC2124 | LPC2129 | Lpc2138 | LPC213x | LPC21xx | LPC2210 | LPC2212 | LPC2214 | LPC2292 | LPC2294 | LPC2xxx | LPC3128 | MCB2100 | Olimex | Philips | PWM | Rowley | RTC | RTOS | SPI | SSP | UART | UART0 | UART1 | ULINK | USB | Watchdog | Wiggler

Hi, The info for TMS470 actually have been on TI web site for years but they never made the datasheets public, as didn't want to deal with small customers. Now TI changed their mind and the datasheets for the first three members are already on the web. The budgetary pricing for their TMS470R1A256 with 256K Flash 12K RAM is $6.85/1K (and yes I'm biased as the only development board on TI web available is ours :) Best regards Tsvetan --- PCB prototypes for $26 at http://run.to/pcb (http://www.olimex.com/pcb) PCB any volume assembly (http://www.olimex.com/pcb/protoa.html) Development boards for ARM, AVR, PIC, and MSP430 (http://www.olimex.com/dev)

(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

I think this is a very interesting development. I have been asking TI about their ARM CPUs for a couple of years. Since they are willing to sell their parts (although there is nothing available even as samples just yet) I have started a Yahoo group for the TMS430 ARM parts. http://groups.yahoo.com/group/TMS470_ARM/ (this time I remembered to post the link!) To Tsvetanusunov, what TMS430 chip is on your board? Is it the TMS470R1A256? The web site does not actually say and they list both the 256 and the 128 as "related devices". Is this board currently available? The TI site says status is "preview". Will you be selling it directly? $400 is a bit steep for such a simple board, even if it includes a simple JTAG dongle. --- In , "tsvetanusunov" <tusunov@m...> wrote: > > Hi, > > The info for TMS470 actually have been on TI web site for years but > they never made the datasheets public, as didn't want to deal with > small customers. > Now TI changed their mind and the datasheets for the first three > members are already on the web. > The budgetary pricing for their TMS470R1A256 with 256K Flash 12K RAM > is $6.85/1K > > (and yes I'm biased as the only development board on TI web available > is ours :) > > Best regards > Tsvetan > --- > PCB prototypes for $26 at http://run.to/pcb > (http://www.olimex.com/pcb) > PCB any volume assembly (http://www.olimex.com/pcb/protoa.html) > Development boards for ARM, AVR, PIC, and MSP430 > (http://www.olimex.com/dev)

(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

--- In , "Rick Collins" <gnuarm@a...> wrote: > > I think this is a very interesting development. I have been asking TI > about their ARM CPUs for a couple of years. Since they are willing to > sell their parts (although there is nothing available even as samples > just yet) I have started a Yahoo group for the TMS430 ARM parts. > > http://groups.yahoo.com/group/TMS470_ARM/ > > (this time I remembered to post the link!) > > To Tsvetanusunov, what TMS430 chip is on your board? Is it the > TMS470R1A256? The web site does not actually say and they list both > the 256 and the 128 as "related devices". Is this board currently > available? The TI site says status is "preview". Will you be selling > it directly? $400 is a bit steep for such a simple board, even if it > includes a simple JTAG dongle. on board is with TMS470R1A256 the only difference with 128 is that it have more memory so this is why they say board cover the development for both devices. The board is available and TI sells it now in bundle with Segger's J- Link. I can't comment the price, this is TI policy. Segger retial for J- Link only is 400 Euro, so looking at this side the deal looks like bargain ;) This board was designed exclusively for TI and TI only sells it. We are developing our own header, proto and Ethernet boards which will be available around May this year when the TMS470 devices will be available through TI disty channels. Best regards Tsvetan --- PCB prototypes for $26 at http://run.to/pcb (http://www.olimex.com/pcb) PCB any volume assembly (http://www.olimex.com/pcb/protoa.html) Development boards for ARM, AVR, PIC, and MSP430 (http://www.olimex.com/dev)

(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

Boy, I sure seem to be good at making mistakes. Just to make it clear, the group I started is for the TMS470 ARM parts, not the TMS430 part. The link is correct. Sorry... --- In , "tsvetanusunov" <tusunov@m...> wrote: > > --- In , "Rick Collins" <gnuarm@a...> wrote: > > > > I think this is a very interesting development. I have been asking > TI > > about their ARM CPUs for a couple of years. Since they are willing > to > > sell their parts (although there is nothing available even as > samples > > just yet) I have started a Yahoo group for the TMS430 ARM parts. > > > > http://groups.yahoo.com/group/TMS470_ARM/ > > > > (this time I remembered to post the link!) > > > > To Tsvetanusunov, what TMS430 chip is on your board? Is it the > > TMS470R1A256? The web site does not actually say and they list both > > the 256 and the 128 as "related devices". Is this board currently > > available? The TI site says status is "preview". Will you be > selling > > it directly? $400 is a bit steep for such a simple board, even if > it > > includes a simple JTAG dongle. > > on board is with TMS470R1A256 the only difference with 128 is that it > have more memory so this is why they say board cover the development > for both devices. > The board is available and TI sells it now in bundle with Segger's J- > Link. > I can't comment the price, this is TI policy. Segger retial for J- > Link only is 400 Euro, so looking at this side the deal looks like > bargain ;) > This board was designed exclusively for TI and TI only sells it. > We are developing our own header, proto and Ethernet boards which > will be available around May this year when the TMS470 devices will > be available through TI disty channels. > > Best regards > Tsvetan > --- > PCB prototypes for $26 at http://run.to/pcb > (http://www.olimex.com/pcb) > PCB any volume assembly (http://www.olimex.com/pcb/protoa.html) > Development boards for ARM, AVR, PIC, and MSP430 > (http://www.olimex.com/dev)

(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

Hello! I would like to connect several P89LPC932 (x51 core) slaves to single LPC2xxx master. Each slave has unused SPI and UART, which can be used for this communication. One slave is addressed at once. What would be best solution for that? I think SPI is ideal for that. I could use free port pins for slave selects. Is there any other (more scalable) option without external/additional components? How many slaves can I connect to single master to avoid port overloading? Data transfer rate is very low (~100 bytes/s per slave) and distance between master and slaves is <1m. Any further suggestions or tips&tricks? M.

(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

> Data transfer > rate is very low (~100 bytes/s per slave) and distance between master > and slaves is <1m. Unless you have a very large board ( <1m ), using an RS-485 would be the easiest way to get running. Using a scheme like MODBUS is also easy on software. There are many projects on the web using slimmed downed version of MODBUS that you might leverage. hamilton

(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

--- In , "Marko Pavlin (home)" <mp@h...> wrote: > Hello! > > I would like to connect several P89LPC932 (x51 core) slaves to single > LPC2xxx master. Each slave has unused SPI and UART, which can be used > for this communication. One slave is addressed at once. > > What would be best solution for that? I think SPI is ideal for that. I > could use free port pins for slave selects. Is there any other (more > scalable) option without external/additional components? How many slaves > can I connect to single master to avoid port overloading? Data transfer > rate is very low (~100 bytes/s per slave) and distance between master > and slaves is <1m. > > Any further suggestions or tips&tricks? > > M. If you had CAN controllers on your devices then I'd say use that. You don't need all the differential stuff to run CAN, just hook up all the RX pins (and TX pins via diodes) and add a pull-up. Are all these micros on one board? If so, you can use the same scheme as above with UARTS. That is, make a "1-wire" bus where all the rx lines are joined together, all tx lines are attached to the 1-wire through a diode, a pull-up. You just need some sort of protocol so that the devices don't all talk at the same time. If they're on different boards, then RS485 is the easiest way to go multi-master.

(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

I have to say that the UART solution is the easiest and the best although it's a pity that Philips implemented a PC style UART on the ARM (no 9-bit mode). But with the 16-byte FIFO it does take some of the load off the CPU. The SPI approach suffers for many reasons, mainly because there are no buffers and so incurs a high overhead. But never rule it out, do your sums first, it may be fine in your app. For a hardware interface I would not bother with diodes and pullups but rather tie the rx and tx lines together on the CPU and then couple this to a common coms bus through a current limiting resistor (say 100 - 220ohms) for those recalcitrant nodes. A very light pullup will be needed to keep the line high when inactive. You can always disable the transmitter output when listening and it still has plenty of drive, especially for higher speeds. Then again, the diode/pullup option has some advantages too. No need for 485 unless you are running higher-speeds/longer distances. CAN is ideal for this application but unfortunately the 932s don't have them. *Peter* Marko Pavlin (home) wrote: >Hello! > >I would like to connect several P89LPC932 (x51 core) slaves to single >LPC2xxx master. Each slave has unused SPI and UART, which can be used >for this communication. One slave is addressed at once. > >What would be best solution for that? I think SPI is ideal for that. I >could use free port pins for slave selects. Is there any other (more >scalable) option without external/additional components? How many slaves >can I connect to single master to avoid port overloading? Data transfer >rate is very low (~100 bytes/s per slave) and distance between master >and slaves is <1m. > >Any further suggestions or tips&tricks? -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.7.5 - Release Date: 1/26/05

(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

At 01:49 PM 1/27/05 +1000, you wrote: >I have to say that the UART solution is the easiest and the best >although it's a pity that Philips implemented a PC style UART on the ARM >(no 9-bit mode). But with the 16-byte FIFO it does take some of the load >off the CPU. The SPI approach suffers for many reasons, mainly because >there are no buffers and so incurs a high overhead. But never rule it >out, do your sums first, it may be fine in your app. You can do 9 bit on a 16550 (at least a real one) using a technique I've seen referred to as parity modulation. The ideas is to use 8 bit with mark or space parity. You set up the UART to interrupt on a parity violation and then set it to space parity. When you receive a character with mark parity you get an interrupt and that's your 'address' byte. Just as with normal 9 bit you can then switch receive all characters if selected or just wait for the next parity violation. I may have the sense of whether to use mark and space backwards, it's been a while. And I have no idea if the nearly compatible UART in the LPC's can do it or not. If the lines stay on board I'd certain consider SPI, but I'm always reluctant to run TTL signals off board unprotected. You could use 232 or 485 style drivers I suppose but at that point you might as well use the UART and save the select pins. >CAN is ideal for this application but unfortunately the 932s don't have >them. Depending on what you need to pass around another automotive derived signalling spec to look at is LIN, fewer wires and less communications capability (lower baud, fewer and smaller packets) than CAN. Robert " 'Freedom' has no meaning of itself. There are always restrictions, be they legal, genetic, or physical. If you don't believe me, try to chew a radio signal. " Kelvin Throop, III

(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

At 12:00 AM 1/27/05 -0500, you wrote: >At 01:49 PM 1/27/05 +1000, you wrote: > >CAN is ideal for this application but unfortunately the 932s don't have > >them. > >Depending on what you need to pass around another automotive derived >signalling spec to look at is LIN, fewer wires and less communications >capability (lower baud, fewer and smaller packets) than CAN. And what I didn't point out, uses a UART. Robert " 'Freedom' has no meaning of itself. There are always restrictions, be they legal, genetic, or physical. If you don't believe me, try to chew a radio signal. " Kelvin Throop, III

(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

----- Original Message ----- From: "Robert Adsett" <> To: <> Sent: Thursday, January 27, 2005 5:13 AM Subject: Re: [lpc2000] Best solution for multiMCU comm > > At 12:00 AM 1/27/05 -0500, you wrote: > >>At 01:49 PM 1/27/05 +1000, you wrote: >> >CAN is ideal for this application but unfortunately the 932s don't have >> >them. >> >>Depending on what you need to pass around another automotive derived >>signalling spec to look at is LIN, fewer wires and less communications >>capability (lower baud, fewer and smaller packets) than CAN. > > And what I didn't point out, uses a UART. Atmel has an app note on a software LIN technique for the AVR. Also, EDN has this neat design idea: http://www.edn.com/article/CA484493.html?spacedesc=designIdeas Leon -- Internal Virus Database is out-of-date. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.7.1 - Release Date: 19/01/2005

(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )