Re: [JIRA-MYNEWT-384] Query

On Fri, Jun 16, 2017, at 08:08 AM, amit mehta wrote: > On Sun, Jun 11, 2017 at 9:30 PM, amit mehta wrote: > > Eclipse Paho has multiple implementation of MQTT client. I have > > tried integrating the one [1], for the embedded targets, which works > > fine (Build works fine).

Re: #if directives and the MYNEWT_VAL(..) macro

ndexes as well.> > Lastly, this probably affects more than just I2C as the #if > MYNEWT_VAL(..) pattern is used many places in the core.> > > Thoughts? I think the "value" in the syscfg.yml files usually means a flag to enable/disable something. I2C_0 with value 0 means it's disabled, 1 means it is enabled. Also looking at "hw/mcu/nordic/nrf52xxx/src/hal_i2c.c", it seems to only use the value as an enable/disable flag, not as an indexing value. Cheers, Fabio Utzig

Re: newtmgr macos issues: newtmgr Killed: 9 and cgo argument has Go pointer to Go pointer

I have 8.3.2 too. On Tue, Apr 25, 2017, at 04:01 PM, Jacob Rosenthal wrote: > @fabio whats your xcode version? Im on 8.3.2 and not being offered > anything > new atm. > > On Tue, Apr 25, 2017 at 11:47 AM, Fabio Utzig <ut...@utzig.org> wrote: > > > I had t

Re: Query on repository and packaging

> I was little tired by the time, I hit the send button, hence I think, I > did > not made the question very clear, hence let me rephrase the question; > Is this approach of creating repository, indeed correct ? or I'm missing > something ? Looks correct to me.

Re: Query on repository and packaging

Very cool Amit! Although your email is basically informational, I would suggest one change: you should be using "runtimeco" instead of "runtimeinc". We're moving projects there, in your case the correct repo would be: https://github.com/runtimeco/mynewt_nordic Cheers, Fabi

Re: STM32F3 Discovery blinky tutorial error

On Mon, Mar 20, 2017, at 09:09 AM, Pradeep Sanjeewa wrote: > Hi Fabio Utzig, > > I thought MIPS port is already implemented. > Imagination Technologies ci40 board is already ported to mynewt which has > a > MIPS mcu. > Isn't it? > > Correct me if I'm wrong. Yes, t

Re: STM32F3 Discovery blinky tutorial error

e a lot of work and Julian from Img Tec already announced, like a month ago, that he's working on it and I think he also did the MIPS port, so it would be a good idea to reach out to him or wait for the MCU port before tackling a bit task like that. Cheers, Fabio Utzig

Re: Problem to use newtmgr through ble

On Fri, Mar 17, 2017, at 08:24 AM, then yon wrote: > Dear Chris, > > When i put sudo newtmgr -c BT01 stat list, it gave me sudo: newtmgr: > command not found. It looks like sudo is not preserving your user path, you could try: sudo "PATH=$PATH" newtmgr -c BT01 stat list

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

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: 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

Re: New STM32F427xx port

On Mon, Mar 13, 2017, at 06:07 PM, Alan Graves wrote: > Yes it might. I noticed that the CC3100 Wi-Fi module interface is using > either a SPI connection or UART+RTS/CTS to communicate with the MCU. I > believe the module is probably configured to use only one interface. A > couple of years ago I

Re: New STM32F427xx port

Hi Alan, Interesting board, it has a CC3100 wifi chip which would be nice to have supported by Mynewt! :P Looks like a good candidate for a BSP. The .NET Micro Framework compatibility can be ignored in our case. Cheers, Fabio Utzig On Mon, Mar 13, 2017, at 02:45 PM, Alan Graves wrote: >

Re: New STM32F427xx port

