Yahoo Groups archive
Thread
2005-11-08 by valis_eric_ykchan
I'm new to microprocessor. I have a LPC2114 inserted on a RedHat 9.0 via Moschip PCI product. I have to make some communication between the programs on the chip and the linux. Can I simply use printf and scanf and "SWI" to communicate via the serial port? Thanks. Eric
2005-11-08 by David Hawkins
valis_eric_ykchan wrote:
> I'm new to microprocessor.
>
> I have a LPC2114 inserted on a RedHat 9.0 via Moschip PCI product. I
> have to make some communication between the programs on the chip and
> the linux. Can I simply use printf and scanf and "SWI" to communicate
> via the serial port?
Hi Eric,
If the board has the serial port available, then yes you should
be able to talk to the processor over the serial port - but
only once it is programmed.
So the real question is;
1) How does Moschip expect you to program the device; over PCI,
or over serial using the bootloader, or both?
2) Does Moschip supply a device driver, or at least enough
data to write your own driver.
3) What is used as the PCI-to-micro interface, I don't think
that this chip has an external memory interface, so have
they made it an SPI or I2C target, or built a bit-bang interface.
4) What is the PCI chipset used on the board; PLX, AMCC, TI?
Send a link to the board data sheet and I'll tell you what I think.
Dave2005-11-09 by Eric
--- In lpc2000@yahoogroups.com, David Hawkins <dwh@o...> wrote: > > valis_eric_ykchan wrote: > > I'm new to microprocessor. > > > > I have a LPC2114 inserted on a RedHat 9.0 via Moschip PCI product. I > > have to make some communication between the programs on the chip and > > the linux. Can I simply use printf and scanf and "SWI" to communicate > > via the serial port? > > Hi Eric, > > If the board has the serial port available, then yes you should > be able to talk to the processor over the serial port - but > only once it is programmed. > > So the real question is; > > 1) How does Moschip expect you to program the device; over PCI, > or over serial using the bootloader, or both? > > 2) Does Moschip supply a device driver, or at least enough > data to write your own driver. > > 3) What is used as the PCI-to-micro interface, I don't think > that this chip has an external memory interface, so have > they made it an SPI or I2C target, or built a bit-bang interface. > > 4) What is the PCI chipset used on the board; PLX, AMCC, TI? > > Send a link to the board data sheet and I'll tell you what I think. > > Dave > Thanks for your reply. The only *driver* of Moschip is to set the serial port to the PCI (http://www.moschip.com/data/products/NM/linux.zip). I don't know the exact model of the PCI chipset (Nm9715, Nm9755, Nm9805, Nm9820, Nm9835, Nm9845, etc) http://www.moschip.com/html/data_sheets.html I don't have a JTAG debugger, I also don't have Angel Debug Monitor. I can only load the sample program to the LPC2114. If nothing comes out, then I don't know what's wrong. Probably I'll have to tell my boss about this mission impossible when he come back...
2005-11-09 by Peter Homann
Hi, I've managed to stuff up something, so that my MCB2130 board won't communicate with the Philips download utility. I'm not sure what I've done. I may have downloaded a hex file for an incorrect processor. Or maybe erasing the whole chip erases the boot loader. Is there something I can do to get it working again? Cheers, Peter. -- ------------------------------------------------------------------ Web: www.homanndesigns.com email: homann@... Phone: +61 421 601 665 www.homanndesigns.com/ModIO.html - Modbus Interface Unit www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
2005-11-09 by David Hawkins
Eric wrote: > > Thanks for your reply. The only *driver* of Moschip is to set the > serial port to the PCI > (http://www.moschip.com/data/products/NM/linux.zip). > > I don't know the exact model of the PCI chipset (Nm9715, Nm9755, > Nm9805, Nm9820, Nm9835, Nm9845, etc) > http://www.moschip.com/html/data_sheets.html Well, according the PDF in the zip file refers to 9835 and 9735, and the data sheet link says that a 9835 is a PCI UART + parallel port, i.e., seems like the chip is destined for use in boards that add a parallel and serial port to your PC. In this case, the serial port has been attached to the LPC. > I don't have a JTAG debugger, I also don't have Angel Debug Monitor. I > can only load the sample program to the LPC2114. If nothing comes out, > then I don't know what's wrong. Probably I'll have to tell my boss > about this mission impossible when he come back... Well, if you can load programs to the LPC2114, you clearly have flash downloading etc working. You can get by without a debugger pretty easily. I've never used one with the LPC parts. Start out with a startup file that sets up the vectors correctly and turn on an LED. Then work on a startup file that sets up the C environment and write a main.c that turns on an LED, ... small steps, make sure you understand each step. Then you'll understand how things work. Don't blindly assume that you can just take GNUARM tools and get things to work on your processor. If you don't understand the above comments - ask more! Dave
2005-11-09 by Peter Homann
Hi, Can anyone help me with getting my LPC2138 processor to start talking to the Philips Flash utility again. A previously explained, it appears to have locked up and I can no longer program it. Is it possible to screw up the boot loader. I'd really appreciate some help here. Cheers, Peter. Peter Homann wrote: > Hi, > > I've managed to stuff up something, so that my MCB2130 board won't > communicate with the Philips download utility. I'm not sure what I've > done. I may have downloaded a hex file for an incorrect processor. Or > maybe erasing the whole chip erases the boot loader. > > Is there something I can do to get it working again? > > Cheers, > > Peter. -- ------------------------------------------------------------------ Web: www.homanndesigns.com email: homann@... Phone: +61 421 601 665 www.homanndesigns.com/ModIO.html - Modbus Interface Unit www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
2005-11-09 by Tom Walsh
Peter Homann wrote: >Hi, > >Can anyone help me with getting my LPC2138 processor to start talking to > the Philips Flash utility again. > >A previously explained, it appears to have locked up and I can no longer >program it. > >Is it possible to screw up the boot loader. > >I'd really appreciate some help here. > >Cheers, > >Peter. > >Peter Homann wrote: > > > >>Hi, >> >>I've managed to stuff up something, so that my MCB2130 board won't >>communicate with the Philips download utility. I'm not sure what I've >>done. I may have downloaded a hex file for an incorrect processor. Or >>maybe erasing the whole chip erases the boot loader. >> >>Is there something I can do to get it working again? >> >> >> Hold P0.14 low and reset the chip. You are probably have a valid checksum in the Flash and it is jump to that program instead of the bootloader. So, you have to "force" it into the loader. TomW -- Tom Walsh - WN3L - Embedded Systems Consultant http://openhardware.net, http://cyberiansoftware.com "Windows? No thanks, I have work to do..." ----------------------------------------------------
2005-11-09 by Peter Homann
Hi Tom, Thanks for the reply. The circuit diagram has P0.14 connected to the com port via a jumper. I'll try holding it low manually as suggested by Zdravko. Do I need to release it before programming? Or, can I leave it tied low for the duration of the programming? Cheers, Peter. Tom Walsh wrote: > Peter Homann wrote: > > >>Hi, >> >>Can anyone help me with getting my LPC2138 processor to start talking to >> the Philips Flash utility again. >> >>A previously explained, it appears to have locked up and I can no longer >>program it. >> >>Is it possible to screw up the boot loader. >> >>I'd really appreciate some help here. >> >>Cheers, >> >>Peter. >> >>Peter Homann wrote: >> >> >> >> >>>Hi, >>> >>>I've managed to stuff up something, so that my MCB2130 board won't >>>communicate with the Philips download utility. I'm not sure what I've >>>done. I may have downloaded a hex file for an incorrect processor. Or >>>maybe erasing the whole chip erases the boot loader. >>> >>>Is there something I can do to get it working again? >>> >>> >>> > > Hold P0.14 low and reset the chip. You are probably have a valid > checksum in the Flash and it is jump to that program instead of the > bootloader. So, you have to "force" it into the loader. > > TomW > > -- ------------------------------------------------------------------ Web: www.homanndesigns.com email: homann@... Phone: +61 421 601 665 www.homanndesigns.com/ModIO.html - Modbus Interface Unit www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
2005-11-10 by Tom Walsh
Peter Homann wrote: >Hi Tom, > >Thanks for the reply. The circuit diagram has P0.14 connected to the com >port via a jumper. I'll try holding it low manually as suggested by Zdravko. > >Do I need to release it before programming? Or, can I leave it tied low >for the duration of the programming? > > > You can release it once it enters the bootloader, it is only necessary to hold it low to notify the processor that you wish it to run the bootloader. TomW -- Tom Walsh - WN3L - Embedded Systems Consultant http://openhardware.net, http://cyberiansoftware.com "Windows? No thanks, I have work to do..." ----------------------------------------------------
2005-11-11 by Eric
--- In lpc2000@yahoogroups.com, David Hawkins <dwh@o...> wrote: > > Eric wrote: > > > > > Thanks for your reply. The only *driver* of Moschip is to set the > > serial port to the PCI > > (http://www.moschip.com/data/products/NM/linux.zip). > > > > I don't know the exact model of the PCI chipset (Nm9715, Nm9755, > > Nm9805, Nm9820, Nm9835, Nm9845, etc) > > http://www.moschip.com/html/data_sheets.html > > Well, according the PDF in the zip file refers to 9835 and 9735, > and the data sheet link says that a 9835 is a PCI UART + parallel > port, i.e., seems like the chip is destined for use in boards > that add a parallel and serial port to your PC. In this case, > the serial port has been attached to the LPC. > > > I don't have a JTAG debugger, I also don't have Angel Debug Monitor. I > > can only load the sample program to the LPC2114. If nothing comes out, > > then I don't know what's wrong. Probably I'll have to tell my boss > > about this mission impossible when he come back... > > Well, if you can load programs to the LPC2114, you clearly have > flash downloading etc working. You can get by without a debugger > pretty easily. I've never used one with the LPC parts. > > Start out with a startup file that sets up the vectors correctly > and turn on an LED. Then work on a startup file that sets up the > C environment and write a main.c that turns on an LED, ... small > steps, make sure you understand each step. Then you'll understand > how things work. > > Don't blindly assume that you can just take GNUARM tools and > get things to work on your processor. > > If you don't understand the above comments - ask more! > > Dave > Thanks for your reply. I'm not using an evaluation board, probably I won't have any LED :p
2005-11-11 by David Hawkins
Eric wrote: > Thanks for your reply. I'm not using an evaluation board, probably I > won't have any LED :p But the board has to be doing I/O of some sort, otherwise its kind of a waste :) If you have a schematic of your board, then you can always configure an I/O pin as output and then drive an LED. Just make sure that the I/O pin is not being driven by something. If you want more help just ask, I'll take a look at the schematic, or board docs and suggest what you can do. Dave
2005-11-11 by Eric
--- In lpc2000@yahoogroups.com, David Hawkins <dwh@o...> wrote: > > Eric wrote: > > > Thanks for your reply. I'm not using an evaluation board, probably I > > won't have any LED :p > > But the board has to be doing I/O of some sort, otherwise its > kind of a waste :) > > If you have a schematic of your board, then you can always > configure an I/O pin as output and then drive an LED. > Just make sure that the I/O pin is not being driven > by something. > > If you want more help just ask, I'll take a look at the > schematic, or board docs and suggest what you can do. > > Dave > Thanks for you reply. I'll take a look at what I have and what I can do :)