[ECOS] RedBoot image for Olimex LPC-E2294

[ECOS] RedBoot image for Olimex LPC-E2294

[peter_lanius]

Hi,

I would like to use RedBoot / eCOS for my new project which is going to run on an Olimex LPC-E2294 board. I have built RedBoot as per the instructions in Anthony Massa's book (using the 'redboot' template for the Olimex board). The whole build went without a hitch, I used the Redboot_ROM.ecm configuration options file provided in the eCOS 3.0 distribution for the Olimex board.

I then used CrossWorks to burn the Flash image ('redboot.bin') using 0x00000000 as the load address. This seemed to work ok as well and when I restarted the board I could connect to RedBoot via Hyperterminal. But I do get a warning message:
 
FLASH: driver init failed: Invalid FLASH address
**Warning** FLASH configuration checksum error or invalid key
Use 'fconfig -i' to [re]initialize database
No network interfaces found

RedBoot(tm) bootstrap and debug environment [ROM]
Non-certified release, version v3_0 - built 19:33:12, Oct 19 2009
...
Platform: Olimex LPC-E2294 development board (ARM7TDMI-S)
RAM: 0x81000000-0x81100000 [0x8100b560-0x810f1000 available]
RedBoot>


What does the 'Invalid Flash address' message mean? Did I burn RedBoot into the wrong location? Should I have used the 'redboot.elf' file instead? Should I have modified the 'mlt_arm_lpc2xxx_olpce2294_rom.ldi' file (what is in there seems to me to also suggest the 0x00000000 start address)?

Thanks
Peter



      __________________________________________________________________________________
Get more done like never before with Yahoo!7 Mail.
Learn more: http://au.overview.mail.yahoo.com/

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] RedBoot image for Olimex LPC-E2294

[Sergei Gavrikov]

On Mon, Oct 19, 2009 at 02:32:36AM -0700, peter_lanius@yahoo.com.au wrote:
> Hi,
> 
> I would like to use RedBoot / eCOS for my new project which is going
> to run on an Olimex LPC-E2294 board. I have built RedBoot as per the
> instructions in Anthony Massa's book (using the 'redboot' template
> for the Olimex board). The whole build went without a hitch, I used
> the Redboot_ROM.ecm configuration options file provided in the eCOS
> 3.0 distribution for the Olimex board.
> 
> I then used CrossWorks to burn the Flash image ('redboot.bin') using
> 0x00000000 as the load address. This seemed to work ok as well and
> when I restarted the board I could connect to RedBoot via
> Hyperterminal. But I do get a warning message:
>  
> FLASH: driver init failed: Invalid FLASH address
> **Warning** FLASH configuration checksum error or invalid key
> Use 'fconfig -i' to [re]initialize database
> No network interfaces found
> 
> RedBoot(tm) bootstrap and debug environment [ROM]
> Non-certified release, version v3_0 - built 19:33:12, Oct 19 2009
> ...
> Platform: Olimex LPC-E2294 development board (ARM7TDMI-S)
> RAM: 0x81000000-0x81100000 [0x8100b560-0x810f1000 available]
> RedBoot>

Hello Peter,

What's board revision do you have?
http://olimex.com/dev/lpc-e2294.html
http://olimex.com/dev/lpc-e2294rb.html

These boards have the different flash parts. eCos v3_0 has HAL for old
(Olimex now says 'obsolete board') Olimex LPC-E2294 board. If you have
the new one, i.e. Olimex LPC-E2294 REV.B board, try this HAL from here
http://bitbucket.org/tickling/olpcx22xx/

> What does the 'Invalid Flash address' message mean? Did I burn
> RedBoot into the wrong location? Should I have used the
> 'redboot.elf' file instead? Should I have modified the
> 'mlt_arm_lpc2xxx_olpce2294_rom.ldi' file (what is in there seems to
> me to also suggest the 0x00000000 start address)?

Old Olimex LPC-E2294 had 28F320C3 Intel flash parts, new boards have
28F160C3. These flash parts have the different device codes, perhaps,
eCos v3_0 flash driver for olpce2294 target cannot identify your chip.


Sergei

> Thanks
> Peter
> 
> 
> 
>       __________________________________________________________________________________
> Get more done like never before with Yahoo!7 Mail.
> Learn more: http://au.overview.mail.yahoo.com/
> 
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] RedBoot image for Olimex LPC-E2294

[peter_lanius]

Hi Sergei

I have the Rev B Olimex LPC-E2294 board with the LPC-2214 CPU and 1MB of Flash (MX26LV800T).

Do I need to apply all the patches from the 

bitbucket.org/tickling/olpcx22xx/

repository?

Thanks, Peter



----- Original Message ----
From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: peter_lanius@yahoo.com.au
Cc: ecos-discuss@ecos.sourceware.org
Sent: Mon, 19 October, 2009 9:45:57 PM
Subject: Re: [ECOS] RedBoot image for Olimex LPC-E2294

On Mon, Oct 19, 2009 at 02:32:36AM -0700, peter_lanius@yahoo.com.au wrote:
> Hi,
> 
> I would like to use RedBoot / eCOS for my new project which is going
> to run on an Olimex LPC-E2294 board. I have built RedBoot as per the
> instructions in Anthony Massa's book (using the 'redboot' template
> for the Olimex board). The whole build went without a hitch, I used
> the Redboot_ROM.ecm configuration options file provided in the eCOS
> 3.0 distribution for the Olimex board.
> 
> I then used CrossWorks to burn the Flash image ('redboot.bin') using
> 0x00000000 as the load address. This seemed to work ok as well and
> when I restarted the board I could connect to RedBoot via
> Hyperterminal. But I do get a warning message:
>  
> FLASH: driver init failed: Invalid FLASH address
> **Warning** FLASH configuration checksum error or invalid key
> Use 'fconfig -i' to [re]initialize database
> No network interfaces found
> 
> RedBoot(tm) bootstrap and debug environment [ROM]
> Non-certified release, version v3_0 - built 19:33:12, Oct 19 2009
> ...
> Platform: Olimex LPC-E2294 development board (ARM7TDMI-S)
> RAM: 0x81000000-0x81100000 [0x8100b560-0x810f1000 available]
> RedBoot>

Hello Peter,

What's board revision do you have?
http://olimex.com/dev/lpc-e2294.html
http://olimex.com/dev/lpc-e2294rb.html

These boards have the different flash parts. eCos v3_0 has HAL for old
(Olimex now says 'obsolete board') Olimex LPC-E2294 board. If you have
the new one, i.e. Olimex LPC-E2294 REV.B board, try this HAL from here
http://bitbucket.org/tickling/olpcx22xx/

> What does the 'Invalid Flash address' message mean? Did I burn
> RedBoot into the wrong location? Should I have used the
> 'redboot.elf' file instead? Should I have modified the
> 'mlt_arm_lpc2xxx_olpce2294_rom.ldi' file (what is in there seems to
> me to also suggest the 0x00000000 start address)?

Old Olimex LPC-E2294 had 28F320C3 Intel flash parts, new boards have
28F160C3. These flash parts have the different device codes, perhaps,
eCos v3_0 flash driver for olpce2294 target cannot identify your chip.


Sergei

> Thanks
> Peter
> 
> 
> 
>       __________________________________________________________________________________
> Get more done like never before with Yahoo!7 Mail.
> Learn more: http://au.overview.mail.yahoo.com/
> 
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss



      __________________________________________________________________________________
Get more done like never before with Yahoo!7 Mail.
Learn more: http://au.overview.mail.yahoo.com/

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] RedBoot image for Olimex LPC-E2294

[Sergei Gavrikov]

On Mon, Oct 19, 2009 at 04:42:12AM -0700, peter_lanius@yahoo.com.au wrote:
> Hi Sergei
> 
> I have the Rev B Olimex LPC-E2294 board with the LPC-2214 CPU and
> 1MB of Flash (MX26LV800T).
                ^^^^^^^^^^
                         |_ That is not Intel parts!

Peter, it seems for me that you have Olimex LPC-E22_14_ board, and not
Olimex LPC-E22_94_ ! I have not the same board and I could not test a
flash driver for it, but, there is `olpce2214' target in a row of
those olpcx22xx targets. You can try that target, but, there are _No
Warranties_ that you will have a success. The target's flash driver
was written in 'a dark' (I just assumed that MX26LV800T parts belong
the am29xxxxx family), but, may be that's my fault (in this case you
need to write own flash driver or ask about community).

> Do I need to apply all the patches from the 
> 
> bitbucket.org/tickling/olpcx22xx/
> 
> repository?

There is install script which upgrades old LPC2294 targets from Olimex
and adds new ones. All those targets use some olpcx22xx common part to
prevent a duplication of code

hal
`-- arm
    `-- lpc2xxx
        `-- olpcx22xx
            |-- common
            |-- olpce2214
            |-- olpce2294
            |-- olpce2294rb
            |-- olpch2214
            |-- olpch2294
            `-- olpcl2294

I did not try to install a choosen target separately, but, you can try
it, perhaps, it's needed some handywork.

Peter, I would suggest you do not mess up your eCos v3_0 sources, and
try to install new experimental targets for eCos sources is got from
CVS/HG repository, a safe way to try the experimental code would be

mkdir -p ~/sandbox && cd ~/sandbox
hg clone http://hg-pub.ecoscentric.com/ecos     ;# ~80M of traffic
hg clone http://bitbucket.org/tickling/olpcx22xx;# <1M of traffic
export ECOS_REPOSITORY=~/sandbox/ecos/packages  ;# <- Important!!!
sh olpcx22xx/install.sh                         ;# Install targets

Build RedBoot[ROM] without flash support, burn it, if you will get
the alive RedBoot, then build eCos flash test, `flash1'

mkdir -p /tmp/t && cd /tmp/t
export ECOS_REPOSITORY=~/sandbox/ecos/packages  ;# <- Important!!!
ecosconfig new olpce2214
ecosconfig add flash
ecosconfig tree && make
make -C io/flash/current tests

and walk through out a flash init code in GDB. May be you'll get a
clue.