to "main" at the end of the Reset_Handler. You need to change it to jump to "_start". 2) There is already zeroing of the "bss" section, but you also need to add zeroing of "corebss". Of course the linker script also has to be updated accordingly (sections/

Re: os_msys_get_pkthdr always return null

(comment out) the calls to "fs_close" just after the "done:" label. The file in question is "fs/fs/src/fsutil.c". Please do this change and check if it solves your problem. Cheers, Fabio Utzig On Wed, Feb 15, 2017, at 12:58 AM, then yon wrote: > Dear Chris, > &g

Re: file system fs/fs not working after updated to latest myNewt

me testing today to try to find what is causing your problem with NFFS (or with no FS enabled). What FS operations are you doing? Are you using any of the fs_* calls? Could you copy/paste some of your FS usage code as a gist (or pastebin, etc)? Cheers, Fabio Utzig On Mon, Feb 13, 2017, at 02:57 AM

Re: about cannot executable newt.exe

quot; path usage instead of using the path library. You also need all the tooling like git, gcc, etc and making it compatible with MSVC would probably be too much work. Cheers, Fabio Utzig On Fri, Feb 10, 2017, at 12:04 PM, David G. Simmons wrote: > Unfortunately, Newt is not available na

Re: file system fs/fs not working after updated to latest myNewt

No sure what you mean by "removed this fs part". What FS are you using? Could you provide the output of "newt target dep" and "newt target revdep"? Cheers, Fabio Utzig On Fri, Feb 10, 2017, at 10:59 AM, then yon wrote: > Dear Support, > > After updated

Re: Tutorial problem with the Docker Container

On Thu, Jan 19, 2017, at 12:44 PM, Li-Chun Ko wrote: > Hi all, > > 2. Error message when executing $newt test all: > > lcko@lcko-VirtualBox:~/dev/go/myproj$ cd repos > lcko@lcko-VirtualBox:~/dev/go/myproj/repos$ $newt test all > Testing package @apache-mynewt-core/boot/boot_serial/test >

Re: Tutorial problem with the Docker Container

On Thu, Jan 19, 2017, at 06:55 AM, Li-Chun Ko wrote: > > In addition, I also found the conmend: > > newt test all > > did not work in Linux and resulted in compiling errors and somehow I feel > there is some issues with the newt install commend. Hi, could you copy the error here?

Adding support for an external SPI flash (AT45DB)

al_flash as an extra pointer field, something like "device_priv" or similar that points to whatever extra data the needs... Anyway, still needs some polish but a good start I think! Cheers, Fabio Utzig

Re: Supporting multiple filesystems and "block" devices

ust and "drive" names are an aberration, I would be OK at giving a try on implementing a proper VFS! Cheers, Fabio Utzig

Supporting multiple filesystems and "block" devices

now which SPI to use, which configuration, etc. This will probably also add another parameter to disk_register with the said context struct. I'll be fixing the above issues on a new PR. Please review the current PR, add suggestions, etc. Cheers, Fabio Utzig

Re: macOS Sierra Support

If no "brew cleanup" was run, you can always "brew switch" to another version. On Tue, Jan 10, 2017, at 04:00 PM, David G. Simmons wrote: > Oh, yeah, because then it updates your gcc toolchain, and then all hell > breaks loose. There is a way to back one update out. I think I documented > that

Re: Getting Unhandled interrupt (17)

ne your own handler. Best, Fabio Utzig

Re: Compile and build time, any way to speed up?

inc/newt-docker/blob/master/Makefile#L15 Att, Fabio Utzig On Fri, Jan 6, 2017, at 01:14 AM, Cris Frusina wrote: > Stupid question... Is there any way to try out the development branch > while using the docker method on a Windows machine? > > Cris > > > On 1/5/2017 8:20 PM, S

Re: Getting Unhandled interrupt (17)

Hi, The unhandled exception is most probably caused by missing to define a handler function. Before enabling the IRQ, try adding something like (assuming the IRQ you want to handle is SWI0_EGU0_IRQ): NVIC_SetVector(SWI0_EGU0_IRQn, (uint32_t) my_swi0_handler); Att, Fabio Utzig On Fri, Jan 6

Re: Schedule task with strict fixed timing and variable workload

(timeout); } } This should probably work but having the functionality in the OS would be cool! Cheers, Fabio Utzig On Mon, Dec 26, 2016, at 09:01 AM, Kevin Townsend wrote: > Is there a mechanism in the scheduler to fire a task at a specific > interval, where the task execution time itself

Re: newt build error

Alan, Your Ubuntu is i686 right? That would make sense because 0x is really too big for an int (in 32 bit systems). I guess everyone has been developing newt on 64 bit systems (OSX or Linux x86_64). On Fri, Dec 23, 2016, at 06:50 PM, Alan Graves wrote: > Hi Sterling, > > BTW Thanks for

Initial MMC/SD card support

d of block transfers. Would also be better to do interrupt driven block reads/writes. The next step now is to make hal_flash, mmc (and the future spi flash) devices interchangeable for the FS's. Cheers, Fabio Utzig

Re: Newbie & running into an error during setup

cies like go and gcc-arm-embedded. Easily done with homebrew: $ brew install go $ brew cask install gcc-arm-embedded Cheers, Fabio Utzig

Fwd: Re: License doubts regarding addition of external FAT library to Apache Mynewt

y to Apache Mynewt Date: Fri, 18 Nov 2016 08:36:55 -0800 That's a 1-clause BSD license; looks fine to me. It's not explicitly listed on resolved.html because 1-clause is not very common (compared to 2-clause and 3-clause versions of BSD). Hen On Fri, Nov 18, 2016 at 4:45 AM, Fabio Utzig <

Initial FAT support

forward: 1) Write a MMC driver to access SD-Cards. I think this would rely only on having a hal_spi driver. 2) Add support for USB and USB disks. This is much harder but will have to be done eventually anyway. So, what's the suggestion? Fabio Utzig

Initial FAT support

forward: 1) Write a MMC driver to access SD-Cards. I think this would rely only on having a hal_spi driver. 2) Add support for USB and USB disks. This is much harder but will have to be done eventually anyway. So, what's the suggestion? Fabio Utzig