|
flash tinytile
Hello all,
I am trying to flash my tinytile. When I use the commands make BOARD=tinytile flash or make flash or the dfu-util command, I get the errors below. Tinytile does not have a jtag connection
Hello all,
I am trying to flash my tinytile. When I use the commands make BOARD=tinytile flash or make flash or the dfu-util command, I get the errors below. Tinytile does not have a jtag connection
|
By
Tamra Oyama <tamrako@...>
·
#1033
·
|
|
Re: How to reduce footprint and size of applications in Zephyr
I see. That makes a lot of sense. Thank you Maciek!
I have another question, if you dont mind.
I have an app that's taking about ~5MB of RAM and ~5.6MB of ROM judging from the 'ram_report' and
I see. That makes a lot of sense. Thank you Maciek!
I have another question, if you dont mind.
I have an app that's taking about ~5MB of RAM and ~5.6MB of ROM judging from the 'ram_report' and
|
By
Yie
·
#1032
·
|
|
Re: How to reduce footprint and size of applications in Zephyr
qemu-system-arm is just a VM that can emulate, among others, Cortex-M
MCUs. `qemu_cortext_m3` board is in fact emulated by qemu. Memory
usage of a running Qemu process does not directly (or
qemu-system-arm is just a VM that can emulate, among others, Cortex-M
MCUs. `qemu_cortext_m3` board is in fact emulated by qemu. Memory
usage of a running Qemu process does not directly (or
|
By
Maciek Borzecki <maciek.borzecki@...>
·
#1031
·
|
|
Re: How to reduce footprint and size of applications in Zephyr
Hi Thiago,
Thank you so much for the reply. I am running Zephyr on Linux and building the hello_world app on ARM using qemu_cortex_m3.
I've got the numbers from the following:
The 8MB of memory is
Hi Thiago,
Thank you so much for the reply. I am running Zephyr on Linux and building the hello_world app on ARM using qemu_cortex_m3.
I've got the numbers from the following:
The 8MB of memory is
|
By
Yie
·
#1030
·
|
|
Re: How to reduce footprint and size of applications in Zephyr
Hi Yie,
That definitely isn't right. In which environment are you running Zephyr, and how are you measuring this?
Try 'make rom_report' and 'make ram_report' to get a nice report of how much each
Hi Yie,
That definitely isn't right. In which environment are you running Zephyr, and how are you measuring this?
Try 'make rom_report' and 'make ram_report' to get a nice report of how much each
|
By
Thiago Silveira
·
#1029
·
|
|
Re: RFC: Stopping Zephyr networking from being painful by enabling error logging by default
Hello David,
I appreciate the detailed response, with many points coinciding with
what I wrote previously. And my hypothesis that many of these points
would apply not just to "hobbyist" usage, but
Hello David,
I appreciate the detailed response, with many points coinciding with
what I wrote previously. And my hypothesis that many of these points
would apply not just to "hobbyist" usage, but
|
By
Paul Sokolovsky
·
#1028
·
|
|
How to reduce footprint and size of applications in Zephyr
Hi,
I read that Zephyr allows small footprint of a few KBs. However, the sample hello world application already takes up 8MB of memory and has a size of 3.8MB. I am not sure if I am running this
Hi,
I read that Zephyr allows small footprint of a few KBs. However, the sample hello world application already takes up 8MB of memory and has a size of 3.8MB. I am not sure if I am running this
|
By
Yie
·
#1027
·
|
|
HTTP Request Timeout Not Working
Hi,
I am currently running a HTTP client in QEMU_cortex_m3 and I was trying to set the timeout for the http_client_send_req(..) function and it doesn't seem to work.
It still does not return
Hi,
I am currently running a HTTP client in QEMU_cortex_m3 and I was trying to set the timeout for the http_client_send_req(..) function and it doesn't seem to work.
It still does not return
|
By
Yie
·
#1026
·
|
|
Zephyr SDK issue tracking moved to github
Hi,
As part of the migration to Github Issues, we moved the SDK Jira project and made the Jira project read-only. All new SDK issues should be reported to
Hi,
As part of the migration to Github Issues, we moved the SDK Jira project and made the Jira project read-only. All new SDK issues should be reported to
|
By
Nashif, Anas
·
#1025
·
|
|
Re: RFC: Stopping Zephyr networking from being painful by enabling error logging by default
I definitely think it makes sense to do this by default for our QEMU based targets, since they have lots of ram and we don't gather performance metrics for emulated targets.
Andrew
I definitely think it makes sense to do this by default for our QEMU based targets, since they have lots of ram and we don't gather performance metrics for emulated targets.
Andrew
|
By
Boie, Andrew P
·
#1024
·
|
|
Re: RFC: Stopping Zephyr networking from being painful by enabling error logging by default
Re (1): in this spirit, I would also enable CONFIG_ASSERT by default...
Re (4): SYS_LOG itself is not the issue, it is the layers added on top of it to enable logging in subsystems such as the IP
Re (1): in this spirit, I would also enable CONFIG_ASSERT by default...
Re (4): SYS_LOG itself is not the issue, it is the layers added on top of it to enable logging in subsystems such as the IP
|
By
Nashif, Anas
·
#1023
·
|
|
Re: RFC: Stopping Zephyr networking from being painful by enabling error logging by default
My views on this topic:
1) Right now we have very inconsistent error/debug logging. In lots of places in the kernel, when a bad situation is encountered the problem is simply reported with a
My views on this topic:
1) Right now we have very inconsistent error/debug logging. In lots of places in the kernel, when a bad situation is encountered the problem is simply reported with a
|
By
Boie, Andrew P
·
#1022
·
|
|
Re: RFC: Stopping Zephyr networking from being painful by enabling error logging by default
This is an incredibly astute comment.
I am coming to the RTOS world from years of Unix & Linux development, with a recent foray into the Arduino world, which has led me to slightly larger systems
This is an incredibly astute comment.
I am coming to the RTOS world from years of Unix & Linux development, with a recent foray into the Arduino world, which has led me to slightly larger systems
|
By
david zuhn
·
#1021
·
|
|
Adding Nucleo-F030R8 support to Zephyr - CI fails due to low SOC RAM (8k)
Hello Macjie,
the pull request #1103 seems to fail some CI tests due to not enough RAM space (8k only).
The missing amount of RAM is above 1.5k so disabling the RAM vector table (~400 bytes) will not
Hello Macjie,
the pull request #1103 seems to fail some CI tests due to not enough RAM space (8k only).
The missing amount of RAM is above 1.5k so disabling the RAM vector table (~400 bytes) will not
|
By
Bobby
·
#1020
·
|
|
Re: RFC: Stopping Zephyr networking from being painful by enabling error logging by default
Hello Luiz,
By
Paul Sokolovsky
·
#1019
·
|
|
Re: RFC: Stopping Zephyr networking from being painful by enabling error logging by default
Hi Paul,
<paul.sokolovsky@...> wrote:
When you use a presentation which says:
Main benefits taking zephyr in use would come from good ble and tcp/ip stacks
...
I understand it can be
Hi Paul,
<paul.sokolovsky@...> wrote:
When you use a presentation which says:
Main benefits taking zephyr in use would come from good ble and tcp/ip stacks
...
I understand it can be
|
By
Luiz Augusto von Dentz
·
#1018
·
|
|
Re: RFC: Stopping Zephyr networking from being painful by enabling error logging by default
Hello Piotr,
By
Paul Sokolovsky
·
#1017
·
|
|
Re: RFC: Stopping Zephyr networking from being painful by enabling error logging by default
Hello Piotr,
By
Paul Sokolovsky
·
#1016
·
|
|
Re: Counter API ambiguity.
Hi,
Analysing the problem here, with a 32-bit integers, only 31-bit value range can be used to set alarms that expire after a rollover of 32-bit clock counts.
This is considering that we want to
Hi,
Analysing the problem here, with a 32-bit integers, only 31-bit value range can be used to set alarms that expire after a rollover of 32-bit clock counts.
This is considering that we want to
|
By
Chettimada, Vinayak Kariappa
·
#1015
·
|
|
the zephyr device-tree mechanism seems not identical with the linux dirver, right?
Hi all:
from the dtc compiler command in Makefile.lib document, the device tree of zepher project are compiler to "DTS" file, not the blob file "DTB" type, so, and then convert to header
Hi all:
from the dtc compiler command in Makefile.lib document, the device tree of zepher project are compiler to "DTS" file, not the blob file "DTB" type, so, and then convert to header
|
By
曹子龙
·
#1014
·
|