Re: [riot-devel] Oneway-Malloc

[Carsten Bormann]

Carsten Bormann wrote:
> https://twitter.com/c4bo/status/676393852798922752

OK, that may have been a bit opaque :-)

http://www.barrgroup.com/Embedded-Systems/How-To/Malloc-Free-Dynamic-Memory-Allocation
http://www.embedded.com/design/programming-languages-and-tools/4416457/EMB-tm-6-15-13-Dynamic-memory-and-heap-contiguity
http://stackoverflow.com/questions/1725923/how-bad-is-it-to-use-dynamic-datastuctures-on-an-embedded-system
http://www.nongnu.org/avr-libc/user-manual/malloc.html

If you really need dynamic memory for some algorithm, consider an arena
allocator.
https://en.wikipedia.org/wiki/Region-based_memory_management

Grüße, Carsten
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Oneway-Malloc

[Carsten Bormann]

https://twitter.com/c4bo/status/676393852798922752

:-)

Grüße, Carsten


Sam Kumar wrote:
> Hello,
> I noticed that there is a "oneway-malloc" module in RIOT OS. It appears
> to be a thin wrapper around sbrk that only supports allocating memory,
> not freeing it.
> 
> I am doing some development using RIOT OS, and dynamic memory allocation
> would be useful to me. Is there already a module that implements dynamic
> memory allocation suitable for general-purpose use in the kernel and in
> user programs?
> 
> If such a module does not already exist, I am willing to contribute a
> lightweight implementation of malloc, realloc, calloc, and free to
> replace the oneway-malloc module.
> 
> Sam Kumar
> 
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Disable 15.4 Acknowledgements

[Peter Kietzmann]

Hi,

NETOPT_ACK_REQ is currently not handled by the at86rf2xx driver but IIRC 
NETOPT_AUTOACK covers both for that device (didn't check that).


Best
Peter

Am 09.08.2016 um 16:44 schrieb Simon Brummer:

Hi Oleg,


netopt_enable_t opt = NETOPT_DISABLE;
gnrc_netif_get(ifs);
gnrc_netapi_set(ifs[0], NETOPT_AUTOACK, 0, , sizeof(opt));
gnrc_netapi_set(ifs[0], NETOPT_ACK_REQ, 0, , sizeof(opt));


Did the trick. So there is a way to disable acknowledgements.

Cheers,

Simon

Am Dienstag, den 09.08.2016, 16:40 +0200 schrieb Oleg Hahm:

Hi Simon!

On Tue, Aug 09, 2016 at 02:33:56PM +0200, simon wrote:


Currently I am testing my TCP implementation between two samr21
Boards
and a Raspberry Pi as sniffing Probe in between.

My measured network dump contains a few unexpected retransmissions
and
i am unable to distinguish between retransmissions caused by 15.4
and
retransmissions caused by TCP. Is there a way to disable the 15.4
acknowledgement and retransmission mechanism?


IIRC auto acknowledgement can currently not be disabled with the
at86rf2xx
driver, but you can set the retransmissions to zero. You can do this
either
using the shell:

 ifconfig 7 set retrans 0

or directly via netapi:

 gnrc_netapi_set(CCNLRIOT_NETIF, NETOPT_CSMA_RETRIES, 0, 0,
sizeof(uint8_t));

Cheers,
Oleg
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel



--
Peter Kietzmann

Hamburg University of Applied Sciences
Dept. Informatik, Internet Technologies Group
Berliner Tor 7, 20099 Hamburg, Germany
Fon: +49-40-42875-8426
Web: http://www.haw-hamburg.de/inet
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Disable 15.4 Acknowledgements

[Oleg Hahm]

Hi Simon!

On Tue, Aug 09, 2016 at 04:44:40PM +0200, simon wrote:
> netopt_enable_t opt = NETOPT_DISABLE;
> gnrc_netif_get(ifs);
> gnrc_netapi_set(ifs[0], NETOPT_AUTOACK, 0, , sizeof(opt));
> gnrc_netapi_set(ifs[0], NETOPT_ACK_REQ, 0, , sizeof(opt));
> 
> 
> Did the trick. So there is a way to disable acknowledgements.

Have you checked if this actually works (i.e. no more ACKs are sent)?

If yes, cool and sorry for my wrong statement.

Cheers,
Oleg
-- 
gur orfg guvat nobhg EBG13 wbxrf vf, rirelbar unf gb qvt hc gurve 20 lrne byq
pbairegref


signature.asc
Description: PGP signature
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] qemu-i386 port

[Oleg Hahm]

Hi Ludwig!

On Tue, Aug 09, 2016 at 02:30:25PM +0200, Ludwig Knüpfer wrote:
> Without any further insights I would say your case is different because the
> board is actively maintained, used, and can be bought.
> In the case of the FU boards I had in mind (msb430*) none of these points is 
> true.

While I agree with your assessment, I don't think we should drop support for
MSB430 platforms. First, we have plenty of them in Berlin and Hamburg and I
will happily lend them to anyone asking for it. Second, they are (or at least
were) used in other academic institutes in WSN area. Finally, they are very
similar to widely used platforms such as TelosB or WSN430 and the additional
maintenance effort is really small. However, we definitely should try harder
to get a better support for MSP430 platforms in general.

Cheers,
Oleg
-- 
printk("NULL POINTER IDIOT\n");
linux-2.6.6/drivers/media/dvb/dvb-core/dvb_filter.c


signature.asc
Description: PGP signature
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Disable 15.4 Acknowledgements

[Oleg Hahm]

Hi Simon!

On Tue, Aug 09, 2016 at 02:33:56PM +0200, simon wrote:
> Currently I am testing my TCP implementation between two samr21 Boards
> and a Raspberry Pi as sniffing Probe in between.
> 
> My measured network dump contains a few unexpected retransmissions and
> i am unable to distinguish between retransmissions caused by 15.4 and
> retransmissions caused by TCP. Is there a way to disable the 15.4
> acknowledgement and retransmission mechanism?

IIRC auto acknowledgement can currently not be disabled with the at86rf2xx
driver, but you can set the retransmissions to zero. You can do this either
using the shell:
 
 ifconfig 7 set retrans 0

or directly via netapi:

 gnrc_netapi_set(CCNLRIOT_NETIF, NETOPT_CSMA_RETRIES, 0, 0, sizeof(uint8_t));

Cheers,
Oleg
-- 
Chuck Norris doesn't do TCP handshake - he does TCP roundhouse-kick to initiate
the connection.


signature.asc
Description: PGP signature
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] qemu-i386 port

[Marc]

[ek-lm4f120-xl board can't be bought anymore, only its replacement TivaC can 
(and it is not supported by RIOT, at least at the moment)]

It is actively maintained... sort of. I have the feeling that no RIOT developer 
has time for it. It is not listed on the RIOT wiki and it is hard to find 
someone with time and hw.
If that's considered normal, then so be it and I'll happily continue to ping my 
PRs from time to time. I may even contribute a wiki page for it :)

Sorry if this subject is considered OT,
Cheers,

Marc

August 9 2016 2:30 PM, "Ludwig Knüpfer"  wrote:
> Hi,
> 
> Without any further insights I would say your case is different because the 
> board is actively
> maintained, used, and can be bought.
> In the case of the FU boards I had in mind (msb430*) none of these points is 
> true.
> 
> Cheers,
> Ludwig
> 
> Am 9. August 2016 14:21:44 MESZ, schrieb Marc :
> 
>> Hey,
>> 
>> This discussion is also related to
>> https://github.com/RIOT-OS/RIOT/pull/5412#issuecomment-237688208
>> I'm trying to enhance support for ek-lm4fxl-120 board, which is not as
>> popular as stm boards...
>> It's a bit complicated to find reviewers with some extra time for
>> reviewing, and even more for hardware testing...
>> 
>> Would it be possible to have an in-between set of boards (between "well
>> supported/tested" and "in
>> the trash") ? Where reviewers could omit the hardware tests for example
>> and rely on the "community"
>> to do such tests ?
>> 
>> I must admit that having to spend several weeks for each small PR is a
>> bit frustrating, but I fully
>> understand that nobody really cares about this board. If this is not
>> possible, then maybe you're
>> right and boards that can't be maintained should be ditched. People can
>> still maintain their own
>> fork (what I'll probably do for TivaC board).
>> 
>> Marc
>> 
>> August 9 2016 2:06 PM, "Ludwig Knüpfer" 
>> wrote:
>> 
>>> Hi,
>>> 
>>> I'm all for cleaning up stale boards, especially I'd they are as hard
>> 
>> to obtain as for example the
>>> FU boards.
>>> If I'm not mistaken this would also enable the removal of at least
>> 
>> one legacy driver interface (I
>>> have some GPIO API in mind).
>>> 
>>> Cheers,
>>> Ludwig
>>> 
>>> Am 9. August 2016 13:52:56 MESZ, schrieb "Joakim Nohlgård"
>> 
>> :
 I agree with dropping qemu-i386
 
 On the same subject, would it make sense to clean up some other
>> 
>> boards
 with less than ideal support?
 chronos is one board which I frequently run into trouble with
>> 
>> because
 it is never up to date with the other platform implementations,
 especially the stdio is very hacky on that board.
 
 /Joakim
 
 On Aug 9, 2016 12:51, "Martine Lenders" 
>> 
>> wrote:
> Hi,
> we now have the third person wondering about the qemu-i386 port.
>> 
>> Fact
> is, it doesn't work (we do not even have the unittests activated
> anymore). Is there a reason why we did not drop it yet (except
>> 
>> making
> all the good work by René void)? Or are we planning to provide
>> 
>> better
> support for it in the future?
> 
> Cheers,
> Martine
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
 
 ___
 devel mailing list
 devel@riot-os.org
 https://lists.riot-os.org/mailman/listinfo/devel
>>> 
>>> ___
>>> devel mailing list
>>> devel@riot-os.org
>>> https://lists.riot-os.org/mailman/listinfo/devel
>> 
>> ___
>> devel mailing list
>> devel@riot-os.org
>> https://lists.riot-os.org/mailman/listinfo/devel
> 
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] Disable 15.4 Acknowledgements

[Simon Brummer]

Hello Everybody,

Currently I am testing my TCP implementation between two samr21 Boards
and a Raspberry Pi as sniffing Probe in between.

My measured network dump contains a few unexpected retransmissions and
i am unable to distinguish between retransmissions caused by 15.4 and
retransmissions caused by TCP. Is there a way to disable the 15.4
acknowledgement and retransmission mechanism?

Thanks, Simon
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] Directions on how to setup a test environment for RIOTOS (Real Time OS for tiny embedded devices)

[Steven Anderson]

Hi I have performed the following in order to setup a test network of
devices on Ubuntu 14.04 with Vagrant and vbox. (see below)

I am getting the following error:

ifconfig 4 add 2001:db8::1
error: unable to add IPv6 address.
I cant get around this.
I believe I am using the native chipset in order to work on Linux.

Please take a look and tell me what I am doing wrong.

Thanks in advance!

Steven



Directions on how to setup a test environment for
RIOTOS (Real Time OS for tiny embedded devices)

install Ubuntu 14.04
http://releases.ubuntu.com/14.04/ubuntu-14.04.5-desktop-amd64.iso and burn
it to a  CD install it on a x86_64 bit machine

Install VirtualBox 4.3
https://www.virtualbox.org/wiki/Download_Old_Builds_4_3

install "VirtualBox Extension Pack 4.3"
https://www.virtualbox.org/wiki/Download_Old_Builds_4_3

