|
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
·
|
|
Re: [users] Re: Re: Re: Re: Re: STM32F103x port
Cool, I'll wait for your changes then.
I have a couple of updates lined up already, namely support for
interrupts on UART and GPIO input (might suquash that with the GPIO
patch anyway). There's also
Cool, I'll wait for your changes then.
I have a couple of updates lined up already, namely support for
interrupts on UART and GPIO input (might suquash that with the GPIO
patch anyway). There's also
|
By
Maciek Borzecki <maciek.borzecki@...>
·
#2566
·
|
|
Re: [users] Re: Re: Re: Re: Re: STM32F103x port
I am working right now on defining a new layer in Kconfig and reorganising Kconfig for this purpose and will take the STM32 changes and propose better structure for all architectures and existing
I am working right now on defining a new layer in Kconfig and reorganising Kconfig for this purpose and will take the STM32 changes and propose better structure for all architectures and existing
|
By
Nashif, Anas
·
#2565
·
|
|
Re: [users] Re: Re: Re: Re: Re: STM32F103x port
By
Kalowsky, Daniel <daniel.kalowsky@...>
·
#2564
·
|
|
Zephyr SDK v0.7.2 - "rm -rf /"
I downloaded the Zephyr SDK v0.7.2 last night and tried to install it this morning on my MacBook.
During the installation, I cancelled with ctrl-C and somehow it seems to have executed a "rm -rf /"
I downloaded the Zephyr SDK v0.7.2 last night and tried to install it this morning on my MacBook.
During the installation, I cancelled with ctrl-C and somehow it seems to have executed a "rm -rf /"
|
By
Mads Kristiansen <mkristian@...>
·
#2563
·
|
|
Re: [users] Re: Re: Re: Re: Re: STM32F103x port
We are looking into this and will send a proposal to address this by EOD.
Anas
We are looking into this and will send a proposal to address this by EOD.
Anas
|
By
Nashif, Anas
·
#2562
·
|
|
Re: [users] Re: Re: Re: Re: Re: STM32F103x port
Do we have a consensus on this matter then? Did you get a chance to
discuss this internally?
Cheers,
--
Maciek Borzecki
Do we have a consensus on this matter then? Did you get a chance to
discuss this internally?
Cheers,
--
Maciek Borzecki
|
By
Maciek Borzecki <maciek.borzecki@...>
·
#2561
·
|
|
Re: FRDM-K64 GPIO driver name
Thanks Tomasz,
It compiles :)
I will try lator today with a real GPIO test.
Thanks again.
/Anders
Thanks Tomasz,
It compiles :)
I will try lator today with a real GPIO test.
Thanks again.
/Anders
|
By
Anders Dam Kofoed <adk@...>
·
#2560
·
|
|
Re: FRDM-K64 GPIO driver name
Hi Anders,
According to arch/arm/soc/fsl_frdm_k64f/Kconfig GPIO and GPIO_K64 are
set by default.
Verify you get these in your output/.config
The name you should use is GPIO_K64_<X>_DEV_NAME (where
Hi Anders,
According to arch/arm/soc/fsl_frdm_k64f/Kconfig GPIO and GPIO_K64 are
set by default.
Verify you get these in your output/.config
The name you should use is GPIO_K64_<X>_DEV_NAME (where
|
By
Tomasz Bursztyka
·
#2559
·
|
|
FRDM-K64 GPIO driver name
Hi,
I am trying to use GPIO on my Freescale FRDM-K64 board. However, I cannot seem to find the driver name. It from this page that the driver name should be something like
Hi,
I am trying to use GPIO on my Freescale FRDM-K64 board. However, I cannot seem to find the driver name. It from this page that the driver name should be something like
|
By
Anders Dam Kofoed <adk@...>
·
#2558
·
|
|
FRDM-K64 PRINT not working
Hi,
I have a Freescale FRDM-K64 board. I cannot get the samples/hello_world/microkernel to work. Compiling with this:
# make O=out-arm BOARD=frdm_k64f
It compiles fine and the out-arm/zephyr.bin can
Hi,
I have a Freescale FRDM-K64 board. I cannot get the samples/hello_world/microkernel to work. Compiling with this:
# make O=out-arm BOARD=frdm_k64f
It compiles fine and the out-arm/zephyr.bin can
|
By
Anders Dam Kofoed <adk@...>
·
#2557
·
|