|
Re: Zephyr SDK v0.7.2 - "rm -rf /"
Hi,
I had the same issue earlier. I filed the bug which wasn’t able to save you, Mads.
https://jira.zephyrproject.org/browse/ZEP-88
I was lucky enough not to run it under root.
Sakari
From:
Hi,
I had the same issue earlier. I filed the bug which wasn’t able to save you, Mads.
https://jira.zephyrproject.org/browse/ZEP-88
I was lucky enough not to run it under root.
Sakari
From:
|
By
Poussa, Sakari
·
#2583
·
|
|
Re: Zephyr SDK v0.7.2 - "rm -rf /"
Yes, this is probably what happened :)
Yes, this is probably what happened :)
|
By
Mads Kristiansen <mads.kristiansen@...>
·
#2585
·
|
|
Re: FRDM-K64 GPIO driver name
Hi idups
Yes, I do see flashing tx lights on the board when typing something in the "screen /dev/ttyACM0". I have also tried all possible options in the "make menuconfig" but with no luck.
Regarding
Hi idups
Yes, I do see flashing tx lights on the board when typing something in the "screen /dev/ttyACM0". I have also tried all possible options in the "make menuconfig" but with no luck.
Regarding
|
By
Anders Dam Kofoed <adk@...>
·
#2582
·
|
|
Re: FRDM-K64 GPIO driver name
Hi Maureen,
Thanks for taking the time.
I am not sure how I would set the PORTB_PCR[22] as an output (red led). I have tried a few things including looking at outdir/.config and changing the driver
Hi Maureen,
Thanks for taking the time.
I am not sure how I would set the PORTB_PCR[22] as an output (red led). I have tried a few things including looking at outdir/.config and changing the driver
|
By
Anders Dam Kofoed <adk@...>
·
#2581
·
|
|
Re: RFC: Change returning type from Pinmux APIs
Short version +1
By
Kalowsky, Daniel <daniel.kalowsky@...>
·
#2580
·
|
|
RFC: Change returning type from Pinmux APIs
Hi all,
While I was working on the errno transition patchset, I realized all driver
APIs (i2c, spi, gpio, etc.) return 'int' type, but pinmux APIs. For the sake
of consistency, I think we should
Hi all,
While I was working on the errno transition patchset, I realized all driver
APIs (i2c, spi, gpio, etc.) return 'int' type, but pinmux APIs. For the sake
of consistency, I think we should
|
By
Andre Guedes <andre.guedes@...>
·
#2579
·
|
|
Re: FRDM-K64 GPIO driver name
Hey Marueen,
I'm wondering now, because I've searched for the multiplex-lib for the K64
and found nothing (But for the arduinos). So I thought: only the first
function of every pin/port is accessable.
Hey Marueen,
I'm wondering now, because I've searched for the multiplex-lib for the K64
and found nothing (But for the arduinos). So I thought: only the first
function of every pin/port is accessable.
|
By
Idupsle <idupsle@...>
·
#2578
·
|
|
Re: FRDM-K64 GPIO driver name
Hi Anders,
I took a quick look and ran your code, and it appears that the pinmux for PTB22 is not configured correctly. The register field PORTB_PCR[MUX] is set to 0 when it should be set to 1. You
Hi Anders,
I took a quick look and ran your code, and it appears that the pinmux for PTB22 is not configured correctly. The register field PORTB_PCR[MUX] is set to 0 when it should be set to 1. You
|
By
Maureen Helm
·
#2577
·
|
|
Re: FRDM-K64 GPIO driver name
Hi,
I don't know what's happening with your UART but regarding the GPIO, I think
the problem is K64 gpio driver doesn't configure the pin as GPIO when you
call the gpio_pin_configure function.
I got
Hi,
I don't know what's happening with your UART but regarding the GPIO, I think
the problem is K64 gpio driver doesn't configure the pin as GPIO when you
call the gpio_pin_configure function.
I got
|
By
Carlos Carrizosa <c.carrizosa@...>
·
#2586
·
|
|
Re: FRDM-K64 GPIO driver name
I did copy it to the MBED Mount Point (Actual Firmware)...
Besides, I forgot that I played a little bit with the kernel-config, which
isn't present in my prj.conf... but I'm sorry to say that I'm away
I did copy it to the MBED Mount Point (Actual Firmware)...
Besides, I forgot that I played a little bit with the kernel-config, which
isn't present in my prj.conf... but I'm sorry to say that I'm away
|
By
Idupsle <idupsle@...>
·
#2576
·
|
|
Re: FRDM-K64 GPIO driver name
Hi,
I have tried your settings above and also with the following - but it still does not work:
CONFIG_STDOUT_CONSOLE=y
CONFIG_PRINTK=y
I am using the latest firmware 226 and programming the board
Hi,
I have tried your settings above and also with the following - but it still does not work:
CONFIG_STDOUT_CONSOLE=y
CONFIG_PRINTK=y
I am using the latest firmware 226 and programming the board
|
By
Anders Dam Kofoed <adk@...>
·
#2575
·
|
|
Re: Zephyr SDK v0.7.2 - "rm -rf /"
Hi Anas,
Yes, that is correct. I was installing it on OSX. Cannot really give more details about what happened except that I pressed ctrl-C during the installation. It was the only shell I had open at
Hi Anas,
Yes, that is correct. I was installing it on OSX. Cannot really give more details about what happened except that I pressed ctrl-C during the installation. It was the only shell I had open at
|
By
Mads Kristiansen <mkristian@...>
·
#2574
·
|
|
build zephyr failed
I have installed gcc,g++,and sdk , the environment shows that
I have installed gcc,g++,and sdk , the environment shows that
|
By
ZhangLei <ezio_zhang@...>
·
#2584
·
|
|
Re: Zephyr SDK v0.7.2 - "rm -rf /"
Mads,
Were you trying to install the SDK on Mac OS?
If yes, this issue will be addressed in the latest SDK drop which will be released today.
Anas
Mads,
Were you trying to install the SDK on Mac OS?
If yes, this issue will be addressed in the latest SDK drop which will be released today.
Anas
|
By
Nashif, Anas
·
#2573
·
|
|
FYI: Gerrit and JIRA are down
Hi,
The issue has been reported and being addressed. Still not known what the issue is exactly :(
Anas
Hi,
The issue has been reported and being addressed. Still not known what the issue is exactly :(
Anas
|
By
Nashif, Anas
·
#2572
·
|
|
Re: Zephyr SDK v0.7.2 - "rm -rf /"
Hi Mads,
<mkristian(a)outlook.com> wrote:
I was curious on how this could happen. So I unpacked the installer
script (using "--noexec --target somedir --keep options") and looked
at setup.sh. This
Hi Mads,
<mkristian(a)outlook.com> wrote:
I was curious on how this could happen. So I unpacked the installer
script (using "--noexec --target somedir --keep options") and looked
at setup.sh. This
|
By
Anderson Lizardo <anderson.lizardo@...>
·
#2571
·
|
|
Some emails from devel mailing list does arrive to my inbox
Hi everyone,
is it just me or everyone does not receive some emails to their inbox
from the devel mailing list?
For example I did not receive any email for the threads:
[RFC] GPIO API
Hi everyone,
is it just me or everyone does not receive some emails to their inbox
from the devel mailing list?
For example I did not receive any email for the threads:
[RFC] GPIO API
|
By
Yannis Damigos
·
#2570
·
|
|
Re: [RFC] GPIO API changes
Hi Vinicius,
Rethinking about that, while doing the proper patch-set. You've got good
point.
I am making it useless if the user has not set a callback through
gpio_set_callback()
(old way of doing,
Hi Vinicius,
Rethinking about that, while doing the proper patch-set. You've got good
point.
I am making it useless if the user has not set a callback through
gpio_set_callback()
(old way of doing,
|
By
Tomasz Bursztyka
·
#2569
·
|
|
Re: FRDM-K64 GPIO driver name
Hi, Reffering to my post in users, I wasn't successfully activating the
LEDs, but I got the debug output. See below
I've following
Hi, Reffering to my post in users, I wasn't successfully activating the
LEDs, but I got the debug output. See below
I've following
|
By
Idupsle <idupsle@...>
·
#2568
·
|
|
Re: FRDM-K64 GPIO driver name
Hi Thomasz,
Yesterday I tried with the following source code - but nothing happens :(
Nothing blinks. I programming it by copying the outdir/zephyr.bin onto the MBED folder. The board seems to "eat"
Hi Thomasz,
Yesterday I tried with the following source code - but nothing happens :(
Nothing blinks. I programming it by copying the outdir/zephyr.bin onto the MBED folder. The board seems to "eat"
|
By
Anders Dam Kofoed <adk@...>
·
#2567
·
|