On 6/8/05, Stephen Rivera - WRCA.Net <steverivera@wrca.net> wrote:
the dsp cards should use the dmf files. the older cards used the sdl files. are you using TCM or PSDL.exe?
I'm using PCSDL, because the card has no firmware on it (thus I can't use TCM) In this case I'm working with an NMC, not a DSP card. I have the actual firmware file that I could upload via TCM if the card had firmware already, but not this sdl file that PCSDL claims to require. The output of PCSDL.EXE: U.S. Robotics, Inc. (c) 1993-1995 Software Download Program Version 3.0.2 **Error** Insufficient Number of Arguments Command Line Options: pcsdl -pPort -rRate -iIrq -vSDn.n.n -v<NA/NI>n.n.n -nSD?? -n<NA/NI>?? [-dDirectory] -pPort <Required> = COM Port: 1, 2, 3 or 4 -rRate <Required> = Baud Rate: 2400, 9600, 19200, 38400, 57600 or 115200 -iIrq [Optional] = 3(default COM2/4), 4(default COM1/3), 5, or 7 -vSDn.n.n <Required> = Software Download Version: n = 0-99 -v<NA/NI>n.n.n <Required> = NAC/NIC Operation Code Version: n = 0-99 -nSD?? <Required> = Software Download Filename Prefix: ? = ASCII -n<NA/NI>?? <Required> = NAC/NIC Operation Code Filename Prefix: ? = ASCII -dDirectory [Optional] = DOS Directory Path Name: default = current directory -b [Optional] = Disable Uart's Fifos Example: pcsdl -p1 -r38400 -vSD1.1.0 -vNA1.2.0 -nSDt1 -nNAst As you can see it requires three arguments, one being the SDL file. UTStar shows the following in their documentation of how to use PCSDL: 7. Once you are in the directory that you stored the code in you can now issue the pcsdl commands as follows: pcsdl -p1 -r9600 -vsdn.n.n -vnan.n.n –nsd[nn] –nna[nn]Note: Be careful with the baud rate. In most cards it varies according to the position of the dipswitches 1 and 2. Parameter Purposepcsdl executes the PC SDL program -p selects the communication port (port 1 or 2) -r selects serial port rate (= to card DIP switch settings) -vsd Version number of the .sdl file. -subsitute a real number for n.n.n (-vnd1.0.2) -vna Version number of the NAC file substitute a real number for n.n.n (-vna1.0.3) -nsd Two character prefix of the .SDL file name (example -nsdnm = NMC) -d specifies the directory path name (optional); -d should be followed by thedirectory name where the operation and SDL software are stored [not necessary if you have run the pcsdl program from the directory where you placed the SDL and NAC files] -h displays on line help-nna Filename prefixes are required to specify the type of .sdl and .nac file used in the download. So, from what I can tell, I have to have this ".sdl" file - but I have no idea where to obtain it. - Nick
At 03:19 PM 6/8/2005, you wrote:
On 6/7/05, Clayton Zekelman <clayton@mnsi.net> wrote:
When the NMC cards were upgrade to a larger flash to support Hiper DSP
cards, USR shipped blank flash modules to replace the smaller ones that shipped with the cards.
To put the code on the unit, you would do it through the serial port
using the PCSDL.EXE utility.
When the card is sitting there with a green blinking light, it means
its waiting for the PCSDL utility to send it code through the serial port.
So, I got PCSDL from UTStar's support site, and copied all of my firmware files to the same directory, but It wants this SDL file. The problem is that I have no idea what that file is, and have never seen one. It's not included in the .zip files of firmware I have either. Is this something I can get ahold of without a support contract?
Any advice appreciated :)
----- Original Message ---------------
Subject: [USR-TC] How to reload firmware on blank NMC? From: Nick Bright <nick.bright@gmail.com> Date: Tue, 7 Jun 2005 19:26:41 -0500 To: usr-tc@mailman.xmission.com
So in my exploration of what componants are available to me to deploy this new RAS, I went through my NMC collection. I've discovered that one of my NMC units has a stick note stating "NO SOFTWARE!!!!", and when I put it in my chassis and try to boot it, it does nothing - won't even respond on the serial port. All I get is a blinking green "RN/FL" light.
So, I'm figuring someone tried to flash it, and it didn't work. Any thoughs on how to fix this? Can I send firmware up to it through the serial port somehow?
Thanks, Nick
_______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc
_______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc