This was suggested/requested in mindboards/ev3dev-kernel#22

In the test image that I have just posted (00.01.98.1), The files that need to be changed are in place. I have removed any need to change kernel boot parameters. Just need to make a script to edit and/or rename the these files:

/etc/modules.d/legoev3-ports.conf
/etc/sysctl.d/ev3dev.conf

Hi,
My aim is to make the robot communicate using protocol 802.15.4 through usb dongle 802.15.4 over 6LoWPAN.
the robot has to be able to get information from TelosB captor
Do you think it can be possible ?

This is a really strange bug that has me scratching my head and google turns up nothing. It probably isn't high priority that we try to fix it since it can be worked around, but I want to make sure people know about it.

I have been playing around with boot parameters. I wanted to turn off kernel messages to serial port ttyS1 because this is the UART on input port 1. If kernel messages are being sent to this port, it will interfere with UART sensors that are connected to it. The obvious thing to do is to change the kernel parameter to use a virtual console instead of the serial console. However when you do this, fast interrupts (FIQs) are no longer "fast". What I mean by this is that the interrupt still take place, but it does not operate as it should (see link). Instead of the very high rate of interrupts (on the order of 10kHz), it can take up to 250 msec between interrupts. As a result, I2C communications are way too slow and don't work. Sound also takes way longer than it should to playback and the audio is unrecognizable (beep still works though because it does not use FIQ).

Similar to the "event driven buttons" file, but it would block until the motor has finished running instead of until a button is pressed.

In my /etc/network/interfaces I made it look like

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wireless-essid Censored
wireless-mode Managed

and now it hangs when I restart the networking service with the dongle in, it hangs on shutdown with it in, and it hangs on boot with it in

Playing with ifconfig

root@ev3dev:~# ifconfig wlan0 up
Segmentation fault
root@ev3dev:~#
Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:Internal error: Oops - BUG: 0 [#1] PREEMPT

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:Process ifconfig (pid: 2268, stack limit = 0xc2c7a270)

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:Stack: (0xc2c7bb10 to 0xc2c7c000)

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bb00:                                     ffddf000 00001000 c39aa8a0 c3a                                                                        63780

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bb20: c38a1000 c2c7bbfc 00000010 00000000 00000040 00000010 c2c7bb8c c2c                                                                        7bb48

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bb40: c01fb164 c01fa80c c2c7bb9c c2c7bb58 c000dbb8 c000f990 c3a63840 c38                                                                        a10e0

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bb60: c0568c80 00000000 00000000 c2c7bbfc 00000032 00000000 00000040 000                                                                        00010

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bb80: c2c7bbb4 c2c7bb90 c01fbf50 c01fab4c c3a63780 c3a63780 c2c7bbb8 c2c                                                                        7bbfc

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bba0: 00000032 00000000 c2c7bbec c2c7bbb8 c01fd074 c01fbcd4 00000000 c2c                                                                        7bbbc

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bbc0: c2c7bbbc c3a63780 c2c7bbec c2c39800 c39aa8a0 00000000 000000ea 000                                                                        00000

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bbe0: c2c7bc2c c2c7bbf0 c01fd2d4 c01fd038 c48b2020 80000700 00000007 000                                                                        01000

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bc00: c2c7bc1c 000000ea c2c39800 ffddf000 c48b2020 00000007 00000011 000                                                                        01000

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bc20: c2c7bc74 c2c7bc30 bf01fba8 c01fd214 00001000 00000000 ffddf000 000                                                                        000ea

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bc40: 00000032 c2c39800 00000000 c2c64000 c3b94e80 00000000 c48b2020 000                                                                        01000

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bc60: c48b2020 00000076 c2c7bca4 c2c7bc78 bf003dc4 bf01fb2c 00000000 c3b                                                                        9428c

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bc80: c48b2020 00000000 c3b94e80 00001000 00000003 00000e6e c2c7bccc c2c                                                                        7bca8

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bca0: bf003f14 bf003d68 00001000 00000000 c3b94e80 c48b2020 c3b94260 c48                                                                        b2020

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bcc0: c2c7bd04 c2c7bcd0 bf0041b4 bf003ea4 c2c7bcec c2c7bce0 bf020994 c3b                                                                        94e80

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bce0: c3b94260 c3b94e80 c3b94e80 c3b94e80 00000002 00000010 c2c7bd5c c2c                                                                        7bd08

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bd00: bf030284 bf003f80 00000003 00000003 00000003 c00525bc 00000008 000                                                                        00000

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bd20: 000000e7 00000002 00000003 c2c49368 c2c7bd84 c3b94260 c3b94e80 c3b                                                                        94260

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bd40: 00000001 c3b9428c c2c7be70 00000001 c2c7bd8c c2c7bd60 bf0204e0 bf0                                                                        2f6a0

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bd60: c02974d4 0000000d c3b94e80 00000001 c3b94260 00000001 c2c49360 000                                                                        00001

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bd80: c2c7bdac c2c7bd90 bf01afa0 bf0204c0 bf01af50 c3b94260 c2c49000 000                                                                        01002

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bda0: c2c7bddc c2c7bdb0 c0373490 bf01af60 000000ff c2c49000 c03c2af8 000                                                                        01002

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bdc0: 00000001 c39b8d0c c2c7be70 00000000 c2c7bdf4 c2c7bde0 c0373aec c03                                                                        73388

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bde0: c0373a7c c2c49000 c2c7be0c c2c7bdf8 c0291cb4 c0373a8c c2c49000 000                                                                        01043

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:be00: c2c7be2c c2c7be10 c0291ef8 c0291c1c c2c49000 00001002 c2c49000 c39                                                                        b8d00

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:be20: c2c7be4c c2c7be30 c0292008 c0291e74 00008914 00000000 00000001 c2c                                                                        49000

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:be40: c2c7bebc c2c7be50 c02da67c c0292000 00000020 be81fec9 00008914 be8                                                                        1fae4

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:be60: 6e616c77 00000030 00000000 00000000 b6f71043 be81fec9 0000002c 000                                                                        0006e

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:be80: b6f71043 be81fec9 0000002c 0000006e b6f71002 00008914 be81fae4 be8                                                                        1fae4

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bea0: c3487b20 c00095c4 c2c7a000 00000000 c2c7bed4 c2c7bec0 c02db82c c02                                                                        da398

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bec0: c3487b00 00008914 c2c7bef4 c2c7bed8 c027f7f4 c02db76c c027f600 c2c                                                                        8d800

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bee0: be81fae4 be81fae4 c2c7bf04 c2c7bef8 c0097408 c027f610 c2c7bf7c c2c                                                                        7bf08

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bf00: c0097ee0 c00973ec c0052730 c00525bc c04daab8 00000004 c2c7bf3c c2c                                                                        7bf28

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bf20: c00527b0 c00526e0 c04daab8 20000013 c2c7bf54 c2c7bf40 c00527f0 c00                                                                        52768

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bf40: c2c8d680 c2c8de00 c2c7bf64 c2c7bf58 c003789c c00527c8 c2c8d800 be8                                                                        1fae4

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bf60: 00008914 00000004 c00095c4 c2c7a000 c2c7bfa4 c2c7bf80 c0097f78 c00                                                                        979c8

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bf80: 00000021 00000000 0001f958 be81fbc8 0001f6d4 00000036 00000000 c2c                                                                        7bfa8

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bfa0: c0009440 c0097f48 0001f958 be81fbc8 00000004 00008914 be81fae4 000                                                                        01002

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bfc0: 0001f958 be81fbc8 0001f6d4 00000036 0001f960 00000075 b6f8f000 be8                                                                        1fec9

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:bfe0: 00001043 be81fad8 0000b9b4 b6ecf28c 60000010 00000004 e1a04007 e28                                                                        7700c

Message from syslogd@ev3dev at Jan  1 00:41:51 ...
 kernel:Code: e59f1110 e5911000 e15a0001 3a000000 (e7f001f2)

Then when I run ifconfig a second time, it hangs.

It's worth noting that it works fine on my raspberry pi

We have sound already working.

@fdetro: If you have any additional goals for the coming release, please let us know.

This issue is up for grabs. Any volunteers?

Preliminary bluetooth support is implemented in the uart-sensors branch (see #36 for how to get it).

I have tinkered with it a bit and the bluetooth appears to be functional. We need somebody to tinker with it more and figure out how to pair and enable services and stuff like that and then write up how to do it so we can put it on the wiki.

From talking to @Geekdude on IRC, it is apparent that the gyro sensor is not returning signed data values as it should.

Relevant code is at: https://github.com/mindboards/ev3dev-kernel/blob/master/drivers/legoev3/legoev3_uart.c#L846

I don't have a gyro sensor, so if anyone wants to take a crack at it...

This issue is a transcript of an email thread between Ralph and I in case we find a solution that's useful to others.

tl;dr - output works on serial console, input doesn't, need a clue.

Long version:

Sorry to bother you but I was trying to hack on my EV3 and as far as I can tell you're one of very few competent people working on the device.

Both with the stock distribution and with your ev3dev distribution, I can see output on the serial console and type, but the system doesn't react. Characters are echoed back across the connection but that's it, I can't log in or interact with a shell (after changing /etc/inittab to spawn a shell instead of anything else at startup) or find any stty settings that make any difference (after changing /etc/inittab to start a shell script that messes with the terminal before starting a shell).

So I wanted to confirm - in your ev3dev setup, you're able to actually work on the serial console, right?

Any insight much appreciated,

Work is being done in the ev3dev-kernel/motor-driver branch.

Reference to #34 this is the new issue.. @rhempel

I have a Class 4 - 2gb microsd sd-co2g
I am following https://github.com/mindboards/ev3dev/wiki/Getting-started-v2#step-4-enable-usb-networking step 3 Linux command line to write the image.
I am using Linux 12.04 Ubuntu

When I format the disk - what should it be formatted to? ext 3 / ext 2 / fat 32? etc.. Maybe this could be it.. I have tried ext 3 and fat 32

@rhempel: Am I correct in assuming that you based ev3dev on Davinci PSP 03.22.00.02

I have been working on creating a new SD card image and spent quite a bit of time researching the bootstrapping process. Based on what I have learned, I would like to propose some ideas for creating the root file system and SD card image.

Well, I was going to make a list of ideas, but it really boils down to this: Use the polystrap tool from @josch for creating the root file system and use guestfish for creating the SD card image.

@josch has written an article on his motivation. TL;RD (but you should read it) is that it is better to do the boostrapping as non-root user. I can completely sympathize with this as I hosed my system more than once using multistrap.

I am using the proot variant. (proot is available from http://proot.me and my modified polystrap package is available from http://ppa.lechnology.com/ev3dev.) proot is amazing, but I do see one potential issue: it cannot do hard links. If I understand correctly, the workaround that was settled on is to copy the common file to a new location and create 2 symbolic links to the moved file so that it more or less emulates hard links (other than when you delete both links, you still have the moved file laying around). So far, the images I have created with this seem to work fine on the EV3.

If proot turns out to be a problem, we can try fakeroot/fakechroot, but they seem to be a bit tricky and I have not been able to get them to work yet. We could also modify polystrap to use root if we need to.

guestfish (part of [libguestfs[(http://libguestfs.org/)) is another brilliant tool that lets us build the image file without root privileges as well. The only shortcoming I have found with it is that you cannot label the vfat file system.

Whenever I boot the EV3 with the USB cable plugged in (usually because I ran the reboot command), it gives me this error traytip, and I can't connect to it until I physically reattach the cable.

USB Device Not Recognized
One of the USB devices attached to this computer has
malfunctioned, and Windows does not recognize it.
For assistance in solving this problem, click this
message.

Just an idea. As we run sshd anyway, I'd recommend that users will copy their pub-key to ~/.ssh/authorized_keys2 and then use scp/rsync. This way we can skip running nfs-common and rpcbind. That makes the bootup a tad faster and frees memory.

I forked this repo and added a new page for ssh and sftp. I changed the Home page too.
But i cant pull this to the main repo, so i post this here.

Analog sensors are an sensor that is not I2C or UART.

Touch sensors are supported in the uart-sensors branch (See #36).

More changes are coming soon.

After using dd to flash ev3dev.img 00.01.00 onto my SD card I was able to mount the file system just fine.

Following the same procedure with the newer image results in:

Even though we don't exactly have a massive following at this point, I thought it might be useful/fun to have an IRC channel, so I have set one up - #ev3dev on irc://irc.freenode.net. It is logged so you can ask a question and come back in a couple of days and see if anyone responded.

I finally got around to adding my own userid to the ev3dev distro, and found that even after adding myself to the sudo group, I could not run sudo without the warning message telling me:

sudo: effective uid is not 0, is sudo installed setuid root?

And of course, /usr/bin/sudo does not have setuid, so the quick fix is (as root)

chmod 4755 /usr/bin/sudo

And then all is good. Still need to investigate this as I may have borked up other permissions on the ev3dev image. It's always a learning experience.

Hi, I just put ev3dev on my sdcard and wanted to report some minor issues I had which individually do not warrent individual bug reports.

Firstly, https://github.com/mindboards/ev3dev/wiki/Writing-A-microSD-Card pointed me to the "RPi Easy SD Card Setup" page. It turns out that I wasted quite some time on this page as it is very long. Could you just put somewhere that doing:

zcat ev3dev.img.gz | dd of=/dev/sdX

is enough? I have been using several embedded devices, including the openmoko phones and the beagleboard, so I was used to the fact that creating the SD card image would take quite a number of steps. If the above wiki page would just point out that ev3dev.img.gz is a disk image of a 500MB sd card, including the partition table which has to be written straight to the SD card, While the page calls it "image" a couple of times, it was not obvious for me what kind of image it is, since it pointed to the very elaborate and long RPi instructions. I could've saved some time that I spent in the maybe-easy-but-not-quite-short RPi setup page.

Something else which you could mention somewhere is, that after flashing it, you can reload your partition table with:

sudo partprobe

So that you dont have to eject and reinsert the sd card to be able to mount the first partition. I edited ev3dev.rc.local, unmounted, inserted the sdcard into my ev3 and switched it on.

I then tried to network my ev3 with my host computer. The instructions for setting up usb networking for a linux host make use of ifconfig. Not all systems use ifconfig but all systems running ifconfig also have iproute2 available. So maybe in addition you can supply instructions for usb networking on linux using iproute2. That also has the advantage that you do not have to touch any config file:

ip addr add 192.168.2.1 dev usb0
ip link set usb0 up
ip route add 192.168.2.100 dev usb0

I then tried to login via ssh but did not know the password. As far as I can see, the root password is only mentioned in one bugreport and in the README.md file from the ev3dev-modules repository. Maybe it would make sense to mention the default root password in a few more places? At least in the wiki page for setting up usb ethernet networking?

Also, the instructions setup NAT are a bit too verbose because the line:

sudo iptables -P FORWARD ACCEPT

is actually not needed. And instead of doing:

echo "nameserver 192.168.0.1" >> /etc/resolv.conf

It would be better to copy the resolv.conf from your host system to the ev3 like so:

ssh [email protected] "cat > /etc/resolv.conf" < /etc/resolv.conf

Or just by using scp:

scp /etc/resolv.conf [email protected]:/etc/resolv.conf

After I was logged in, I tried to play with the LEDs only to notice that the /sys directory was not present. Apparently I had to manually insmod the respective module. Could the fact that I have to manually insmod it be mentioned somewhere in the wiki? Why are the modules not loaded automatically at bootup?

I tried to flash my LEDs and read out the button values which worked fine besides the fact that my ev3 LEDs were already flashing in some pattern for the whole time since bootup. Why are they flashing? The fact that they were flashing already made it hard to test the LEDs.

I then tried to control a moter I attached to port A via /sys/devices/platform/ev3dev/pwm/motorA/speed to no avail. What is necessary to control the motors? Writing a 1 to other files like "enable" or "power" also does not seem to change anything.

Hello,
I have a question: is there any way to use the ev3dev OS on a virtual Machine, VirtualBOX?
I have look to make it work but did not succed to emulate the Sitara AM1808 SoC CPU ARM9.
Are you using virtual machine for working? If so, can you share your method?
Thanks!

There seems to be a problem with the poweroff command:

USB 1.1 clocked from USB 2.0 PHY -- can't power it down
System halted.

The only way to workaround this is to boot into the original flash firmware and use the LEGO GUI to power off.

Hi,

I am planning to buy a Wi-Fi dongle to get rid of the USB cable.
I read the Wiki page about how to add an unsupported wifi Dongle... But in order to avoid any problem, I would like to buy a supported dongle.

I know that LEGO recommended dongle is Netgear WNA1100, which is also supported by ev3dev (according to @rhempel here #20) but it is not the cheapest one around.

For example, would a dongle using ralink rt2870sta module work? (Like Tenda W311U, which is cheap and has good reputation.)

Thank you!

Silly question, I didn't see it in your wiki, what is the default root password for your SD image?

Thanks!

I2C sensors are already partially supported in the uart-sensors branch (See #36).

More changes are coming soon.

Any chance the rtl8188eu-module binary could be updated. Upstream has some changes that improve the driver. The current binary misses some features.
If you have some notes how you built the driver, I could try this myself.

After setting up ev3dev to use CDC and connecting the device to a MacBook Pro running 10.9.1, I open the Network pref pane, click + and select CDC Composite Gadget. Nothing happens (the device is not added to the list).

The same procedure works fine inside of a VM running 10.7.

Console.app does not show any interesting error messages.

UART sensor support is being developed in the ev3dev-kernel repo.

If you want to try out UART sensors now, see mindboards/ev3dev-kernel#15

Documentation is on the wiki.

Hello,

I am trying to install a Logitech webcam on my robot and I have been encountering several problems. I am wondering if you could help me on this ?

I am using the driver Logitech Quickcam Notebookls with the following instructions: http://qce-ga.sourceforge.net/

Could you please tell me if it’s possible to make it work? I would really appreciate to have this cam working on my project.

Thanks in advance for you answer.
I join the log that I have during the subsequent steps, but it seems that there is a Kernel problem looking for X86 build. What can be the workaround?

[!] Kernel configuration file /lib/modules/3.3.0-1-ev3dev/build/.config not fou$
If the headers have been already configured properly, you might
not need it. But it would be better not to trust this, you
really should know where is your configuration file, and
copy it into its place. Often it can be found in /boot/
directory with a name like /boot/config-2.4.26 or something.
WARNING: If you press Enter, I'll try to continue anyway,
but this probably will fail. You SHOULD press Ctrl+C now.
Press Ctrl+C to quit, Enter to continue --->
[!] Can not find version.h in kernel source.
[!] Kernel source is not configured properly.
You have only kernel headers but they are not configured
properly. It's pointless trying to continue, this won't work.
Either install properly configured kernel headers or full
source with kernel configuration file. In the latter case
I can configure the kernel source using the configuration
file automatically.

Hi,
I'm new to linux (Ubuntu) and I just can't connect do my device (ev3) and don't really understand the "nfs" and "usb" pages here.

I looked at https://github.com/mindboards/ev3dev/wiki/Setting-Up-Linux-USB-Ethernet-Networking
And I don't know what are cdc_eem and cdc_subset and how to get them.
Also, when i try to run ssh [email protected] it dosent connect (is it imported which dir i am now?)

Thanks for the future help!

I just came across [this post] from Feb 3, 2013 by the Emdebian Grip maintainer. Essentially, he has said that he no longer has a need for it and wants to know if others find it useful still. I agree with him that it is not really that useful.

Just to be clear, I am only talking about using the Grip packages here and not the multistrap tool. We definitely need the multistrap tool for building the root files system since we will be rolling some of our own packages. I am just talking about which package repository that we use.

For those who are not familiar with Grip, essentially it takes existing Debian packages and makes them smaller by removing man pages and other non-essential files. Also, there are no -dev or -dbg packages.

Given that we have plenty of space on SD cards and that we are designing ev3dev for development, I propose that we use the standard Debian packages and not Grip. Here is why:

• Space is not that much of a concern.
• We do want man pages
• If you try to install -dev and -dbg packages (which we do want because we are developing, right?) from the main Debian repository along side the corresponding regular package from Grip, many of them are broken because Grip adds "em1" to the package version and the package requires an exact version match. To get around this, you have to manually "downgrade" the package to the version from the Debian repository, with gets downright difficult if there are lots of dependencies.

I have noticed that by default both options (g_ether and g_cdc) are commented out. It isn't a big deal, but I think it might make it a bit easier (for two thirds of possible users) if one of them was uncommented by default. Am I correct that they both work with Linux? If so, I would suggest picking whichever will work for the most users and set it as the default, just to remove an extra step of complication for some people.

Guys is it possible to use usb tethering on ev3....I know its possible on ubuntu desktop.

After getting 00.01.01 installed and running I seem to be missing some important stuff:

1. I tried to login as ev3dev, and discovered the user doesn't exist
2. I looked for the EV3 related devices under /sys/devices/platform/ev3dev and found nothing

Am I missing something? (no pun intended :)

For me the Wifi support does not work as described.
I use a Netgear WNA1100-100PES

1. I had to add ath9k_htc: Firmware because it was not included
   usb 1-1: ath9k_htc: Firmware - htc_9271.fw not found
   e.g. from here
   http://wireless.kernel.org/download/htc_fw/1.3/htc_9271.fw
2. After this I'm not able to connect to any Wifi.
   iwconfig & iwlib3 are missing -- How does this work for you?

Hi,

I tried using your scripts and docs but your docs are incomplete and your scripts don't work out of the box and do not seem to be very portable, among linux distributions.

To give some context, I am part of a group of people who are interested in flashing a handcrafted realtime operating system to the EV3, and we wanted to start out by trying to get a your ev3dev on it and looking around.

would you mind if I fixed the most prominent issues in your scripts and send you a pull request?

Thanks,
Andy

Hi,
I am actually testing the Test Release 3 and I have not been able to make the EV3 console work properly during and after booting. I have made several tests and seen that the Ev3console working on Com5 works only if it’s plugged in before the start of the brick, and then during the boot process the Brick sends information on the COM5 but after booting the console freezes and won't work at all, even if I try a new connection after the robot is up and running

here is part where the Ev3console does not answer; the port is still up on the windows
periperical but there is no way to communicate with it.

W: devtmpfs not available, falling back to tmpfs for /dev
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒

Are you aware of this? Do you have any info that could help me to solve this issue?

Thanks

I previously used the Lejos image, which worked out of the box with my wifi dongle and USB networking.

Neither work for me on this Debian image. The only thing that works is the serial console, but I can't easily transfer files that way.

My WiFi dongle is this one http://www.icidu.com/en/networking/wireless/nano-usb-adapter-150n.html

I use a Mac and the Lejos image showed up as RNDIS gadget.

On this image ifconfig just shows the loopback interface. Even with a wifi configuration in place. My Linux fu was insufficient to get the network going using the serial console.

Setting the LEDs via the ledXXX device files seems to be broken:

echo 1 > /sys/devices/platform/ev3dev/ui/ledleft0 
cat /sys/devices/platform/ev3dev/ui/ledleft0 
1

The LEDs stay flashing in orange all the time, independent of the ledXXX device file used.

Hello,
Just for your information, the release test 3 system is out of date. i have an issue with this so it might be helpfull for you to know it too

Sat Jan 1 07:58:22 UTC 2000
root@ev3dev:/bc-1.06# date
Sat Jan 1 07:59:50 UTC 2000
root@ev3dev:/bc-1.06# date --set="Wed Apr 16 05:59:50 UTC 2014"
Wed Apr 16 05:59:50 UTC 2014
root@ev3dev:/bc-1.06# date
Wed Apr 16 05:59:52 UTC 2014
root@ev3dev:/bc-1.06#

Regards,

This is a follow up from a discussion on another issue. @rhempel wants to know what packages should be pre-installed in the ev3dev image.

I'll start off with bsdmainutils (for hexdump).

I feel like I've gotten pretty far going through the wiki (which seems very incomplete still). I've stumbled through many missing sections and broken links, and it's hard to tell what's been completed yet or not. So just tell me if i'm just too far in, and you're still working on things...

I have the most recent SD card image working, loaded up the recent kernel update, and got wifi working.

The "Loading A Driver Module" wiki page says to find the ev3 kernel modules under the ev3dev repo in a directory named modules. That directory doesn't exist, so I assumed it meant the ev3dev-modules repo .... yet still there were no *.ko files anywhere in that repo, nor any releases... so where are these kernel extensions?

Looking around on the booted ev3 file system, I found 3 .ko files (ev3dev, ev3dev_ui, and ev3dev_pwm) under /lib/modules/3.3.0/kernel/ev3dev. So I kept going forward assuming they were up-to-date (though i'm not quite so sure now). I followed the directions to add the three to /etc/modules, rebooted, and saw that the modules were now loaded.

I was able to see and mess with the LED and button device files at /sys/devices/platform/ev3dev/ui and they all work fine...

I'm stuck at the motor section now, the files don't seem to be there from the documentation (https://github.com/mindboards/ev3dev/wiki/Using-Motors). In fact I don't see this directory at all: /sys/bus/legoev3. Is this not working yet? Seems like other people have them working. I can see motor files for A B C and D under /sys/devices/platform/ev3dev/pwm but I can't quite get them working.

Can you point me in the right direction to start messing with the motor drivers?

How do we contribute for manipulating mindstorm sensor?

Folks, I'm restricting wiki edit privileges to members with PUSH access for now.

No, we have not been hacked.

I was working on the nfs howto this morning and when I tried to push, a bunch of other changes got there ahead of me, which was a bit of a surprise. One change was to the SD card image unpack instructions, which was a correct change for the issue that the author had at the time, but was incorrect for the updated ev3dev.img.gz file.

I really do appreciate the assistance with the wiki updates, but for now, I'd like to be able to review changes to keep the content consistent. Please consider forking the wiki and issuing pull requests - once we get into a rhythm and then I'll give certain individuals PUSH privileges.

Thanks for your patience

I have an SD card that I flashed with the latest release. All of the initial setup went fine on Windows 8 and I can SSH in to the brick. But there's one thing that I'm not clear on: Does USB actually supply external network access? I couldn't tell from the wording on the guides, and although I can't get it to connect to anything (to use tools such as apt), it could be my setup.
Did I not set it up right, or is this just not a feature?

As I mentioned in an email, binary files are not very git friendly. This repo is really just a handful of scripts and already it is 13MB to download when you clone it. Perhaps this is just nit-picking, but github is not super-fast and I find it annoying to have to wait to download unnecessary files - namely the old versions of the binary files.

I propose that before we get too far down the road, we remove the binary baggage. I have created https://github.com/dlech/ev3dev-scripts in which I have done exactly this. It is back down in the KB range and downloads almost instantly.

For distributing the binary files, I suggest using the releases feature of github (more). You just tag a commit and push the tag. then you just attach the binary files to the release [here]((https://github.com/mindboards/ev3dev/releases).

Here are the options (in my personal order of preference):

1. Transfer ownership of the repo I have created to mindboards and abandon/delete this repo.
2. Do a git push -f from the repo that I have created to this repo. If we do this, all contributors will have to be aware that they have to re-clone this repo before they can do any pull requests because the commit hashes will have changed.
3. Do nothing and just have an unnecessarily large repo.

Apologies if this is a silly very basic Linux question
I installed Ubuntu 13.10 on my laptop to develop thses ideas.
I have created a micro SD card which powers the EV3 brick and gets to the welcome screen and the flashing orange lights
But I have no idea how to set up the host laptop PC to communicate with it.
I don't see any reference to usb0 anywhere in the linux files on my laptop
I am sure I am missing something very basic to Linux, but as I said I am really an absolute beginner in Linux (although this is my third attempt in over 50 years of playing with computers)

I cannot find any documentation on how to program the LCD Display, the corresponding page link in the Wiki is dead.

Can you add some links / information, please?

From #36, @rhempel says:

David, I was thinking about how to handle the issue with a single sensor, and I think the answer may be that for debugging, we build the input port driver as a module that must be loaded manually, and you can pass a parameter to either turn on PORT 1 for sensors or leave it for use as the serial console.

The next rootfs and kernel for general release should probably turn on the PORT 1 driver.

What do you think?