Can you please open an issue herehttps://github.com/zephyrproject-rtos/zephyr/issues with all details and what sample code you are building and how to reproduce this please, this thread starting to

Hi Anas, I opened minicom using minicom -D /dev/ttyUSB0. This was after making the BOARD=arduino_101 even though I'm using the tinyTILE. Opening minicom using ACM0 results in minicom freezing and none

Which serial device do you connect minicom to? How is the device connected to your host? TinyTILe board is configured to use USB CDC, so the console output is on ttyACM, if you flash the Arduino board

On Fri, Oct 13, 2017 at 6:47 AM Li, Jun R <jun.r.li@...> wrote: Yeah sorry I meant "make BOARD=tinytile". Although it works and applications can flash with this command. When I open minicom to view

Please try “make BOARD=tinytile”. The board name should be exactly same as “boards/x86/tinytile”. From: <zephyr-devel-bounces@...> on behalf of Jie Zhou <zhoujie@...> Date: Friday, October

Hi, Last night, a pull request of mine was merged which uses a Python script to flash binaries ("make flash"): https://github.com/zephyrproject-rtos/zephyr/pull/4304 If you run into any problems, you

Jie, Great. I believe that cleaning up the CONFIG setting would fix the tinyTile build. Graham

Hey Graham, Thanks for the help! It worked. To flash on tinyTILE, do make BOARD=arduino_101 flash. Since they are using the same Intel curie chip, it will work. Interesting that BOARD=tinyTILE doesn't

I find myself in a situation where my platform keeps going through the __reset and I’m not sure why? How does one debug something like this with Zephyr? My target is a FRDM-KW41Z board.

Hi, First bug fix release for 1.9 with many Bluetooth related bug fixes, see the release page for details: https://github.com/zephyrproject-rtos/zephyr/releases/tag/zephyr-v1.9.1

Hi, RC5 has been released and available from https://github.com/zephyrproject-rtos/meta-zephyr-sdk/releases/tag/0.9.2-rc5 This release removes the QEMU update and restores the original

I created the PR https://github.com/zephyrproject-rtos/zephyr/pull/4298 Yannis

Thanks Erwan, It works now. I will create a PR for it Yannis

Hello Erwan, Thanks for the help; the CONFIG_GPIO_STM32_PORTD was missing. I'll send a PR to add this to stm32f4_disco_defconfig later today. Regarding debugging, I was using debug before, but was

Hi, I don't have time to test this yet, but looking into STM32F303 reference manual, it seems that I2C on F3 is clock independent and hence, we should sepcify clock before using it. It seems this case

Hi Daniel, I was trying to get I2C working on stm32f3_disco a couple of months ago. You could find my local branch here https://github.com/ydamigos/zephyr/tree/f3disco (it needs a rebase to the master

Hi, I’m working on a project that needs I2C functionality on a STM32F0 Chip. Since STM32F0 support is not yet merged into zephyr (I’m

Hi Pushpal, Regarding the blinky issue. It's happening since CONFIG_GPIO_STM32_PORTD is not activated. You should add it in board defconfig. Then, regarding the debug issue. Have you tried make

Hi Graham, Hmm interesting, which CONFIG settings? Also I want to use tinyTILE for a bluetooth application that I am working on. I need tinyTILE for its wearable size. For flashing on to tinyTILE, all

Jie, My board is in use at this time so I cannot do this test for you. However I did look at the Bluetooth beacon sample and I see that it is setting some Bluetooth related CONFIG settings that