This is the mail archive of the ecos-devel@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Uploading and saving images


On Tuesday 31 August 2004 00:37, Gary Thomas wrote:
> On Mon, 2004-08-30 at 14:21, Wayne Gemmell wrote:
> > On Wednesday 18 August 2004 00:11, Wayne Gemmell wrote:
> > > Hi all,
> > >
> > > I don't know if this is the right forum to post this but here goes
> > > anyway...
> >
> > Hi, could anyone point me in the to a forum that can answer this post?
> > I'm really battling to fix this problem. I need to unplug it for testing.
> >
> > > First off, when I try upload files through Minicom using X or Y Modem
> > > protocols I get lots of NAK errors and then
> > >
> > > Ymodem sectors/kbytes sent: 249/31kRetry 0: NAK on sector
> > > Ymodem sectors/kbytes sent: 253/31kRetry 0: NAK on sector
> > > Ymodem sectors/kbytes sent: 254/31kRetry 0: Cancelled
> > >
> > > Transfer incomplete
> > >
> > > RedBoot> load -m y
> > > *** Warning! Checksum failure - Addr: 207990, FF <> 46
> > > xyzModem - CRC mode, 253(SOH)/0(STX)/2(CAN) packets, 123 retries
> > > RedBoot>
> > >
> > > I get the same results from xmodem.
> > >
> > > My transfer protocol settings are
> > > B  ymodem     /usr/bin/sb -vv                 Y    U    N       Y      
> > > Y C  xmodem     /usr/bin/sx -vv                 Y    U    N       Y    
> > >   N
>
> Check that your timeouts are working correctly.  This can be a problem
> if your CYGACC_CALL_IF_DELAY_US is not right.  Try this:
>   RedBoot> lo -m xm
> then do nothing.  Measure how fast the "C" characters come out.  If they
> come out much faster than 1 per 3-5 seconds, then you need to look at
> the delay functions.
The C's come every 5 seconds, roughly. If the problem was in Redboot wouldn't 
that mean that I wouldn't be able to upload using hyperterminal? v850-elf-gdb 
also seems to work as far as my testing goes.

>
> > > I can however load up the program in hyperterminal in Windows.
> > >
> > > Once loaded I follow the instructions in the documentation...
> > > redboot> fis create file_name
> > > redboot>fconfig
> > > Do you want to run a boot script?>true
> > > Enter boot script terminated by empty line>
> > > fis load file_name
> > > go 0x205000
> > >
> > > Set time out>5
> > > Write>y
> > >
> > > I can run the program straight away but when I reset the unit (fx35)
> > > the program fails to execute with no errors.
> > >
> > > Any ideas? I've seen similar questions through googling but no real
> > > answers.
>
> This can happen if your device has two serial ports.  RedBoot will
> gladly print messages and accept commands on either.  However, if
> you try and run a boot-script and use a port which is not the system
> default, then you'll not see any messages get printed.
I have connected to both serial ports, the debug and the serial access port. I 
can't see any output in either of them. There is nothing wrong with my boot 
script because when I type reset the boot script works but on a hard reset 
the program bombs. 

Thanks
Wayne


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]