If you have a doubt about 80M of traffic, drop me tonight personally,
then I'll build `RedBoot' and `flash1' images for the target and
upload them on bitbucket for a testing.


Sergei



-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] RedBoot loading eCOS examples causes PC reboot

[peter_lanius]

Hi,

I have now successfully installed RedBoot on my Olimex LPC-E2214 Rev_B board. I can excute RedBoot commands via the serial port using Hyperterminal. I then built the eCOS library for the default configuration using the configtool. Finally I built the eCOS example applications using the standard Makefile under /ecos/examples. The Makefile produces ELF files which are rather big (850KB) for serial transfer, so I used arm-eabi-objcopy to create SREC files (150KB). 

I then use RedBoot to download an application using:
load -v -m ymodem 

I then use Hyperterminal to send the SREC file via Ymodem. This process seems to run ok until it is finished, when the suddenly PC reboots. That happens every time. No other applications are open. The board is connected via a USB-to-Serial cable and the Olimex JTAG ARM_USB_OCD is also connected, but OpenOCD/GDB is not running.

I have tried it with the ELF file as well, same result. 

What am I doing wrong and why does the PC reboot?

Thanks
Peter


      __________________________________________________________________________________
Get more done like never before with Yahoo!7 Mail.
Learn more: http://au.overview.mail.yahoo.com/

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] RedBoot loading eCOS examples causes PC reboot

[Sergei Gavrikov]

Peter writes
> Hi,
> 
> I have now successfully installed RedBoot on my Olimex LPC-E2214
> Rev_B board. I can excute RedBoot commands via the serial port using
> Hyperterminal. I then built the eCOS library for the default
> configuration using the configtool. Finally I built the eCOS example
> applications using the standard Makefile under /ecos/examples. The
> Makefile produces ELF files which are rather big (850KB) for serial
> transfer, so I used arm-eabi-objcopy to create SREC files (150KB). 
> 
> I then use RedBoot to download an application using: load -v -m
> ymodem 
> 
> I then use Hyperterminal to send the SREC file via Ymodem. This
> process seems to run ok until it is finished, when the suddenly PC
> reboots. That happens every time. No other applications are open.

Hi Peter

if you wrote, suddenly _board_ reboots, I would start to investigate
in your issue. But it seemed for me the described behavior is not eCos
(target) related thing. I'm sorry, I does not use Windows+Cygwin eCos
environment. I interact with the board via Redboot just fine on 230K
via USB-to-serial, but, under Linux. Just a guess, may be your issue
is a FTDI driver issue? Do you use UART0 to connect to the target? If
you do, it means that it is used serial-over-usb stuff (=FTDI driver
for Windows). May be some FTDI driver's issue does reboot PC? Try to
use LPC's UART1 and use a real serial DB9 connector (NO USB, NO FTDI).
On start Redboot "listens" on both serial channels and will start to
interact on that channel on which it will see the first input.

Second. You can add CYGPKG_COMPRESS (=zlib) to Redboot build and that
will let you then to upload the gzip-compressed images if you will use
RB's load command with -d (decompress) option

gzip hello

Redboot> load -m y -d
CC

Then open hello.gz in terminal program and start to upload it using
Y-modem protocol.

Third. The got images are not huge, to see/know its size, invoke

arm-eabi-size hello

and look on .code segment for a reference.

Fourth. Start to play with eCos tests using GDB or Insight. The eCos
tests are small, laconic, and well designed and they all run smoothly
under GDB. Just select in configtool: Build Tests and you will get a
lot of them for the target under tests directory.

> The board is connected via a USB-to-Serial cable and the Olimex JTAG
> ARM_USB_OCD is also connected, but OpenOCD/GDB is not running.
                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^
I'm sorry. Again, it is not eCos related too.

> I have tried it with the ELF file as well, same result. 
> 
> What am I doing wrong and why does the PC reboot?

IMO, it is something wrong with your work environment, settings, etc.
I believe in that what any terminal program can/should not reboot PC.
Well, may be just to hang it :-) or to freeze a keyboard input, but, a
rebooting..., it's very strange. Peter, what your PC is? May be it is
a Laptop with USB ports only? However, I use both and PC and DELL
Laptop without serial ports with the target having no issues with it,
but, that is Linux. I'm sorry, I have no clues anymore, but if you can
try UART1 (real serial port), try it. FYI, you can use Ethernet to
upload images on the target, but, that is off-topic just now. Try the
UART1 first.

HIH

Sergei

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] Re: RedBoot loading eCOS examples causes PC reboot

[Grant Edwards]

On 2009-10-24, peter_lanius@yahoo.com.au <peter_lanius@yahoo.com.au> wrote:

> I then use Hyperterminal to send the SREC file via Ymodem.
> This process seems to run ok until it is finished, when the
> suddenly PC reboots. That happens every time. No other
> applications are open. The board is connected via a
> USB-to-Serial cable and the Olimex JTAG ARM_USB_OCD is also
> connected, but OpenOCD/GDB is not running.
>
> I have tried it with the ELF file as well, same result. 
>
> What am I doing wrong

You're using Windows.

> and why does the PC reboot?

You're using Windows.  

1/2 ;)

Seriously, it's a Windows problem.  Probably a bug in one of
the of the USB-serial drivers (either the one for the
ARM_USB_OCD adapter or the one for the USB-serial cable).  Try
it without the ARM_USB_OCD plugged in.  Try it with a different
USB-serial cable (one that uses a chip from a different
vendor).

It might also be Hyperterminal. Though it's a buggy piece of
dreck, I don't think it's the cuplit in this case -- but you
could try something like Teraterm.

Or you could try using Linux...

-- 
Grant




-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] RedBoot loading eCOS examples causes PC reboot

[Sergei Gavrikov]

Please keep your replies on the mailing list so that all may benefit.

Peter wrote:
> Hi Sergei
> 
> thank you for being so helpful. I understand that what I reported
> isn't an eCOS issue and rather has to do with
> Windows/Hyperterminal/FTDI drivers. 
> 
> I am happy to switch to Linux as I had several problems with the
> FTDI drivers under Windows. I would appreciate a few pointers
> regarding the selection of tools you recommend. I have installed
> openSUSE 11.1 and added obvious things like Eclipse, mercurial,
> python.

Hi Peter,

That's great. I hope that you will get a success with the target under
Linux more that you are unix veteran as I knew and I hope you will get
an enjoy with the modern unix-like environment (Linux) and open source
OS for embedded (eCos). I used Slackware a couple years ago and now
beeing no geek anymore :-) I use Ubuntu, but, openSUSE it is the great
distribution too! So, my proposals would be an apt-centric, but your
system is zypper-centric. Hope, someone will fix my faults.

> What I would like to know is:
> 1. Which GNU ARM toolchain do I install? Sourcery G++ Lite for ARM
> EABI?

That toolchain is built against newlib libc and eCos has own libc
implementation. There is ready-to-use eCos toolchain for ARM (and
other) targets on the eCosCentric FTP site:
ftp://ecoscentric.com/pub/ecos/gnutools/

You have to install this toolchain for the target
ftp://ecoscentric.com/pub/ecos/gnutools/i386linux/ecoscentric-gnutools-arm-eabi-20081213-sw.i386linux.tar.bz2

The toolchain is based on GCC 4.3 on it is well tested toolchain for
eCos v3_0/CVS. But, more proper way to install eCos is to use these
official proposals and eCos install script. Look here, please
http://ecos.sourceware.org/getstart.html

So, you have to install Tcl to get the stuff. On Ubuntu it's need to
install {tcl,tk}-dev packages with apt-get, and Google told me that
you need to do

$ sudo zypper install tcl tk tcl-devel tk-devel

and then run `sh ecos-install.tcl' as root (sudo sh) and you will get
eCos v3_0, configtool and the selected gnu toolchain(s) under /opt.
And how to install eCos from HG I wrote you a couple days ago. So, may
be you need only arm-eabi toolchain only from their FTP.

> 2. Where do I get the FTDI driver for the Olimex ARM-USB-OCD JTAG
> for Linux? How do I install it?

The below is the FTDI board related (no OpenOCD USB JTAG). The modern
Linux kernels have modules to manage FTDI devices. Just plug in your
board to USB port and then look on `dmesg' output.

$ gmesg | tail

and you'll get it.

or use lsusb utility

$ lsusb | grep -i future
Bus 005 Device 002: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC

and at the end you should see new character device (on my Ubuntu that
will be ttyUSB0, I hope on openSUSE that will be the same)

$ ls -l /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 0 2009-10-25 13:01 /dev/ttyUSB0

And this character device can be used to interact with RedBoot on the
board via terminal program. As you can see I should belong `dialout'
group, but on SUSE that may be something another.

> 3. Do I need to install OpenOCD? If yes, which version? Do I need to
> build it?

Peter, nowadays I do not use OpenOCD with the board, it's enougth for
me to use the pair RedBoot+GDB for that target (your target has 1M RAM
and that is good amount of memory to use RedBoot), but, in a past I
had success with Olimex parallel JTAG wiggler and OpenOCD on Linux box
(well that openocd was built from sources). Today eCos/Redboot has not
native support for OpenOCD debugger. So, I would say, it is may be odd
to use JTAG for _your_ target. Seek on the list on the subject and you
will know about OpenOCD+eCos a bit more. I live without JTAG because I
can burn ROM images using own Expect script, i.e. program on-chip LPC
flash using LPC ISP commands via... /dev/ttyUSB0, e.g.

$ prog_lpc2xxx -file install/bin/redboot.bin -port /dev/ttyUSB0

Since I've used RedBoot I does not need JTAG/OpenOCD. If you want I
can put that script on bitbucket.

> Anything else you recommend? I haven't done development on Unix
> since 1992, so my knowledge is rather obsolete...

Perhaps, you need to install `minicom' (instead hyperterm) and may be
`lrzsz' package (x,y,zmodems utilities).

$ sudo zypper install minicom

Then prepare minicom rc script for the target

$ cat > ~/.minirc.olimex << EOF
pu port             /dev/ttyUSB0
pu baudrate         38400
pu bits             8
pu parity           N
pu stopbits         1
pu rtscts           No 
EOF

And use `minicom' with the board (~ HyperTerm), `man minicom'.

$ minicom -o olimex ;# run then press RST on the board.

Eclipse... I'm sorry, I do not use this IDE. The gdb, gdb-tui is
enough for me, this is a good intro http://beej.us/guide/bggdb/

To develop on Linux you need to have more stuff is got with zypper,
i.e. to install some host's development tools, gcc, g++, autotools,
etc. if you plan to use eCos from CVS/HG and build the latest eCos
host tools from the sources. Wellcome to Open Source World!

Well, on Ubuntu that's easy enough

$ sudo apt-get install build-essential

What's I found for openSUSE
http://forums.opensuse.org/applications/413553-build-essential.html

$ zypper se -t pattern devel

and it seems for me those `devel_basic', `devel_C_C++' will be good
choices for start. But, may be you have those packages installed.

Peter, and at the end, all eCos/RedBoot documentation is your friend
http://ecos.sourceware.org/docs-latest/
and sure the eCos mailing list archives (it is searchable stuff)
http://ecos.sourceware.org/intouch.html
and Google as well are too.

HIH

Sergei

> Thanks
> Peter

[snip]

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] RedBoot loading eCOS examples causes PC reboot

[Sergei Gavrikov]

Sergei Gavrikov wrote:
> Peter Lanius wrote:
[snip]
> > 2. Where do I get the FTDI driver for the Olimex ARM-USB-OCD JTAG
> > for Linux? How do I install it?
> 
> The below is the FTDI board related (no OpenOCD USB JTAG). The modern
> Linux kernels have modules to manage FTDI devices. Just plug in your
> board to USB port and then look on `dmesg' output.
[snip]

Peter, I'm sure that it's possible to get working Olimex USB JTAG (I
have not this JTAG) and OpenOCD working under Linux. But, you need
to have some experience with a building the GNU packages using that
'configure-make-make install' magic, i.e.

svn checkout http://svn.berlios.de/svnroot/repos/openocd/trunk openocd
...

cd openocd
sh bootstrap

But just here you _can_ get a lot of a panic about some absent things:
aclocal, autoconf, autoheader, automake, libtool, etc. and I will be
very sorry if you will be sorry about a changing host OS for eCos
development

I "found" (excuse me SUSE guys)
http://software.opensuse.org/search

and enter 'openocd' in search box. It seemed for me that you can
install OpenOCD just from Web or manually (from those RPMs) and if you
have valid openocd cfg file for target board and your usb jtag, you
can try it. It seems for me that `dmesg', `lsmod', `lsusb' are good
things to know what is happened when you plug in that  USB cable.
_BUT_, you have to know that with OpenOCD you will get 2 breakpoints
limit and there won't be eCos thread support (info threads) in GDB
with OpenOCD.

IMO, with RedBoot+GDB you can get more strong debug-engine for for
your target.

Sergei

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] LPC2XXX watchdog feeds and interrupts

[Laurie Gellatly]

Hi All,
I using an ARM 7 (LPC2212) based on an eCosCentric build. It appears that
watchdog feeds are done with interrupts enabled yet the NXP manual
warns against leaving interrupts enabled during a feed sequence (and I'm
pretty sure I've seen the consequences).
Firstly, have I missed something? Are interrupts disabled and I just don't
see where when I call watchdog_reset() 
OR
should I be adding cyg_interrupt_disable() and cyg_interrupt_enable() calls
around the feed sequence in watchdog_lpc2xxx.cxx

Thanks			...Laurie:{)



-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] RedBoot loading eCOS examples causes PC reboot

[peter_lanius]

On 2009-10-24, peter_lanius@yahoo.com.au <peter_lanius@yahoo.com.au> wrote:

>> I then use Hyperterminal to send the SREC file via Ymodem.
>> This process seems to run ok until it is finished, when the
>> suddenly PC reboots. That happens every time. No other
>> applications are open. The board is connected via a
>> USB-to-Serial cable and the Olimex JTAG ARM_USB_OCD is also
>> connected, but OpenOCD/GDB is not running.
>>
>> I have tried it with the ELF file as well, same result. 
>>
>> What am I doing wrong

> You're using Windows.

>> and why does the PC reboot?

> You're using Windows.  

> 1/2 ;)

> Seriously, it's a Windows problem.  Probably a bug in one of
> the of the USB-serial drivers (either the one for the
> ARM_USB_OCD adapter or the one for the USB-serial cable).  Try
> it without the ARM_USB_OCD plugged in.  Try it with a different
> USB-serial cable (one that uses a chip from a different
>vendor).

Yes, it was. It was the USB-serial cable. Replaced the cable, unplugged the JTAG for good measure and now works fine.

> It might also be Hyperterminal. Though it's a buggy piece of
> dreck, I don't think it's the cuplit in this case -- but you
> could try something like Teraterm.

> Or you could try using Linux...

Yep, done that. Have installed openSUSE and am now slowly migrating everything across... Haven't used Unix since 1993, so I am not rushing it :)

> -- 
> Grant

Thanks again
Peter


      __________________________________________________________________________________
Get more done like never before with Yahoo!7 Mail.
Learn more: http://au.overview.mail.yahoo.com/

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] Using openssl for HTTPS

[Laurie Gellatly]

Hi All,
I've looked at all types of examples but without luck.
I'm trying to setup eCos openSSL package so I can use HTTPS to my web
server.
The steps I'm using to bring up SSL so far are:
SSL_library_init()			// OK
Meth=SSLv23_server_method()		// OK
but when I do this next step
SSL_CTX_new(Meth)
I get a NULL (failed) response.

Does anyone have a working example they can share?
If the example happens to go into the certificates and keys (their setup,
format and functions that use them) that would be really excellent.

Thanks			...Laurie:{)


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] Re: Using openssl for HTTPS

[Kelvin Lawson]

Hi Laurie,

> Does anyone have a working example they can share?
> If the example happens to go into the certificates and keys (their setup,
> format and functions that use them) that would be really excellent.

A good example is the "wserver" code available from:
http://www.rtfm.com/openssl-examples/

Regards,
Kelvin.


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

RE: [ECOS] Re: Using openssl for HTTPS

[Laurie Gellatly]

Hi Kevin,
Thanks for the speedy reply.
Unfortunately I'd already seen (and have tried to follow) that page.
Now that I've slept on it I realized that I had unchecked some of the 
algorithms in the openSSL package. I've just put them all back in
(suffering quite an increase in code size) but at least the SSL_CTX_new
now passes and the complaint is now about my private key.

Does anyone know which algorithms are needed (or conversely which 
ones can be unchecked) for SSL to still work?

			...Laurie:{)

> -----Original Message-----
> From: ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss-
> owner@ecos.sourceware.org] On Behalf Of Kelvin Lawson
> Sent: Saturday, 31 October 2009 1:20 AM
> To: ecos-discuss@sources.redhat.com
> Subject: [ECOS] Re: Using openssl for HTTPS
> 
> Hi Laurie,
> 
> > Does anyone have a working example they can share?
> > If the example happens to go into the certificates and keys (their
> setup,
> > format and functions that use them) that would be really excellent.
> 
> A good example is the "wserver" code available from:
> http://www.rtfm.com/openssl-examples/
> 
> Regards,
> Kelvin.
> 
> 
> --
> Before posting, please read the FAQ:
> http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] Re: Using openssl for HTTPS

[Kelvin Lawson]

Hi Laurie,

> Thanks for the speedy reply.
> Unfortunately I'd already seen (and have tried to follow) that page.
> Now that I've slept on it I realized that I had unchecked some of the 
> algorithms in the openSSL package. I've just put them all back in
> (suffering quite an increase in code size) but at least the SSL_CTX_new
> now passes and the complaint is now about my private key.
> 
> Does anyone know which algorithms are needed (or conversely which 
> ones can be unchecked) for SSL to still work?

Looking back at my notes, I had everything under OpenSSL enabled except 
CYGPKG_OPENSSL_RC5 and CYGPKG_DES_READ_PWD. Some of these will be 
unnecessary but I was also experimenting with other techniques at the 
time. With this configuration the 'wserver' example I mentioned works 
perfectly.

Regards,
Kelvin.



>> -----Original Message-----
>> From: ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss-
>> owner@ecos.sourceware.org] On Behalf Of Kelvin Lawson
>> Sent: Saturday, 31 October 2009 1:20 AM
>> To: ecos-discuss@sources.redhat.com
>> Subject: [ECOS] Re: Using openssl for HTTPS
>>
>> Hi Laurie,
>>
>>> Does anyone have a working example they can share?
>>> If the example happens to go into the certificates and keys (their
>> setup,
>>> format and functions that use them) that would be really excellent.
>> A good example is the "wserver" code available from:
>> http://www.rtfm.com/openssl-examples/
>>
>> Regards,
>> Kelvin.
>>
>>
>> --
>> Before posting, please read the FAQ:
>> http://ecos.sourceware.org/fom/ecos
>> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 
> 


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

RE: [ECOS] Re: Using openssl for HTTPS

[Laurie Gellatly]

Thanks again Kevin,
I've left them all checked for the moment till I get it working.
Then I plan to trim down what I can.
To get the certificate and key in I'm using SSL_CTX_use_certificate_ASN1
and SSL_CTX_use_RSAPrivateKey_ASN1 as they could both take memory resident
values (prefer not to use any files). These two functions taking the same
parameters but in different order didn't help either.

I followed this site (among others) to generate certificates and keys :
http://www.eclectica.ca/howto/ssl-cert-howto.php
which I converted to DER types.
Not sure this helps but might help others :
http://www.mobilefish.com/developer/openssl/openssl_quickguide_command_examp
les.html
has an interesting flow diagram.

			...Laurie:{)


> -----Original Message-----
> From: ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss-
> owner@ecos.sourceware.org] On Behalf Of Kelvin Lawson
> Sent: Monday, 2 November 2009 7:58 PM
> To: ecos-discuss@sources.redhat.com
> Subject: [ECOS] Re: Using openssl for HTTPS
> 
> Hi Laurie,
> 
> > Thanks for the speedy reply.
> > Unfortunately I'd already seen (and have tried to follow) that page.
> > Now that I've slept on it I realized that I had unchecked some of the
> > algorithms in the openSSL package. I've just put them all back in
> > (suffering quite an increase in code size) but at least the
> SSL_CTX_new
> > now passes and the complaint is now about my private key.
> >
> > Does anyone know which algorithms are needed (or conversely which
> > ones can be unchecked) for SSL to still work?
> 
> Looking back at my notes, I had everything under OpenSSL enabled except
> CYGPKG_OPENSSL_RC5 and CYGPKG_DES_READ_PWD. Some of these will be
> unnecessary but I was also experimenting with other techniques at the
> time. With this configuration the 'wserver' example I mentioned works
> perfectly.
> 
> Regards,
> Kelvin.
> 
> 
> 
> >> -----Original Message-----
> >> From: ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss-
> >> owner@ecos.sourceware.org] On Behalf Of Kelvin Lawson
> >> Sent: Saturday, 31 October 2009 1:20 AM
> >> To: ecos-discuss@sources.redhat.com
> >> Subject: [ECOS] Re: Using openssl for HTTPS
> >>
> >> Hi Laurie,
> >>
> >>> Does anyone have a working example they can share?
> >>> If the example happens to go into the certificates and keys (their
> >> setup,
> >>> format and functions that use them) that would be really excellent.
> >> A good example is the "wserver" code available from:
> >> http://www.rtfm.com/openssl-examples/
> >>
> >> Regards,
> >> Kelvin.
> >>
> >>
> >> --
> >> Before posting, please read the FAQ:
> >> http://ecos.sourceware.org/fom/ecos
> >> and search the list archive: http://ecos.sourceware.org/ml/ecos-
> discuss
> >
> >
> 
> 
> --
> Before posting, please read the FAQ:
> http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] pthread_kill return value

[Jay Foster]

According to the man page for pthread_kill, the return value is supposed 
to be 0 on success and an error number (ESRCH, EINVAL) on error.  
However, the eCos implementation is returning 0 on success and -1 on 
error with errno set to the error number.  It looks like the eCos 
pthread_kill() function is using the SIGNAL_RETURN() macro when it 
should be using the SIGNAL_RETURN_VALUE() macro.

Am I reading this correctly?

Jay



-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] pthread_kill return value

[Bart Veer]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1494 bytes --]

>>>>> "Jay" == Jay Foster <jay@systech.com> writes:

    Jay> According to the man page for pthread_kill, the return value
    Jay> is supposed to be 0 on success and an error number (ESRCH,
    Jay> EINVAL) on error. However, the eCos implementation is
    Jay> returning 0 on success and -1 on error with errno set to the
    Jay> error number. It looks like the eCos pthread_kill() function
    Jay> is using the SIGNAL_RETURN() macro when it should be using
    Jay> the SIGNAL_RETURN_VALUE() macro.

    Jay> Am I reading this correctly?

According to
http://www.opengroup.org/onlinepubs/009695399/functions/pthread_kill.html
the man page is correct. I guess the eCos implementation should be
using SIGNAL_RETURN_VALUE() instead of SIGNAL_RETURN(). A patch would
be welcome. The only use of pthread_kill() in the eCos sources appears
to be in io/fileio, the pselect.c testcase, so that would need fixing
as well.

Bart

-- 
Bart Veer                                   eCos Configuration Architect
eCosCentric Limited    The eCos experts      http://www.ecoscentric.com/
Barnwell House, Barnwell Drive, Cambridge, UK.      Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
Besuchen Sie uns vom 2-4 März auf der Embedded World 2010, Stand 11-208
Visit us at Embedded World 2010, Nürnberg-Germany, 2-4 Mar, Stand 11-208

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss