Richard Rauch | 23 May 2013 12:49
Picon

Found problem in Thread class implementation

Hi,

maybe I found a problem in schedulers code....

For debugging purposes I enabled some options:

- CYGVAR_KERNEL_THREADS_LIST
- CYGDBG_KERNEL_DEBUG_GDB_THREAD_SUPPORT

On application startup some threads should be created, but I am running in
an exception. The reason of exception is located here:

inline void
Cyg_Thread::add_to_list( void )
{
    // Add thread to housekeeping list
    Cyg_Scheduler::lock();

    if( thread_list == 0 )
        list_next = this;
    else {
        Cyg_Thread *prev = thread_list;
        do {
            if ( this == prev )
                break; // found it already!
            prev = prev->list_next;
        } while ( prev != thread_list );
        if ( this != prev ) {
            // insert it in the list:
            list_next = thread_list->list_next;
(Continue reading)

yusuf.husainy | 23 May 2013 09:27
Picon

ecos configuration for LPC1769

Hi all,

I have just started with eCos recently. I am using a custom board with
LPC1769 on it. My requirement is that I have to build and port redboot to
the internal flash of LPC1769. This will then serve as a purpose to load any
other application(firmware or ecos linked application) to my board via the
ethernet connection or UART.

So, I downloaded eCos3.0, and also ecos from anoncvs. Then I followed the
instructions told on that webpage and changed my repository to the anoncvs
one.  export ECOS_REPOSITORY=/mnt/ecoCVS/ecos/packages.

After that I executed the config tool for ecos3.0, and selected te Olimex
1766-STK as my board. But, I need it for 1769, So, what I would like to know
is that, before building redboot(as selected from template menu), where
should I make some modifications so that I will be able to use my custom
board using LPC1769.

Any help is appreciated.

Regards,
Yusuf Husainy.

--
View this message in context: http://sourceware-org.1504.n7.nabble.com/ecos-configuration-for-LPC1769-tp233012.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.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
(Continue reading)

Felix R | 21 May 2013 17:44
Favicon

how to call mount() in cyg_start()

Hi,

i i call mount() in he main function (like in the fatfs1 test), it works.
But if i want i use threads i dont havte main() ant i want to call it in
cyg_start(). this fails wih this assert:

ASSERT FAIL: <1>disk.c[370]disk_connected() Bad LBA sector count
ASSERT FAIL: <1>disk.c              [ 370] disk_connected()                                                                                    
Bad LBA sector count

Note: I am mounting a SD-Card.

Thanks
Felix

--
View this message in context: http://sourceware-org.1504.n7.nabble.com/how-to-call-mount-in-cyg-start-tp232754.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.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

张天勇 | 21 May 2013 08:31
Picon

questrons about pc jump from rom to ram

Hi all
I am working on the stm32f207zg board, and going to develop a
bootloader myself which works same as redboot.The loader will receive
the executable through the net and save which to the ram, and then
jump PC from ROM to RAM to execute the new executable.
In case of redboot,after load a new executable to the ram, type the
commend of go 0x64008011, then the new executable in RAM works.
But in case of my bootloader, i use the following code to realize the
same job. Disable the interrupt first, jump sp to the top of ram then
, and finally jump pc to the entry address of executable in ram.
HAL_DISABLE_INTERRUPTS(oldints);
__asm__ volatile("ldr sp,=0x64800000" );
(*(void (*)(void))(0x64008011))();
But it cannot work. so,would anybody give me some advice,thanks very much!

--

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

Ilija Kocho | 20 May 2013 14:05
Picon

Re: 回复:[ECOS] Re: How to use TWR-K60N512's GPIO in user app

On 20.05.2013 13:48, xfce <at> sina.com wrote:
> Dear ilijak,
>
>     For the TWR-K60N512 target,If I want to set a GPIO for input, and how to set the input as pull up or pull down?
Thanks 

As it suits you. If you have a button, normally it should be tied to the
opposite rail then the button. Then you don't need external resistor. If
you have external resistor than you need no pull.

HTH

Ilija

>
> ----- 原始邮件 -----
> 发件人:Ilija Kocho <ilijak <at> siva.com.mk>
> 收件人:xfce <at> sina.com
> 抄送人:ecos-discuss <ecos-discuss <at> sourceware.org>
> 主题:[ECOS] Re: How to use TWR-K60N512's GPIO in user app
> 日期:2013年05月17日 21点13分
> On 17.05.2013 02:38, xfce <at> sina.com wrote:
>> Dear ilijak
>> I want to use the TWR-K60N512's GPIO in my app.c
>>
>> below is some of my codes, and it can't work correctly,could you
>> please tell me where is the bug,thanks.
>>
>> #include <cyg/hal/var_io.h> //gpio function header file
>>
(Continue reading)

Leonardo Passos | 17 May 2013 20:53
Picon

CYGPKG_OBJLOADER vs CYGPKG_LOADER

Hi,

I would like to understand the difference between CYGPKG_OBJLOADER and
CYGPKG_LOADER, as their description in the CDL script are similar, and
the eCos reference manual does not provide further insights.

Regards.

--

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

Ilija Kocho | 17 May 2013 15:13
Picon

Re: How to use TWR-K60N512's GPIO in user app

On 17.05.2013 02:38, xfce <at> sina.com wrote:
> Dear ilijak
> I want to use the TWR-K60N512's GPIO in my app.c
>
> below is some of my codes, and it can't work correctly,could you
> please tell me where is the bug,thanks.
>
> #include <cyg/hal/var_io.h> //gpio function header file
>
> //set the PORTA bit_19 and bit_11 as GPIO function
> #define KEY1_GPIO_ENABLE CYGHWR_HAL_KINETIS_PIN(A, 19,
> CYGHWR_HAL_KINETIS_PORT_PCR_MUX_GPIO,
> CYGHWR_HAL_KINETIS_PORT_PCR_PE_M) //KEY1
> #define LED1_GPIO_ENABLE CYGHWR_HAL_KINETIS_PIN(A, 11,
> CYGHWR_HAL_KINETIS_PORT_PCR_MUX_GPIO,
> CYGHWR_HAL_KINETIS_PORT_PCR_PE_M) //LED1
>
> //set the GPIO as INPUT and OUTPUT
> #define KEY1_INPUT_ENABLE CYGHWR_HAL_KINETIS_GPIO_PIN_DDR_IN(A, 19)
> #define LED1_OUTPUT_ENABLE CYGHWR_HAL_KINETIS_GPIO_PIN_DDR_OUT(A, 11)
>
> //get the input value
> #define GET_KEY1_VALUE CYGHWR_HAL_KINETIS_GPIO_GET_PIN(A, 19)
>
> //set the output high or low
> #define LED1_OUTPUT_H CYGHWR_HAL_KINETIS_GPIO_SET_PIN(A, 11)
> #define LED1_OUTPUT_L CYGHWR_HAL_KINETIS_GPIO_CLEAR_PIN(A, 11)
>
> //gpio test function
> void cyg_user_start(void)
(Continue reading)

Max Seidenstücker | 15 May 2013 17:49

JFFS2 on NOR flash with ECC

Hi folks,

we are using a µC that has ECC calculation on an 8 Byte boundary in
its NOR flash storage. After taking a glance at the JFFS2 eCos port
and the most recent Linux version I am a little lost on how to get the
fastest solution to solve this.

The problem with ECC'd NOR is that the obsolete-flag cannot be
written. ECC is calculated after the initial write, so even this one
bit flip results in an ECC error.

Unfortunately the eCos port of JFFS2 doesn't support NAND flash and
Linux MTD, where the NOR ECC patches
(http://mhonarc.axis.se/jffs-dev/msg01398.html) would be easily ported
to.

So I see two possible approaches:
1. Add JFFS2 NAND support to eCos by updating JFFS2 to the newest
version, which also incorporates adaption of the Linux MTD stuff
2. Increment the obsolete marker to 8 Byte and align it on an 8 Byte
boundary so a obsolete marker will write to a formerly unwritten 8
Byte sector and make sure the flash writes are 8 Byte aligned.

I would like to go with the second approach as it looks faster, but
don't know if this easy to achieve.

Any ideas or help on how to do that, is highly appreciated.

Cheers Max

(Continue reading)

EnneGi | 15 May 2013 17:02
Picon

lwIP for eCos (LPC1768)

Hi all, i'm in trouble with lwIP. I'm trying the examples of lwIP for eCos SO
on my board (LPC1768 , a cortexM board). I found any examples of lwIP in
eCos repository

(you find it here: https://www.dropbox.com/s/fn1qp2pt70sfnw2/tests.zip ) 

in particular, I try the httpd_simple.c example. It compiles and works on my
board, but I can't test it with a connection by ethernet between board and
pc. My computer doesn't link to a board.

I set a static ip address by configtools, but it doesn't works.
My question is: 
how can I test httpd_simple?

Thanks. 

--
View this message in context: http://sourceware-org.1504.n7.nabble.com/lwIP-for-eCos-LPC1768-tp231949.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.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

Felix R | 14 May 2013 12:52
Favicon

building/running tests without RedBoot

Hi,

If i want to run and debug the tests as an demo application i usually copy
the file to my SDK, remove/replace the CYG_TEST_ Macros and i can run it.
Mostly i works but now i didn't.

building the \ecos\packages\io\fileio\current\tests\stdio.c gives me
"undefined reference to fopen" (and all other stdio.h funcions) whereas it
builds and runs with "build tests" and loading the executable with my jtag
adapter. The library is linked correctly.

What do i have to look after when building tests this way?

Thanks,
Felix

--
View this message in context: http://sourceware-org.1504.n7.nabble.com/building-running-tests-without-RedBoot-tp231726.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.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

Felix R | 14 May 2013 11:39
Favicon

Cant break in eCos-Library

Hi,

i have some issues with the eCos Lib in the (eclipse based) Xilinx SDK.
Breakpoints in sources inside the library are skipped. Why?

When i set a breakpoint in my source, it will break. I can step into the
library and set a breakpoint there. If i run again, it does no break there.
In the Breakpoints window, you can see a blue check next to the working
breakpoints, whereas the others don have this check.

I am using the onboard JTAG adapter on the zedboard for debugging. Redboot
is ot used.

Thanks,
Felix

--
View this message in context: http://sourceware-org.1504.n7.nabble.com/Cant-break-in-eCos-Library-tp231717.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.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


Gmane