Re: Debugging blecent application on nrf52dk

Hi Will, I'm not building the controller lib for the image that runs on the stm32f4Discovery board. I'm building it as a Host Only. So I build the host, HCI, and uart transport. Broadcom's Bluetooth core is really a BlackBox to me, I don't have any way to debug what's going on there (except maybe

Re: Debugging blecent application on nrf52dk

Hi Chris, On Thu, Mar 16, 2017 at 2:30 PM, Christopher Collins wrote: > Hi Pritish, > > On Thu, Mar 16, 2017 at 01:50:12PM -0700, Pritish Gandhi wrote: > > Hi All, > > I'm trying to run blecent on an nrf52dk and am running the bleprph > > application on another BLE module

Re: Target download pathing issues

Testing here it correctly prints out that it's impossible to execute... Maybe adding "-ldebug" to the newt load command might show some extra relevant info. On Thu, Mar 16, 2017, at 06:51 PM, Fabio Utzig wrote: > Are your scripts executable: chmod +x ? > > On Thu, Mar 16, 2017, at 05:57 PM,

Re: Target download pathing issues

Are your scripts executable: chmod +x ? On Thu, Mar 16, 2017, at 05:57 PM, Jacob Rosenthal wrote: > Im seeing all sorts of errors with targets on my osx 10.12.3 > > Some targets cant find download script > > Error: fork/exec /Users/jacobrosenthal/Downloads/xxx/repos/apache- >

Re: Debugging blecent application on nrf52dk

I do not think there is a simple way to debug this. As Chris points out, the first problem is a LL control procedure timeout. I think I can help figure some things out there. There is a function called ble_ll_ctrl_proc_rsp_timer_cb. If you set a breakpoint at this function in the debugger when

Re: Debugging blecent application on nrf52dk

Hi Pritish, On Thu, Mar 16, 2017 at 01:50:12PM -0700, Pritish Gandhi wrote: > Hi All, > I'm trying to run blecent on an nrf52dk and am running the bleprph > application on another BLE module (stm32f4discovery talking to a broadcom > BLE core). Anyways, when try to run blecent it seems like I

Target download pathing issues

Im seeing all sorts of errors with targets on my osx 10.12.3 Some targets cant find download script Error: fork/exec /Users/jacobrosenthal/Downloads/xxx/repos/apache- mynewt-core/hw/bsp/bbc_microbit/microbit_download.sh: no such file or directory and if I ls

Debugging blecent application on nrf52dk

Hi All, I'm trying to run blecent on an nrf52dk and am running the bleprph application on another BLE module (stm32f4discovery talking to a broadcom BLE core). Anyways, when try to run blecent it seems like I successfully connect to the peripheral and are able to discover it, however after that

Minor typo in tutorial

Hi, just letting you know, that on https://mynewt.apache.org/v0_9_0/os/tutorials/blehci_project/ the command below "Load the image" should probably read: $ newt -v load myble2 Cheers, Matthias

Re: What is the different between drivers and hal module?

I agree, right place for this would be drivers. Standard coding_style rules apply. Regards, Vipul Rahane > On Mar 16, 2017, at 10:32 AM, Sterling Hughes > wrote: > > Belongs in drivers IMO. Cool! Having a LCD driver would be awesome, and I’d > love to

Re: What is the different between drivers and hal module?

Belongs in drivers IMO. Cool! Having a LCD driver would be awesome, and I’d love to get a GFX library into (or compatible with) Mynewt as well. On 16 Mar 2017, at 6:47, Fabio Utzig wrote: I believe the agreed on convention is that the "hal" directory contains SOC drivers that are available

Re: slinky with REBOOT_LOG_FCB, inside log_reboot_pkg_init error

On Thu, Mar 16, 2017 at 10:23 AM, Alan Graves wrote: > > Perhaps there is already a mechanism in MyNewt to persist system > parameters other than a full blown Flash File System? > Config package (in sys/config) can use FCB as its data store (in fs/fcb), which is

RE: slinky with REBOOT_LOG_FCB, inside log_reboot_pkg_init error

Yes I only noticed a problem when I had something other than valid reboot_log_sector data, i.e. the first time I programmed and ran the image over top of something else. The idea of course is to retain the log across reboots so we would need to do some kind of sanity check on the log data prior

Re: Problem to use newtmgr through ble

Hi Chris, newtmgr probably requires just CAP_NET_ADMIN to open either raw or user channel socket so you could do sth like: sudo setcap cap_net_admin=+ep `which newtmgr` And no need for sudo anymore. Best regards, Andrzej On Thu, Mar 16, 2017 at 4:35 PM, Christopher Collins

Re: Problem to use newtmgr through ble

Hi Then, I have found that I need to run newtmgr as root when using ble (e.g., sudo newtmgr ...) Chris On Thu, Mar 16, 2017 at 05:22:01PM +0800, then yon wrote: > Dear Support, > > Anyone have answer on this? > > Some updates on the newtmgr setting: > > Connection profiles: BT01: type=ble,

Re: What is the different between drivers and hal module?

I believe the agreed on convention is that the "hal" directory contains SOC drivers that are available on every supported MCU model. Everything else should go to "drivers" (which would be the case for your LCD driver). On Thu, Mar 16, 2017, at 10:42 AM, Louie Lu wrote: > Hi everyone, > > I'm now

What is the different between drivers and hal module?

Hi everyone, I'm now trying to make STM32F429 LCD work, the early stage video can saw at: https://www.youtube.com/watch?v=TIhjllDWWTI How should I choose this code to put under drivers or hw/hal, is there any rules or convention to follow? Thanks, Louie.

Re: Adding LCD drivers to STM32F429 cause linked error

* stm32f4xx_hal_conf.h 2017-03-16 18:14 GMT+08:00 Louie Lu : > Da, I forgot to enable module at `stm32f4_bsp.h` > > it work now. > > Louie. > > 2017-03-16 16:12 GMT+08:00 Louie Lu : > >> Hi everyone, >> >> I'm now trying to add LCD driver for STM32F429, but get a

Re: Adding LCD drivers to STM32F429 cause linked error

Da, I forgot to enable module at `stm32f4_bsp.h` it work now. Louie. 2017-03-16 16:12 GMT+08:00 Louie Lu : > Hi everyone, > > I'm now trying to add LCD driver for STM32F429, but get a linked error > that I can't resolve. > > The apps/lcdtest/src/main.c include the lcd driver

Re: Problem to use newtmgr through ble

Dear Support, Anyone have answer on this? Some updates on the newtmgr setting: Connection profiles: BT01: type=ble, connstring='nimble-bleprph' Whenever i sent newtmgr command i get the following: 2017/03/16 17:11:35 dev: hci0 up 2017/03/16 17:11:35 dev: hci1 up Error: no supported devices

Adding LCD drivers to STM32F429 cause linked error

Hi everyone, I'm now trying to add LCD driver for STM32F429, but get a linked error that I can't resolve. The apps/lcdtest/src/main.c include the lcd driver header, and then used the defined function "hal_lcd_init": #include "stm32f429_lcd/stm32f429_lcd.h" int main() {

Re: slinky with REBOOT_LOG_FCB, inside log_reboot_pkg_init error

Yes, that is correct. You will get an error if you don’t erase it because you have some corrupt data in that sector. If you erase the flash using opened+gdb, it should fix your issue. Another way is the way I mentioned earlier: in fcb_init() when the initialization of reboot_log fails, erase