[riot-devel] Regarding RNDIS support
Hello, As RIOT support Ethernet devices and USB device , Is someone working on rndis(Remote Network Driver Interface Specification) Protocol.?? Thanks Shishir Tiwari ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] one wire communication
Hello RIOTers, we are trying to communicating with DS2430A IC which support is one wire protocol. if anyone having some basic example of one wire protocol(reading/writing). please share with us. Thanks Shishir Tiwari ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] Regarding Hardware Timer
Hi All , I have configure one hardware timer and testing example hwtimer and hwtimer_spin. This is working and i just want to verify can you please provide me expected output of these examples . Readme are not available . Thanks Shishir tiwari ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Context Switching
Hi Murat,
Please first try Ipc_pingpong example . this will create 2 thread
message is transfer from one to another.
when RIOT initially starts up, the CPU is normally running in
interrupt mode (using the interrupt mode stack). After creating the
stacks for the main and the idle threads, the CPU must be put into
thread-mode. This means the main threads initial context needs to put
into the CPUs registers and the stack pointer must put to the
main-threads stack. After this is done the CPU can just do 'normal'
task switching for switching between threads.
So to put it short: in cpu_switch_context_exit() you simply must load
the main threads context into the CPUs register and point the stack
pointer to the main threads stack.
Thanks
Shishir tiwari
On Tue, Feb 10, 2015 at 12:03 AM, Murat CAKMAK m...@muratcakmak.net wrote:
Thanks Kaspar,
According to your explanations (Interrupting with ISR or higher priority),
RIOT works like as a single thread application.
I would expect a context switch mechanism for a quantum value even if
threads have same priority.
I have tried vtimer_usleep() method instead of my delay() function in two
thread.
static void *led3Thread(void *arg)
{
while (1)
{
LED3_Write(!LED3_Read());
vtimer_usleep(n); // Tried with 50, 100
}
}
static void *led4Thread(void *arg)
{
while (1)
{
LED4_Write(!LED4_Read());
vtimer_usleep(n); // Tried with 50, 100
}
}
After first call of vtimer_usleep(), execution is blocking (no changes on
leds) in vtimer_usleep() function.
For a single thread vtimer_usleep() function is working well.
FYI.
Murat.
-Original Message-
From: devel [mailto:devel-boun...@riot-os.org] On Behalf Of Kaspar Schleiser
Sent: Monday, February 9, 2015 8:02 PM
To: devel@riot-os.org
Subject: Re: [riot-devel] Context Switching
Hi Murat,
On 02/09/15 18:46, Murat CAKMAK wrote:
Threads looks like working as blocking. In general, led3Thread is
started before and only led3Thread is working. Never switch to
Led4Thread (I could not see changes on Led4).
If I dont create thread3, I can see changes on Led4.
So, Why am I not able to observe context switching? Is it normal
behaviour or not?
RIOT will only interrupt a running thread if an ISR occurs or a higher
priority thread becomes runnable. So what you see is expected behaviour.
Using vtimer_usleep should put the calling thread to sleep (if the delay is
high enough to not cause spin-locking). Could you try that with a fairly
high sleep time (e.g., a second)?
Kaspar
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] Adding new Wifi hardware support in RIoT
Hello, We are using a PMODWifi device [PmodWiFi - 802.11b WiFi Interface (MRF24WB0MA, b/g/n compatible)] on Synopsis ARC board and have succeded in initial port for RIoT on it. We wish to add support for the PMODWiFi module within RIoT stack. We see that there is a support for sixlowpan device (ieee802154) and the corresponding driver nrf24l01p into the stack. Current documentation on the portal or web doesn’t say anything about how we can add new network driver support. We wish to add 802.11 a/b/g support. It would be good if anyone would elaborate on how do we proceed with, and what kind of changes are required. Thanks BR, Shishir tiwari ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] thread is not working
Hi Petersen,
we are still facing issue for thread not working . we want to know how
the task get schedule and how it find the task_func entry point and
also how is switching happen.
please help on this.
Thanks
Shishir
On Wed, Jan 14, 2015 at 3:44 PM, Joakim Gebart joakim.geb...@eistec.se wrote:
You can look at the startup files for other CPUs for a proper way of doing
initialization e.g. cpu/stm32f1/startup.c
Note that you must also make sure that your linker script provides the
correct symbols at the beginning and end of .data and .bss.
Best regards,
Joakim Gebart
Eistec AB
www.eistec.se
On 01/13/2015 10:45 PM, Ryan Kurte wrote:
Hi Shishir,
I seem to recall having the same issue when starting the EFM32 port.
The issue in my case was that without the startup files, the .bss section
was not getting cleared.
When the threads came to launch, the value in one of the kernel functions
was not correct. Which is pretty easy to check with a debugger.
The fix was to clear the .bss section in the _init routine, my
implementation (using symbols from the linker) is:
//Clear bss
for (uint32_t i = (uint32_t)__bss_start__; i (uint32_t)__bss_end__;
i++) {
addr = (int*)i;
*addr = (int)NULL;
}
I am not sure this is the /correct/ way to do it, but the .bss definitely
needs to be initialised to zeros.
Hope that helps,
Ryan
On 14 January 2015 at 07:56, Hauke Petersen hauke.peter...@fu-berlin.de
wrote:
Hi,
On 13.01.2015 19:04, shishir tiwari wrote:
Hi petersen,
Thanks for your information.
we are trying to put your method but still is it not working. we are
studying and doing some experiments.
one more question : In hwtimer_init()-- hwtimer_arch_init() this need
to be implemented in harsware is compulsory?? for scheduling to work?
nope, the timer is generally not needed for scheduling.
Cheers,
Hauke
thanks
shishir tiwari
On Mon, Jan 12, 2015 at 10:01 PM, Hauke Petersen
hauke.peter...@fu-berlin.de wrote:
Hi Shishir,
when RIOT initially starts up, the CPU is normally running in interrupt
mode
(using the interrupt mode stack). After creating the stacks for the main
and
the idle threads, the CPU must be put into thread-mode. This means the
main
threads initial context needs to put into the CPUs registers and the
stack
pointer must put to the main-threads stack. After this is done the CPU
can
just do 'normal' task switching for switching between threads.
So to put it short: in cpu_switch_context_exit() you simply must load
the
main threads context into the CPUs register and point the stack pointer
to
the main threads stack.
Let me know if you need further information!
Cheers,
Hauke
On 12.01.2015 15:35, shishir tiwari wrote:
Hey Everyone,
I have been porting RIOT OS to new processor(ARC) and i had compilied
hello world program successfully.
When i debug the helloworld.elf in kernel_init function the
thread_create() function has execute successfully.But the thread
idle_thread and main_trampoline function is not been called. why?
What is thing need to be done on this cpu_switch_context_exit()
function. please explain me.
Thanks
Shishir Tiwari
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] thread is not working
Hey Everyone, I have been porting RIOT OS to new processor(ARC) and i had compilied hello world program successfully. When i debug the helloworld.elf in kernel_init function the thread_create() function has execute successfully.But the thread idle_thread and main_trampoline function is not been called. why? What is thing need to be done on this cpu_switch_context_exit() function. please explain me. Thanks Shishir Tiwari ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] RIOT Porting other platform
Hi Thomas , I am new to Riot , so can you please share sequence of program (function) execution for staring reset(startup) to main(application ) program. This is will help to port into new platform. Thanks Shishir tiwari On Wed, Dec 31, 2014 at 4:59 AM, Thomas Eichinger thomas.eichin...@fu-berlin.de wrote: Hi Shishir, On 30 Dec 2014, at 12:04, shishir tiwari sumit.tiwari1...@gmail.com wrote: Is Porting for ARC600/ ARC700 (Synopsys) has been done. Any idea? As far as I know nobody started to port RIOT to Synopsys processors although they seem quite interesting to me. Although, I don’t know how to get them samples/DKs without of industrial context. If you have any plans into this direction please share them on this list and we’d be happy to support you as much as possible. Best, Thomas ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] RIOT Porting other platform
hi Ludwig, Is Porting for ARC600/ ARC700 (Synopsys) has been done. Any idea? Thanks Shishir tiwari On Wed, Dec 24, 2014 at 8:13 PM, Ludwig Ortmann ludwig.ortm...@fu-berlin.de wrote: Hello Shishir, Please have a look at the porting guide in our wiki: https://github.com/RIOT-OS/RIOT/wiki/Porting-Guide Also keep in mind that all files have to have an LGPL 2.1 compatible license. Finally, you should look at the development procedures and coding conventions: https://github.com/RIOT-OS/RIOT/wiki/Development-procedures https://github.com/RIOT-OS/RIOT/wiki/Coding-conventions Happy hacking! Cheers, Ludwig Am 24. Dezember 2014 15:24:01 MEZ, schrieb shishir tiwari sumit.tiwari1...@gmail.com: Hi All , I want to port RIOT OS to new platform (ARC 600 microncontroller ). What is need to done. Any documentation is available for this. thanks ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] RIOT Porting other platform
Hi All , I want to port RIOT OS to new platform (ARC 600 microncontroller ). What is need to done. Any documentation is available for this. thanks ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