Install vagrant (DONT DO sudo apt-get install vagrant ) instead do
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade
WARNING: do not upgrade to later version of ubuntu if it asks!
sudo apt-get install wget build-essential subversion git
linux-header-`uname -r' nano gedit
cd /home//Downloads
mkdir vagrant
cd vagrant
wget https://releases.hashicorp.com/vagrant/1.8.5/vagrant_1.8.5_x86_64.deb
sudo dpkg -i vagrant_1.8.5_x86_64.deb
mkdir /home//Downloads/RIOT-OS
cd /home//Downloads/RIOT-OS
git clone --recursive https://github.com/RIOT-OS/Tutorials
git clone git://github.com/RIOT-OS/RIOT.git
cd /home//Downloads/RIOT-OS/RIOT
NOTE: if your computer does not have USB3 then you will need to do the
following
gedit Vagrantfile
find the line that reads
vb.customize ["modifyvm", :id, "--usbxhci", "on"]

and comment it out by putting a # sign in front of it
#vb.customize ["modifyvm", :id, "--usbxhci", "on"]
this fixes a usb3 error that is generated by vagrant and vbox

The following commands must be run from the RIOT-OS root directory on the
host system. This will set the ability to name a terminal with set-title
command inside terminal on Ubuntu install. NOTE: This is different than the
repeat of this step you are going to do for Vagrant VM inside vbox. More
info on this helpful shortcut can be found here:
http://unix.stackexchange.com/questions/177572/how-to-rename-terminal-tab-title-in-gnome-terminal
This seems like a lot of work but it actually saves lots of confusion later
on.
gedit /home//.bashrc
at the bottom of the .bashrc file that appears type
function set-title() {
  if [[ -z "$ORIG" ]]; then
ORIG=$PS1
  fi
  TITLE="\[\e]2;$*\a\]"
  PS1=${ORIG}${TITLE}
}

save the .bashrc and exit

NOW you will open terminal tabs one for each of the RIOTOS devices you wish
to create. For ease of use open them as tabs. DO this by opening a terminal
and then go to FILE-Open TAB on Ubuntu Desktop. For example,VirtualBox I
wanted to have 4 devices with 4 tap interfaces so I opened 4 terminals.
After you open the terminals
go into each terminal and type set-title RIOT-OS tap{0,1,2,3,4}...number of
terminals consecutively one in each terminal for example set-title RIOT-OS
tap0 or in next terminal set-title RIOT-OS tap1,  etc...etc.

vagrant up
This will start up the virtual machine and download the Ubuntu image as
well as all necessary toolchains.
This will download and build a VirtualBox VM with Ubuntu 15.04 in it for
use as a platform for RIOTOS, it will then build RIOTOS inside the VM
assuming all goes well
You will do the next step once for each of the instances of native RIOTOS
hardware instances you wish to create.
If your not there already type
cd /home//Downloads/RIOT-OS/RIOT (you should be here)
type:
vagrant ssh

>
For the very first time after building with vagrant up or after a vagrant
destroy you will need to edit the .bashrc in the vagrant / VirtualBox VM
gedit /home/vagrant/.bashrc
at the bottom of the .bashrc file that appears type
function set-title() {
  if [[ -z "$ORIG" ]]; then
ORIG=$PS1
  fi
  TITLE="\[\e]2;$*\a\]"
  PS1=${ORIG}${TITLE}
}

save the .bashrc and exit

>

cd /home/vagrant/RIOT/dist/tools/tapsetup
./tapsetup -c 10 where -c 10 is the number of virtual different boards you
want

[NOTE: if you previously created a tap interface you will need
./tapsetup -d to delete other tap interface ]
cd /home/vagrant/RIOT/examples/default
type in:  make all term
wait a minute and hit enter to bring up prompt >
BEGIN REPEAT SECTION:
For each of the ./tapsetup -c 10 ←-- do the following
open a new terminal on your desktop (not the VirtualBox VM created early
but on the actual desktop)
In the terminal type:
set-title RIOT-OS tap<0>  where <0> is the number of
the tap interface  this will name the terminal
according to which tap interface you are accessing. More info on this
helpful shortcut can be found here:
http://unix.stackexchange.com/questions/177572/how-to-rename-terminal-tab-title-in-gnome-terminal

cd /home//Downloads/RIOT-OS/RIOT
vagrant ssh (this puts you into the vagarant vm running on vbox)

In the terminal type:
set-title RIOT-OS tap<0>  where <0> is the number of 

Re: [riot-devel] qemu-i386 port

[Marc]

Hey,

This discussion is also related to 
https://github.com/RIOT-OS/RIOT/pull/5412#issuecomment-237688208
I'm trying to enhance support for ek-lm4fxl-120 board, which is not as popular 
as stm boards...
It's a bit complicated to find reviewers with some extra time for reviewing, 
and even more for hardware testing...

Would it be possible to have an in-between set of boards (between "well 
supported/tested" and "in
the trash") ? Where reviewers could omit the hardware tests for example and 
rely on the "community"
to do such tests ?

I must admit that having to spend several weeks for each small PR is a bit 
frustrating, but I fully
understand that nobody really cares about this board. If this is not possible, 
then maybe you're
right and boards that can't be maintained should be ditched. People can still 
maintain their own
fork (what I'll probably do for TivaC board).

Marc

August 9 2016 2:06 PM, "Ludwig Knüpfer"  wrote:

> Hi,
> 
> I'm all for cleaning up stale boards, especially I'd they are as hard to 
> obtain as for example the
> FU boards.
> If I'm not mistaken this would also enable the removal of at least one legacy 
> driver interface (I
> have some GPIO API in mind).
> 
> Cheers,
> Ludwig
> 
> Am 9. August 2016 13:52:56 MESZ, schrieb "Joakim Nohlgård" 
> :
> 
>> I agree with dropping qemu-i386
>> 
>> On the same subject, would it make sense to clean up some other boards
>> with less than ideal support?
>> chronos is one board which I frequently run into trouble with because
>> it is never up to date with the other platform implementations,
>> especially the stdio is very hacky on that board.
>> 
>> /Joakim
>> 
>> On Aug 9, 2016 12:51, "Martine Lenders"  wrote:
>>> Hi,
>>> we now have the third person wondering about the qemu-i386 port. Fact
>>> is, it doesn't work (we do not even have the unittests activated
>>> anymore). Is there a reason why we did not drop it yet (except making
>>> all the good work by René void)? Or are we planning to provide better
>>> support for it in the future?
>>> 
>>> Cheers,
>>> Martine
>>> ___
>>> devel mailing list
>>> devel@riot-os.org
>>> https://lists.riot-os.org/mailman/listinfo/devel
>> 
>> ___
>> devel mailing list
>> devel@riot-os.org
>> https://lists.riot-os.org/mailman/listinfo/devel
> 
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] qemu-i386 port

[Oleg Hahm]

Hey!

On Tue, Aug 09, 2016 at 02:06:07PM +0200, Ludwig Knüpfer wrote:
> I'm all for cleaning up stale boards, especially I'd they are as hard to
> obtain as for example the FU boards.

Well, hopefully this situation is about to change once the RasPi
infrastructure is in place.

Cheers,
Oleg
-- 
Yo mamma is so fat that she sat on a binary tree and made it a linked list in
constant time.


signature.asc
Description: PGP signature
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] qemu-i386 port

[Ludwig Knüpfer]

All of them?

Am 9. August 2016 14:11:12 MESZ, schrieb Martine Lenders 
:
>Hi Ludwig,
>well at least the FU boards are now "obtainable" through the IoT-Lab
>testbed. ;-)
>
>Cheers,
>Martine
>
>2016-08-09 14:06 GMT+02:00 Ludwig Knüpfer
>:
>> Hi,
>>
>> I'm all for cleaning up stale boards, especially I'd they are as hard
>to obtain as for example the FU boards.
>> If I'm not mistaken this would also enable the removal of at least
>one legacy driver interface (I have some GPIO API in mind).
>>
>> Cheers,
>> Ludwig
>>
>> Am 9. August 2016 13:52:56 MESZ, schrieb "Joakim Nohlgård"
>:
>>>I agree with dropping qemu-i386
>>>
>>>On the same subject, would it make sense to clean up some other
>boards
>>>with less than ideal support?
>>>chronos is one board which I frequently run into trouble with because
>>>it is never up to date with the other platform implementations,
>>>especially the stdio is very hacky on that board.
>>>
>>>/Joakim
>>>
>>>On Aug 9, 2016 12:51, "Martine Lenders" 
>wrote:

 Hi,
 we now have the third person wondering about the qemu-i386 port.
>Fact
 is, it doesn't work (we do not even have the unittests activated
 anymore). Is there a reason why we did not drop it yet (except
>making
 all the good work by René void)? Or are we planning to provide
>better
 support for it in the future?

 Cheers,
 Martine
 ___
 devel mailing list
 devel@riot-os.org
 https://lists.riot-os.org/mailman/listinfo/devel
>>>___
>>>devel mailing list
>>>devel@riot-os.org
>>>https://lists.riot-os.org/mailman/listinfo/devel
>>
>> ___
>> devel mailing list
>> devel@riot-os.org
>> https://lists.riot-os.org/mailman/listinfo/devel
>___
>devel mailing list
>devel@riot-os.org
>https://lists.riot-os.org/mailman/listinfo/devel

___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Απ: Απ: Απ: Απ: Problem with "make" -lm missing.

[Laurent Navet]

> P.S: Anyone who have tried to run an app on Arduino Uno, please be kind to 
> tell me if they succeed!

What I have personnaly tested on real hardware and works fine is :
 - hello_world
 - timer_periodic_wakeup
 - ipc_pingpong

from RIOT/examples/ directory

-- 
« On ne résout pas un problème avec les modes de pensée qui l’ont engendré. »
« You cannot solve current problems with current thinking. Current
problems are the result of current thinking »
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] qemu-i386 port

[Martine Lenders]

Hi Ludwig,
well at least the FU boards are now "obtainable" through the IoT-Lab
testbed. ;-)

Cheers,
Martine

2016-08-09 14:06 GMT+02:00 Ludwig Knüpfer :
> Hi,
>
> I'm all for cleaning up stale boards, especially I'd they are as hard to 
> obtain as for example the FU boards.
> If I'm not mistaken this would also enable the removal of at least one legacy 
> driver interface (I have some GPIO API in mind).
>
> Cheers,
> Ludwig
>
> Am 9. August 2016 13:52:56 MESZ, schrieb "Joakim Nohlgård" 
> :
>>I agree with dropping qemu-i386
>>
>>On the same subject, would it make sense to clean up some other boards
>>with less than ideal support?
>>chronos is one board which I frequently run into trouble with because
>>it is never up to date with the other platform implementations,
>>especially the stdio is very hacky on that board.
>>
>>/Joakim
>>
>>On Aug 9, 2016 12:51, "Martine Lenders"  wrote:
>>>
>>> Hi,
>>> we now have the third person wondering about the qemu-i386 port. Fact
>>> is, it doesn't work (we do not even have the unittests activated
>>> anymore). Is there a reason why we did not drop it yet (except making
>>> all the good work by René void)? Or are we planning to provide better
>>> support for it in the future?
>>>
>>> Cheers,
>>> Martine
>>> ___
>>> devel mailing list
>>> devel@riot-os.org
>>> https://lists.riot-os.org/mailman/listinfo/devel
>>___
>>devel mailing list
>>devel@riot-os.org
>>https://lists.riot-os.org/mailman/listinfo/devel
>
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] qemu-i386 port

[Ludwig Knüpfer]

Hi,

I'm all for cleaning up stale boards, especially I'd they are as hard to obtain 
as for example the FU boards.
If I'm not mistaken this would also enable the removal of at least one legacy 
driver interface (I have some GPIO API in mind).

Cheers,
Ludwig

Am 9. August 2016 13:52:56 MESZ, schrieb "Joakim Nohlgård" 
:
>I agree with dropping qemu-i386
>
>On the same subject, would it make sense to clean up some other boards
>with less than ideal support?
>chronos is one board which I frequently run into trouble with because
>it is never up to date with the other platform implementations,
>especially the stdio is very hacky on that board.
>
>/Joakim
>
>On Aug 9, 2016 12:51, "Martine Lenders"  wrote:
>>
>> Hi,
>> we now have the third person wondering about the qemu-i386 port. Fact
>> is, it doesn't work (we do not even have the unittests activated
>> anymore). Is there a reason why we did not drop it yet (except making
>> all the good work by René void)? Or are we planning to provide better
>> support for it in the future?
>>
>> Cheers,
>> Martine
>> ___
>> devel mailing list
>> devel@riot-os.org
>> https://lists.riot-os.org/mailman/listinfo/devel
>___
>devel mailing list
>devel@riot-os.org
>https://lists.riot-os.org/mailman/listinfo/devel

___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] Απ: Απ: Απ: Απ: Problem with "make" -lm missing.

[MiTsArAs Jimaras]

Hi again.


The point is that the VM hasn't got an OS.

I mean that when I try to run the app on VM, the VM must not have 
Linux/MacOSX/Windows or whatever.

The only thing that exists on the VM must be the RIOT app.

From that point of view, yes, an OS must be running.


P.S: Anyone who have tried to run an app on Arduino Uno, please be kind to tell 
me if they succeed!


Thanks!



Από: devel  εκ μέρους του Ludwig Knüpfer 

Στάλθηκε: Τρίτη, 9 Αυγούστου 2016 2:52 μμ
Προς: RIOT OS kernel developers
Θέμα: Re: [riot-devel] Απ: Απ: Απ: Problem with "make" -lm missing.

Hi,

If you have been told to write an application that runs on a VM without using 
an OS, RIOT is not the answer because it is an OS, so your application is using 
an OS.

Apart from that there is no difference between running on native and running on 
QEMU from the application point of view.

As René already said: you probably should clarify the intention of the task 
with your teachers.

Cheers,
Ludwig



Am 9. August 2016 12:21:51 MESZ, schrieb MiTsArAs Jimaras 
:
>Hahahahaha it's that WHY again!
>
>
>Because I have told to do so from my university!
>
>I can't explain further because I DON'T KNOW WHY!
>
>
>
>
>Από: devel  εκ μέρους του Ludwig Knupfer
>
>Στάλθηκε: Τρίτη, 9 Αυγούστου 2016 1:02 μμ
>Προς: RIOT OS kernel developers
>Θέμα: Re: [riot-devel] Απ: Απ: Problem with "make" -lm missing.
>
>Hi,
>
>Yes, you said that you want do that before but you never explained:
>*WHY* do you want to do that?
>Also: RIOT is an OS!
>
>Cheers,
>Ludwig
>
>Am 9. August 2016 11:15:26 MESZ, schrieb MiTsArAs Jimaras
>:
>>I made trouble once, speaking about this project, but I am going at it
>>again!!
>>
>>
>>I want my app to run on a bare VM. Meaning that I want my VM to boot
>to
>>my app without an OS been installed in the VM emulator. Any solutions
>>would be very helpful!
>>
>>
>>P.S: On the other hand, I have a raspberry pi on my hands and an
>>arduino uno for some days. My project aims on that purpose too.
>>
>>
>>
>>Από: devel  εκ μέρους του Oleg Hahm
>>
>>Στάλθηκε: Τρίτη, 9 Αυγούστου 2016 12:04 μμ
>>Προς: RIOT OS kernel developers
>>Θέμα: Re: [riot-devel] Απ: Problem with "make" -lm missing.
>>
>>Hi!
>>
>>On Tue, Aug 09, 2016 at 08:27:04AM +, MiTsArAs Jimaras wrote:
>>> Now I have another problem!
>>>
>>> I compile on native board, and everything is alright.
>>>
>>> When I am trying to compile on qemu-i386, it seems to start, but I
>>get no
>>> results.
>>
>>Please note that support for i386 is rather rudimentary. Any
>particular
>>reason
>>you want to use this platform?
>>
>>Cheers,
>>Oleg
>>--
>>panic("Aarggh: attempting to free lock with active wait queue - shoot
>>Andy");
>>linux-2.0.38/fs/locks.c
>>
>>
>>
>>
>>___
>>devel mailing list
>>devel@riot-os.org
>>https://lists.riot-os.org/mailman/listinfo/devel
devel -- RIOT OS kernel 
developers
lists.riot-os.org
This is the mailing list for kernel developers of RIOT OS - the friendly 
Internet Of Things Operating System. To see the collection of prior postings to 
the list ...



>devel -- RIOT OS kernel
>developers
>lists.riot-os.org
>This is the mailing list for kernel developers of RIOT OS - the
>friendly Internet Of Things Operating System. To see the collection of
>prior postings to the list ...
>
>
>
>
>___
>devel mailing list
>devel@riot-os.org
>https://lists.riot-os.org/mailman/listinfo/devel
>
>
>
>
>___
>devel mailing list
>devel@riot-os.org
>https://lists.riot-os.org/mailman/listinfo/devel

___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] qemu-i386 port

[Joakim Nohlgård]

I agree with dropping qemu-i386

On the same subject, would it make sense to clean up some other boards
with less than ideal support?
chronos is one board which I frequently run into trouble with because
it is never up to date with the other platform implementations,
especially the stdio is very hacky on that board.

/Joakim

On Aug 9, 2016 12:51, "Martine Lenders"  wrote:
>
> Hi,
> we now have the third person wondering about the qemu-i386 port. Fact
> is, it doesn't work (we do not even have the unittests activated
> anymore). Is there a reason why we did not drop it yet (except making
> all the good work by René void)? Or are we planning to provide better
> support for it in the future?
>
> Cheers,
> Martine
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Απ: Απ: Απ: Problem with "make" -lm missing.

[Ludwig Knüpfer]

Hi,

If you have been told to write an application that runs on a VM without using 
an OS, RIOT is not the answer because it is an OS, so your application is using 
an OS.

Apart from that there is no difference between running on native and running on 
QEMU from the application point of view.

As René already said: you probably should clarify the intention of the task 
with your teachers.

Cheers,
Ludwig



Am 9. August 2016 12:21:51 MESZ, schrieb MiTsArAs Jimaras 
:
>Hahahahaha it's that WHY again!
>
>
>Because I have told to do so from my university!
>
>I can't explain further because I DON'T KNOW WHY!
>
>
>
>
>Από: devel  εκ μέρους του Ludwig Knupfer
>
>Στάλθηκε: Τρίτη, 9 Αυγούστου 2016 1:02 μμ
>Προς: RIOT OS kernel developers
>Θέμα: Re: [riot-devel] Απ: Απ: Problem with "make" -lm missing.
>
>Hi,
>
>Yes, you said that you want do that before but you never explained:
>*WHY* do you want to do that?
>Also: RIOT is an OS!
>
>Cheers,
>Ludwig
>
>Am 9. August 2016 11:15:26 MESZ, schrieb MiTsArAs Jimaras
>:
>>I made trouble once, speaking about this project, but I am going at it
>>again!!
>>
>>
>>I want my app to run on a bare VM. Meaning that I want my VM to boot
>to
>>my app without an OS been installed in the VM emulator. Any solutions
>>would be very helpful!
>>
>>
>>P.S: On the other hand, I have a raspberry pi on my hands and an
>>arduino uno for some days. My project aims on that purpose too.
>>
>>
>>
>>Από: devel  εκ μέρους του Oleg Hahm
>>
>>Στάλθηκε: Τρίτη, 9 Αυγούστου 2016 12:04 μμ
>>Προς: RIOT OS kernel developers
>>Θέμα: Re: [riot-devel] Απ: Problem with "make" -lm missing.
>>
>>Hi!
>>
>>On Tue, Aug 09, 2016 at 08:27:04AM +, MiTsArAs Jimaras wrote:
>>> Now I have another problem!
>>>
>>> I compile on native board, and everything is alright.
>>>
>>> When I am trying to compile on qemu-i386, it seems to start, but I
>>get no
>>> results.
>>
>>Please note that support for i386 is rather rudimentary. Any
>particular
>>reason
>>you want to use this platform?
>>
>>Cheers,
>>Oleg
>>--
>>panic("Aarggh: attempting to free lock with active wait queue - shoot
>>Andy");
>>linux-2.0.38/fs/locks.c
>>
>>
>>
>>
>>___
>>devel mailing list
>>devel@riot-os.org
>>https://lists.riot-os.org/mailman/listinfo/devel
>devel -- RIOT OS kernel
>developers
>lists.riot-os.org
>This is the mailing list for kernel developers of RIOT OS - the
>friendly Internet Of Things Operating System. To see the collection of
>prior postings to the list ...
>
>
>
>
>___
>devel mailing list
>devel@riot-os.org
>https://lists.riot-os.org/mailman/listinfo/devel
>
>
>
>
>___
>devel mailing list
>devel@riot-os.org
>https://lists.riot-os.org/mailman/listinfo/devel

___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] Απ: Απ: Problem with "make" -lm missing.

[MiTsArAs Jimaras]

So a simple Clock-Chronometer written in shell script, wouldn't work for now?



Από: devel  εκ μέρους του Laurent Navet 

Στάλθηκε: Τρίτη, 9 Αυγούστου 2016 2:26 μμ
Προς: RIOT OS kernel developers
Θέμα: Re: [riot-devel] Απ: Problem with "make" -lm missing.

> Any chances that I can run on Arduino Uno?

Arduino uno is not fully functional for now, depends on your
application needs
Basically, UART and timers should work, gpio are untested, no pwm 

Fetch #5590 and #5451 PR and try 

Good luck,

--
« On ne resout pas un probleme avec les modes de pensee qui l'ont engendre. »
« You cannot solve current problems with current thinking. Current
problems are the result of current thinking »
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
devel -- RIOT OS kernel 
developers
lists.riot-os.org
This is the mailing list for kernel developers of RIOT OS - the friendly 
Internet Of Things Operating System. To see the collection of prior postings to 
the list ...



___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Απ: Problem with "make" -lm missing.

[Laurent Navet]

> Any chances that I can run on Arduino Uno?

Arduino uno is not fully functional for now, depends on your
application needs
Basically, UART and timers should work, gpio are untested, no pwm 

Fetch #5590 and #5451 PR and try 

Good luck,

-- 
« On ne résout pas un problème avec les modes de pensée qui l’ont engendré. »
« You cannot solve current problems with current thinking. Current
problems are the result of current thinking »
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] Απ: Problem with "make" -lm missing.

[MiTsArAs Jimaras]

Okay I understand.

Any chances that I can run on Arduino Uno?



Από: devel  εκ μέρους του Rene Kijewski 

Στάλθηκε: Τρίτη, 9 Αυγούστου 2016 1:53 μμ
Προς: devel@riot-os.org
Θέμα: Re: [riot-devel] Problem with "make" -lm missing.

Am Tue, 9 Aug 2016 10:21:51 +
schrieb MiTsArAs Jimaras :

> Because I have told to do so from my university!
>
> I can't explain further because I DON'T KNOW WHY!

Hi,

then either ask your prof / TA what your objective is or drop the class.
You may quote the author of the qemu-i386 port (that's me) that the port is in 
a bad shape (that's true).
But you are also welcome to bring the port up to speed, but please accept that 
we won't jump because the need port right now.

RIOT has full support for multiple inexpensive boards that might work better 
for you than emulation.
Please see: https://github.com/RIOT-OS/RIOT/wiki/RIOT-Platforms
[https://avatars1.githubusercontent.com/u/3079480?v=3=400]

RIOT Platforms · RIOT-OS/RIOT Wiki · 
GitHub
github.com
RIOT - The friendly OS for IoT ... Board Supplier MCU (cpu) Radio Family Vendor 
Status Maintainer; native: RIOT: Linux/OSX on x86




Regards
Rene
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] qemu-i386 port

[Oleg Hahm]

Hi!

On Tue, Aug 09, 2016 at 10:34:19AM +0200, Martine Lenders wrote:
> we now have the third person wondering about the qemu-i386 port.

For the record: I count only two.

Otherwise: +1 for the proposal.

Cheers,
Oleg

P.S. Should we drop support for the Spark as well?
-- 
I'm working on a bittorrent joke, but I only have about 30% and nobody's
seeding!


signature.asc
Description: PGP signature
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] qemu-i386 port

[René Kijewski]

Am Tue, 9 Aug 2016 10:34:19 +0200
schrieb Martine Lenders :

> we now have the third person wondering about the qemu-i386 port. Fact
> is, it doesn't work (we do not even have the unittests activated
> anymore). Is there a reason why we did not drop it yet (except making
> all the good work by René void)?

Hi Martine,

Git does not forget, so even if the "board" is rm -rf'd for now nothing is lost.
The current state is probably worse then not having the board at all.
Shall I open a PR to pull the port, so it is obvious that the author is OK with 
the decision?

Best,
René
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Problem with "make" -lm missing.

[René Kijewski]

Am Tue, 9 Aug 2016 10:21:51 +
schrieb MiTsArAs Jimaras :

> Because I have told to do so from my university!
> 
> I can't explain further because I DON'T KNOW WHY!

Hi,

then either ask your prof / TA what your objective is or drop the class.
You may quote the author of the qemu-i386 port (that's me) that the port is in 
a bad shape (that's true).
But you are also welcome to bring the port up to speed, but please accept that 
we won't jump because the need port right now.

RIOT has full support for multiple inexpensive boards that might work better 
for you than emulation.
Please see: https://github.com/RIOT-OS/RIOT/wiki/RIOT-Platforms

Regards
René
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] qemu-i386 port

[Martine Lenders]

Hi,
we now have the third person wondering about the qemu-i386 port. Fact
is, it doesn't work (we do not even have the unittests activated
anymore). Is there a reason why we did not drop it yet (except making
all the good work by René void)? Or are we planning to provide better
support for it in the future?

Cheers,
Martine
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] Απ: Απ: Απ: Problem with "make" -lm missing.

[MiTsArAs Jimaras]

Hahahahaha it's that WHY again!


Because I have told to do so from my university!

I can't explain further because I DON'T KNOW WHY!




Από: devel  εκ μέρους του Ludwig Knupfer 

Στάλθηκε: Τρίτη, 9 Αυγούστου 2016 1:02 μμ
Προς: RIOT OS kernel developers
Θέμα: Re: [riot-devel] Απ: Απ: Problem with "make" -lm missing.

Hi,

Yes, you said that you want do that before but you never explained: *WHY* do 
you want to do that?
Also: RIOT is an OS!

Cheers,
Ludwig

Am 9. August 2016 11:15:26 MESZ, schrieb MiTsArAs Jimaras 
:
>I made trouble once, speaking about this project, but I am going at it
>again!!
>
>
>I want my app to run on a bare VM. Meaning that I want my VM to boot to
>my app without an OS been installed in the VM emulator. Any solutions
>would be very helpful!
>
>
>P.S: On the other hand, I have a raspberry pi on my hands and an
>arduino uno for some days. My project aims on that purpose too.
>
>
>
>Από: devel  εκ μέρους του Oleg Hahm
>
>Στάλθηκε: Τρίτη, 9 Αυγούστου 2016 12:04 μμ
>Προς: RIOT OS kernel developers
>Θέμα: Re: [riot-devel] Απ: Problem with "make" -lm missing.
>
>Hi!
>
>On Tue, Aug 09, 2016 at 08:27:04AM +, MiTsArAs Jimaras wrote:
>> Now I have another problem!
>>
>> I compile on native board, and everything is alright.
>>
>> When I am trying to compile on qemu-i386, it seems to start, but I
>get no
>> results.
>
>Please note that support for i386 is rather rudimentary. Any particular
>reason
>you want to use this platform?
>
>Cheers,
>Oleg
>--
>panic("Aarggh: attempting to free lock with active wait queue - shoot
>Andy");
>linux-2.0.38/fs/locks.c
>
>
>
>
>___
>devel mailing list
>devel@riot-os.org
>https://lists.riot-os.org/mailman/listinfo/devel
devel -- RIOT OS kernel 
developers
lists.riot-os.org
This is the mailing list for kernel developers of RIOT OS - the friendly 
Internet Of Things Operating System. To see the collection of prior postings to 
the list ...




___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Απ: Απ: Problem with "make" -lm missing.

[Ludwig Knüpfer]

Hi,

Yes, you said that you want do that before but you never explained: *WHY* do 
you want to do that?
Also: RIOT is an OS!

Cheers,
Ludwig

Am 9. August 2016 11:15:26 MESZ, schrieb MiTsArAs Jimaras 
:
>I made trouble once, speaking about this project, but I am going at it
>again!!
>
>
>I want my app to run on a bare VM. Meaning that I want my VM to boot to
>my app without an OS been installed in the VM emulator. Any solutions
>would be very helpful!
>
>
>P.S: On the other hand, I have a raspberry pi on my hands and an
>arduino uno for some days. My project aims on that purpose too.
>
>
>
>Από: devel  εκ μέρους του Oleg Hahm
>
>Στάλθηκε: Τρίτη, 9 Αυγούστου 2016 12:04 μμ
>Προς: RIOT OS kernel developers
>Θέμα: Re: [riot-devel] Απ: Problem with "make" -lm missing.
>
>Hi!
>
>On Tue, Aug 09, 2016 at 08:27:04AM +, MiTsArAs Jimaras wrote:
>> Now I have another problem!
>>
>> I compile on native board, and everything is alright.
>>
>> When I am trying to compile on qemu-i386, it seems to start, but I
>get no
>> results.
>
>Please note that support for i386 is rather rudimentary. Any particular
>reason
>you want to use this platform?
>
>Cheers,
>Oleg
>--
>panic("Aarggh: attempting to free lock with active wait queue - shoot
>Andy");
>linux-2.0.38/fs/locks.c
>
>
>
>
>___
>devel mailing list
>devel@riot-os.org
>https://lists.riot-os.org/mailman/listinfo/devel

___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] Απ: Απ: Problem with "make" -lm missing.

[MiTsArAs Jimaras]

I made trouble once, speaking about this project, but I am going at it again!!


I want my app to run on a bare VM. Meaning that I want my VM to boot to my app 
without an OS been installed in the VM emulator. Any solutions would be very 
helpful!


P.S: On the other hand, I have a raspberry pi on my hands and an arduino uno 
for some days. My project aims on that purpose too.



Από: devel  εκ μέρους του Oleg Hahm 

Στάλθηκε: Τρίτη, 9 Αυγούστου 2016 12:04 μμ
Προς: RIOT OS kernel developers
Θέμα: Re: [riot-devel] Απ: Problem with "make" -lm missing.

Hi!

On Tue, Aug 09, 2016 at 08:27:04AM +, MiTsArAs Jimaras wrote:
> Now I have another problem!
>
> I compile on native board, and everything is alright.
>
> When I am trying to compile on qemu-i386, it seems to start, but I get no
> results.

Please note that support for i386 is rather rudimentary. Any particular reason
you want to use this platform?

Cheers,
Oleg
--
panic("Aarggh: attempting to free lock with active wait queue - shoot Andy");
linux-2.0.38/fs/locks.c
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Απ: Problem with "make" -lm missing.

[Oleg Hahm]

Hi!

On Tue, Aug 09, 2016 at 08:27:04AM +, MiTsArAs Jimaras wrote:
> Now I have another problem!
> 
> I compile on native board, and everything is alright.
> 
> When I am trying to compile on qemu-i386, it seems to start, but I get no
> results.

Please note that support for i386 is rather rudimentary. Any particular reason
you want to use this platform?

Cheers,
Oleg
-- 
panic("Aarggh: attempting to free lock with active wait queue - shoot Andy");
linux-2.0.38/fs/locks.c


signature.asc
Description: PGP signature
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Απ: Problem with "make" -lm missing.

[Ludwig Knüpfer]

Hi,

It's difficult to say anything about this without seeing the actual source code.

Cheers,
Ludwig

Am 9. August 2016 10:27:04 MESZ, schrieb MiTsArAs Jimaras 
:
>Problem solved.
>
>Now I have another problem!
>
>I compile on native board, and everything is alright.
>
>When I am trying to compile on qemu-i386, it seems to start, but I get
>no results. All I get is:
>
>Building application "time" for "qemu-i386" with MCU "x86".
>
>"make" -C /home/d/RIOT/pkg/tlsf
>rm -rf /home/d/RIOT/examples/time/bin/pkg/qemu-i386/tlsf/src
>mkdir -p /home/d/RIOT/examples/time/bin/pkg/qemu-i386/tlsf/src
>patching file Makefile
>patching file tlsf-malloc.c
>patching file tlsf-malloc.h
>patching file tlsf.c
>patching file tlsf.h
>"make" -C /home/d/RIOT/boards/qemu-i386
>"make" -C /home/d/RIOT/boards/x86-multiboot-common
>"make" -C /home/d/RIOT/core
>"make" -C /home/d/RIOT/cpu/x86
>"make" -C /home/d/RIOT/drivers
>"make" -C /home/d/RIOT/sys
>"make" -C /home/d/RIOT/sys/auto_init
>"make" -C /home/d/RIOT/sys/quad_math
>   text   databssdechex filename
>123739   2392  68228 194359  2f737
>/home/d/RIOT/examples/time/bin/qemu-i386/time.elf
>true
>exec /home/d/RIOT/boards/qemu-i386/dist/term.py qemu-system-i386
>/home//RIOT/examples/time/bin
>/home/d/RIOT/examples/time/bin/qemu-i386/time.hex
>Type 'exit' to exit.
>Starting QEMU: qemu-system-i386 -serial tcp:0.0.0.0:55893 -nographic
>-monitor /dev/null -kernel
>/home/d/RIOT/examples/time/bin/qemu-i386/time.hex -m size=512
>
>2016-08-09 11:19:44.436878: Interrupt handling initialized
>2016-08-09 11:19:44.437139: PIC initialized
>2016-08-09 11:19:44.437568: Warning: Your hardware does not support the
>NX bit!
>2016-08-09 11:19:44.437834:  Setting PT_XD = 0.
>2016-08-09 11:19:44.438586: Kernel memory: 0x10 - 0x132000
>2016-08-09 11:19:44.438882:   .text:   0x100060 - 0x1172ef
>2016-08-09 11:19:44.439173:   .rodata: 0x118000 - 0x11ae08
>2016-08-09 11:19:44.439451:   .data:   0x12 - 0x1208e8
>2016-08-09 11:19:44.439737:   .bss:0x121000 - 0x131a84
>2016-08-09 11:19:44.440049: Unmapped memory: 0x132000 - 0x14
>2016-08-09 11:19:44.440254: Heap start: 0x14
>2016-08-09 11:19:44.440625:    - 0009fc00
>(usable)
>2016-08-09 11:19:44.441091:   0009fc00 - 000a
>(unusable: reseved)
>2016-08-09 11:19:44.441545:   000f - 0010
>(unusable: reseved)
>2016-08-09 11:19:44.441919:   0010 - 1ffe
>(usable)
>2016-08-09 11:19:44.674721:   1ffe - 2000
>(unusable: reseved)
>2016-08-09 11:19:44.675258:   fffc - 0001
>(unusable: reseved)
>2016-08-09 11:19:44.676789: There are 130734 free pages (510.680 MB)
>available for the heap.
>2016-08-09 11:19:44.677060: Virtual memory initialized
>2016-08-09 11:19:44.677378: RTC initialized [08:19:44, 2016-08-09]
>2016-08-09 11:19:44.677551: PIT initialized
>2016-08-09 11:19:44.677769: Looking up PCI devices
>2016-08-09 11:19:44.678502:   00:00.0 "Intel Corporation": "440FX -
>82441FX PMC [Natoma]" (Bridge device: Host bridge, rev: 02)
>2016-08-09 11:19:44.679282:   00:01.0 "Intel Corporation": "82371SB
>PIIX3 ISA [Natoma/Triton II]" (Bridge device: ISA bridge, rev: 00)
>2016-08-09 11:19:44.680175:   00:01.1 "Intel Corporation": "82371SB
>PIIX3 IDE [Natoma/Triton II]" (Mass storage controller: IDE controller,
>rev: 00)
>2016-08-09 11:19:44.680531: BAR 4: I/O space, ports 0xc040-0xc04f
>2016-08-09 11:19:44.681289:   00:01.3 "Intel Corporation":
>"82371AB/EB/MB PIIX4 ACPI" (Bridge device: Other bridge device, rev:
>03)
>2016-08-09 11:19:44.681535: IRQ: new = 10, old = 9
>2016-08-09 11:19:44.682184:   00:02.0 "0x1234": "0x" (Display
>controller: VGA-compatible controller, rev: 02)
>2016-08-09 11:19:44.695092: BAR 0: memory, physical =
>0xfd00-0xfdff, virtual = 0x0023d000-0x0123cfff
>2016-08-09 11:19:44.695797: BAR 2: memory, physical =
>0xfebf-0xfebf0fff, virtual = 0x1fff7000-0x1fff7fff
>2016-08-09 11:19:44.696827:   00:03.0 "Intel Corporation": "82540EM
>Gigabit Ethernet Controller" (Network controller: Ethernet controller,
>rev: 03)
>2016-08-09 11:19:44.697108: IRQ: new = 10, old = 11
>2016-08-09 11:19:44.697756: BAR 0: memory, physical =
>0xfebc-0xfebd, virtual = 0x1fff9000-0x20018fff
>2016-08-09 11:19:44.698100: BAR 1: I/O space, ports 0xc000-0xc03f
>2016-08-09 11:19:44.698438: RIOT x86 hardware initialization complete.
>2016-08-09 11:19:44.698729: RIOT board initialization complete.
>2016-08-09 11:19:44.699216: main(): This is RIOT! (Version:
>2016.10-devel-21-gcf11a-D)
>
>
>After this, it just don't run. It was supposed to show a clock to me.
>
>
>Από: devel  εκ μέρους του Martine Lenders
>
>Στάλθηκε: Τρίτη, 9 Αυγούστου 2016 10:22 πμ
>Προς: RIOT OS kernel developers
>Θέμα: Re: [riot-devel] Problem with "make" -lm missing.
>
>Oops, forgot to 

Re: [riot-devel] Problem with "make" -lm missing.

[Martine Lenders]

Oops, forgot to provide the link for [1]:
https://github.com/RIOT-OS/RIOT/wiki/Family%3A-native#dependencies

2016-08-09 9:19 GMT+02:00 Laurent Navet :
> Hi,
>
> Have you multilib support enabled and installed ?
>
> https://github.com/RIOT-OS/RIOT/wiki/Family:-native
>
> 2016-08-09 9:02 UTC+02:00, MiTsArAs Jimaras :
>> Hello to all.
>> I am trying to build an app with  "make clean all flash term" on native
>> platform, and all I get as a result that:
>>
>> Building application "time" for "native" with MCU "native".
>>
>> "make" -C /home/d/RIOT/boards/native
>> "make" -C /home/d/RIOT/boards/native/drivers
>> "make" -C /home/d/RIOT/core
>> "make" -C /home/d/RIOT/cpu/native
>> "make" -C /home/d/RIOT/cpu/native/periph
>> "make" -C /home/d/RIOT/drivers
>> "make" -C /home/d/RIOT/sys
>> "make" -C /home/d/RIOT/sys/auto_init
>> /usr/bin/ld: skipping incompatible
>> /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib/libm.so when
>> searching for -lm
>> /usr/bin/ld: skipping incompatible
>> /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib/libm.a when searching
>> for -lm
>> /usr/bin/ld: skipping incompatible /lib/../lib/libm.so when searching for
>> -lm
>> /usr/bin/ld: skipping incompatible /lib/../lib/libm.a when searching for
>> -lm
>> /usr/bin/ld: skipping incompatible /usr/lib/../lib/libm.so when searching
>> for -lm
>> /usr/bin/ld: skipping incompatible /usr/lib/../lib/libm.a when searching for
>> -lm
>> /usr/bin/ld: skipping incompatible
>> /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../libm.so when searching for
>> -lm
>> /usr/bin/ld: skipping incompatible
>> /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../libm.a when searching for
>> -lm
>> /usr/bin/ld: skipping incompatible /usr/lib/libm.so when searching for -lm
>> /usr/bin/ld: skipping incompatible /usr/lib/libm.a when searching for -lm
>> /usr/bin/ld: cannot find -lm
>> collect2: error: ld returned 1 exit status
>> make: *** [/home/darch/RIOT/examples/time/../../Makefile.include:261: all]
>> Error 1
>>
>> I am using ArchLinux. What am I doing wrong?
>> Thanks!
>>
>>
>>
>
>
> --
> « On ne résout pas un problème avec les modes de pensée qui l’ont engendré. »
> « You cannot solve current problems with current thinking. Current
> problems are the result of current thinking »
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Problem with "make" -lm missing.

[Martine Lenders]

Hi,
have you installed gcc-multilib and the other dependencies [1]?

Cheers,
Martine

2016-08-09 9:02 GMT+02:00 MiTsArAs Jimaras :
> Hello to all.
> I am trying to build an app with  "make clean all flash term" on native
> platform, and all I get as a result that:
>
> Building application "time" for "native" with MCU "native".
>
> "make" -C /home/d/RIOT/boards/native
> "make" -C /home/d/RIOT/boards/native/drivers
> "make" -C /home/d/RIOT/core
> "make" -C /home/d/RIOT/cpu/native
> "make" -C /home/d/RIOT/cpu/native/periph
> "make" -C /home/d/RIOT/drivers
> "make" -C /home/d/RIOT/sys
> "make" -C /home/d/RIOT/sys/auto_init
> /usr/bin/ld: skipping incompatible
> /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib/libm.so when
> searching for -lm
> /usr/bin/ld: skipping incompatible
> /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib/libm.a when searching
> for -lm
> /usr/bin/ld: skipping incompatible /lib/../lib/libm.so when searching for
> -lm
> /usr/bin/ld: skipping incompatible /lib/../lib/libm.a when searching for -lm
> /usr/bin/ld: skipping incompatible /usr/lib/../lib/libm.so when searching
> for -lm
> /usr/bin/ld: skipping incompatible /usr/lib/../lib/libm.a when searching for
> -lm
> /usr/bin/ld: skipping incompatible
> /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../libm.so when searching for
> -lm
> /usr/bin/ld: skipping incompatible
> /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../libm.a when searching for
> -lm
> /usr/bin/ld: skipping incompatible /usr/lib/libm.so when searching for -lm
> /usr/bin/ld: skipping incompatible /usr/lib/libm.a when searching for -lm
> /usr/bin/ld: cannot find -lm
> collect2: error: ld returned 1 exit status
> make: *** [/home/darch/RIOT/examples/time/../../Makefile.include:261: all]
> Error 1
>
> I am using ArchLinux. What am I doing wrong?
> Thanks!
>
>
>
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Problem with "make" -lm missing.

[Laurent Navet]

Hi,

Have you multilib support enabled and installed ?

https://github.com/RIOT-OS/RIOT/wiki/Family:-native

2016-08-09 9:02 UTC+02:00, MiTsArAs Jimaras :
> Hello to all.
> I am trying to build an app with  "make clean all flash term" on native
> platform, and all I get as a result that:
>
> Building application "time" for "native" with MCU "native".
>
> "make" -C /home/d/RIOT/boards/native
> "make" -C /home/d/RIOT/boards/native/drivers
> "make" -C /home/d/RIOT/core
> "make" -C /home/d/RIOT/cpu/native
> "make" -C /home/d/RIOT/cpu/native/periph
> "make" -C /home/d/RIOT/drivers
> "make" -C /home/d/RIOT/sys
> "make" -C /home/d/RIOT/sys/auto_init
> /usr/bin/ld: skipping incompatible
> /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib/libm.so when
> searching for -lm
> /usr/bin/ld: skipping incompatible
> /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib/libm.a when searching
> for -lm
> /usr/bin/ld: skipping incompatible /lib/../lib/libm.so when searching for
> -lm
> /usr/bin/ld: skipping incompatible /lib/../lib/libm.a when searching for
> -lm
> /usr/bin/ld: skipping incompatible /usr/lib/../lib/libm.so when searching
> for -lm
> /usr/bin/ld: skipping incompatible /usr/lib/../lib/libm.a when searching for
> -lm
> /usr/bin/ld: skipping incompatible
> /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../libm.so when searching for
> -lm
> /usr/bin/ld: skipping incompatible
> /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../libm.a when searching for
> -lm
> /usr/bin/ld: skipping incompatible /usr/lib/libm.so when searching for -lm
> /usr/bin/ld: skipping incompatible /usr/lib/libm.a when searching for -lm
> /usr/bin/ld: cannot find -lm
> collect2: error: ld returned 1 exit status
> make: *** [/home/darch/RIOT/examples/time/../../Makefile.include:261: all]
> Error 1
>
> I am using ArchLinux. What am I doing wrong?
> Thanks!
>
>
>


-- 
« On ne résout pas un problème avec les modes de pensée qui l’ont engendré. »
« You cannot solve current problems with current thinking. Current
problems are the result of current thinking »
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] Problem with "make" -lm missing.

[MiTsArAs Jimaras]

Hello to all.
I am trying to build an app with  "make clean all flash term" on native 
platform, and all I get as a result that:

Building application "time" for "native" with MCU "native".

"make" -C /home/d/RIOT/boards/native
"make" -C /home/d/RIOT/boards/native/drivers
"make" -C /home/d/RIOT/core
"make" -C /home/d/RIOT/cpu/native
"make" -C /home/d/RIOT/cpu/native/periph
"make" -C /home/d/RIOT/drivers
"make" -C /home/d/RIOT/sys
"make" -C /home/d/RIOT/sys/auto_init
/usr/bin/ld: skipping incompatible 
/usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib/libm.so when searching 
for -lm
/usr/bin/ld: skipping incompatible 
/usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib/libm.a when searching 
for -lm
/usr/bin/ld: skipping incompatible /lib/../lib/libm.so when searching for -lm
/usr/bin/ld: skipping incompatible /lib/../lib/libm.a when searching for -lm
/usr/bin/ld: skipping incompatible /usr/lib/../lib/libm.so when searching for 
-lm
/usr/bin/ld: skipping incompatible /usr/lib/../lib/libm.a when searching for -lm
/usr/bin/ld: skipping incompatible 
/usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../libm.so when searching for -lm
/usr/bin/ld: skipping incompatible 
/usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../libm.a when searching for -lm
/usr/bin/ld: skipping incompatible /usr/lib/libm.so when searching for -lm
/usr/bin/ld: skipping incompatible /usr/lib/libm.a when searching for -lm
/usr/bin/ld: cannot find -lm
collect2: error: ld returned 1 exit status
make: *** [/home/darch/RIOT/examples/time/../../Makefile.include:261: all] 
Error 1

I am using ArchLinux. What am I doing wrong?
Thanks!


___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel