You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mynewt.apache.org by Nges B <ng...@gmail.com> on 2016/03/04 02:04:56 UTC

Build Blinky

Have successfully run all the commands needed for the blinky project.
Now wen I run  $ newt target build blinky
i get the error "Error: No configuration section exists"
Please can somebody help me and Identify where I went wrong or I need
to to to get the Configuration section exists?
Thanks in advance

Re: Build Blinky

Posted by marko kiiskila <ma...@runtime.io>.
Yes, that’s good.

Now issue the other commands Chris sent out, where blinky variables
are set, and then inspect the output of ‘newt target show’ again.
You should be able to build blinky target then.

> On Mar 3, 2016, at 6:06 PM, Nges B <ng...@gmail.com> wrote:
> 
> $ newt target build sim_test
> Building target sim_test (project = test)
> Building project test
> Successfully run!
> 
> $ newt target create blinky
> Creating target blinky
> Target blinky successfully created!
> 
> $ newt target show
> bin2img
> 	arch=sim
> 	bsp=hw/bsp/native
> 	compiler=sim
> 	compiler_def=debug
> 	name=bin2img
> 	project=bin2img
> blinky
> 	arch=sim
> 	name=blinky
> sim_test
> 	arch=sim
> 	bsp=hw/bsp/native
> 	compiler=sim
> 	compiler_def=debug
> 	name=sim_test
> 	project=test
> 
> 
> I think this output is the expected.
> 
> On 3/4/16, Christopher Collins <ch...@runtime.io> wrote:
>> On Fri, Mar 04, 2016 at 02:44:52AM +0100, Nges B wrote:
>>> Is that ok or I should put the output in a file??
>>> 
>>> On 3/4/16, Nges B <ng...@gmail.com> wrote:
>>>> $   newt target show
>>>> bin2img
>>>> 	arch=sim
>>>> 	bsp=hw/bsp/native
>>>> 	compiler=sim
>>>> 	compiler_def=debug
>>>> 	name=bin2img
>>>> 	project=bin2img
>>>> sim_test
>>>> 	arch=sim
>>>> 	bsp=hw/bsp/native
>>>> 	compiler=sim
>>>> 	compiler_def=debug
>>>> 	name=sim_test
>>>> 	project=test
>> 
>> Hi Nges,
>> 
>> That is fine, no need for a file.
>> 
>> Newt doesn't see the blinky target.  I am sorry to keep asking, but are
>> you sure you created it?  The "getting started" mynewt page instructs
>> the user to creates two targets:
>>    * sim_test
>>    * blinky
>> 
>> It looks like sim_test was created successfully.
>> 
>> Just to humor me, could you please try executing the below set of
>> commands?
>> 
>> $ newt target create blinky
>> $ newt target set blinky arch=cortex_m4
>> $ newt target set blinky compiler=arm-none-eabi-m4
>> $ newt target set blinky project=blinky
>> $ newt target set blinky compiler_def=debug
>> $ newt target set blinky bsp=hw/bsp/olimex_stm32-e407_devboard
>> 
>> Thanks,
>> Chris
>> 
>>>> 
>>>> 
>>>> $   newt -v -lDEBUG target build blinky
>>>> 2016/03/04 02:42:45 [DEBUG] Searching for repository, starting in
>>>> directory /home/ngesb/dev/larva/project/blinky
>>>> 2016/03/04 02:42:45 [DEBUG] Searching for repo file at
>>>> /home/ngesb/dev/larva/project/blinky/app.yml
>>>> 2016/03/04 02:42:45 [DEBUG] Searching for repo file at
>>>> /home/ngesb/dev/larva/project/app.yml
>>>> 2016/03/04 02:42:45 [DEBUG] Searching for repo file at
>>>> /home/ngesb/dev/larva/app.yml
>>>> 2016/03/04 02:42:45 [DEBUG] Found repo file at
>>>> /home/ngesb/dev/larva/app.yml!
>>>> 2016/03/04 02:42:45 [DEBUG] Repo file found, directory
>>>> /home/ngesb/dev/larva/app.yml, loading configuration...
>>>> 2016/03/04 02:42:45 [DEBUG] Configuration loaded!  Initializing .app
>>>> database
>>>> 2016/03/04 02:42:45 [DEBUG] Populating Repo configuration from
>>>> /home/ngesb/dev/larva/.app//app.db
>>>> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key arch to
>>>> val
>>>> sim
>>>> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key name to
>>>> val bin2img
>>>> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key bsp to
>>>> val hw/bsp/native
>>>> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key compiler
>>>> to val sim
>>>> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key project
>>>> to val bin2img
>>>> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key
>>>> compiler_def to val debug
>>>> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key name to
>>>> val sim_test
>>>> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key arch to
>>>> val
>>>> sim
>>>> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key project
>>>> to val test
>>>> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key
>>>> compiler_def to val debug
>>>> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key bsp to
>>>> val hw/bsp/native
>>>> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key
>>>> compiler to val sim
>>>> 2016/03/04 02:42:45 [DEBUG] Database initialized.
>>>> Importing all targets from /home/ngesb/dev/larva/autotargets  set
>>>> default
>>>> ident
>>>> 2016/03/04 02:42:45 [DEBUG] Storing value sim into key _target_bin2img
>>>> for section compiler
>>>> 2016/03/04 02:42:45 [DEBUG] Key compiler, sect _target_bin2img
>>>> successfully updated to sim
>>>> 2016/03/04 02:42:45 [DEBUG] Storing value bin2img into key
>>>> _target_bin2img for section project
>>>> 2016/03/04 02:42:45 [DEBUG] Key project, sect _target_bin2img
>>>> successfully updated to bin2img
>>>> 2016/03/04 02:42:45 [DEBUG] Storing value debug into key
>>>> _target_bin2img for section compiler_def
>>>> 2016/03/04 02:42:45 [DEBUG] Key compiler_def, sect _target_bin2img
>>>> successfully updated to debug
>>>> 2016/03/04 02:42:45 [DEBUG] Storing value sim into key _target_bin2img
>>>> for section arch
>>>> 2016/03/04 02:42:45 [DEBUG] Key arch, sect _target_bin2img
>>>> successfully updated to sim
>>>> 2016/03/04 02:42:45 [DEBUG] Storing value bin2img into key
>>>> _target_bin2img for section name
>>>> 2016/03/04 02:42:45 [DEBUG] Key name, sect _target_bin2img
>>>> successfully updated to bin2img
>>>> 2016/03/04 02:42:45 [DEBUG] Storing value hw/bsp/native into key
>>>> _target_bin2img for section bsp
>>>> 2016/03/04 02:42:45 [DEBUG] Key bsp, sect _target_bin2img successfully
>>>> updated to hw/bsp/native
>>>> 2016/03/04 02:42:45 [DEBUG] goroutine 1 [running]:
>>>> git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli.NewNewtError(0x8f2a20,
>>>> 0x1f, 0xc820245bf8)
>>>> 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli/util.go:67
>>>> +0xe5
>>>> git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli.(*Repo).GetConfigSect(0xc820079a80,
>>>> 0xc820245bf8, 0xe, 0x7ffd57d5c330, 0x0, 0x0)
>>>> 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli/repo.go:251
>>>> +0x8a
>>>> git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli.LoadTarget(0xc820079a80,
>>>> 0x7ffd57d5c330, 0x6, 0xc82002a280, 0x0, 0x0)
>>>> 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli/target.go:136
>>>> +0xf3
>>>> main.targetBuildCmd(0xc8200d9400, 0xc8201d68d0, 0x1, 0x3)
>>>> 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/newt.go:206
>>>> +0xca
>>>> github.com/spf13/cobra.(*Command).execute(0xc8200d9400, 0xc820214540,
>>>> 0x3, 0x4, 0x0, 0x0)
>>>> 	/home/ccollins/dev/go/src/github.com/spf13/cobra/command.go:569 +0x85a
>>>> github.com/spf13/cobra.(*Command).ExecuteC(0xc8200d8200, 0xc8200d9400,
>>>> 0x0,
>>>> 0x0)
>>>> 	/home/ccollins/dev/go/src/github.com/spf13/cobra/command.go:656 +0x55c
>>>> github.com/spf13/cobra.(*Command).Execute(0xc8200d8200, 0x0, 0x0)
>>>> 	/home/ccollins/dev/go/src/github.com/spf13/cobra/command.go:615 +0x2d
>>>> main.main()
>>>> 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/newt.go:1454
>>>> +0x25
>>>> 
>>>> goroutine 17 [syscall, locked to thread]:
>>>> runtime.goexit()
>>>> 	/usr/local/go/src/runtime/asm_amd64.s:1998 +0x1
>>>> 
>>>> goroutine 5 [syscall]:
>>>> os/signal.signal_recv(0x0)
>>>> 	/usr/local/go/src/runtime/sigqueue.go:116 +0x132
>>>> os/signal.loop()
>>>> 	/usr/local/go/src/os/signal/signal_unix.go:22 +0x18
>>>> created by os/signal.init.1
>>>> 	/usr/local/go/src/os/signal/signal_unix.go:28 +0x37
>>>> 
>>>> goroutine 6 [chan receive]:
>>>> database/sql.(*DB).connectionOpener(0xc820189080)
>>>> 	/usr/local/go/src/database/sql/sql.go:727 +0x45
>>>> created by database/sql.Open
>>>> 	/usr/local/go/src/database/sql/sql.go:493 +0x33f
>>>> 
>>>> Error: No configuration section exists
>>>> 
>>>> 
>>>> 
>>>> On 3/4/16, Christopher Collins <ch...@runtime.io> wrote:
>>>>> Hi Nges,
>>>>> 
>>>>> Can you please run the following commands and send the output?
>>>>> 
>>>>>    newt target show
>>>>>    newt -v -lDEBUG target build blinky
>>>>> 
>>>>> It is probably going to generate a lot of text.
>>>>> 
>>>>> Thanks,
>>>>> Chris
>>>>> 
>>>>> On Fri, Mar 04, 2016 at 02:23:33AM +0100, Nges B wrote:
>>>>>> Yes I have done all the above exactly as you have given and have the
>>>>>> execpected results.
>>>>>> 
>>>>>> Then from my reading here
>>>>>> http://mynewt.apache.org/os/get_started/project1/#build-test-code-on-simulator
>>>>>> 
>>>>>> it says I should run the following
>>>>>> 
>>>>>> $ cd ~/dev/larva/hw/bsp/olimex_stm32-e407_devboard
>>>>>> $ diff olimex_stm32-e407_devboard.ld run_from_sram.ld
>>>>>> $ cp run_from_sram.ld olimex_stm32-e407_devboard.ld
>>>>>> $ cd ~/dev/larva/project/blinky/
>>>>>> 
>>>>>> all the above commands give me expected output.
>>>>>> now when I run
>>>>>> 
>>>>>> $ newt target build blinky
>>>>>> 
>>>>>> I get the following error
>>>>>> 
>>>>>> Error: No configuration section exists
>>>>>> 
>>>>>> so I do not understand what the error is.
>>>>>> 
>>>>>> 
>>>>>> On 3/4/16, Christopher Collins <ch...@runtime.io> wrote:
>>>>>>> Hi Nges,
>>>>>>> 
>>>>>>> Did you create the 'blinky' target using newt?  This process is a
>>>>>>> bit
>>>>>>> of
>>>>>>> a hassle at the moment, but you only have to do it once.
>>>>>>> 
>>>>>>> The following set of commands should do the trick:
>>>>>>> 
>>>>>>>    $ newt target create blinky
>>>>>>>    $ newt target set blinky arch=cortex_m4
>>>>>>>    $ newt target set blinky compiler=arm-none-eabi-m4
>>>>>>>    $ newt target set blinky project=blinky
>>>>>>>    $ newt target set blinky compiler_def=debug
>>>>>>>    $ newt target set blinky bsp=hw/bsp/olimex_stm32-e407_devboard
>>>>>>> 
>>>>>>> 
>>>>>>> From http://mynewt.apache.org/os/get_started/project1/ :
>>>>>>> 
>>>>>>>    $ newt target create blinky
>>>>>>>    Creating target blinky
>>>>>>>    Target blinky sucessfully created!
>>>>>>>    $ newt target set blinky arch=cortex_m4
>>>>>>>    Target blinky successfully set arch to arm
>>>>>>>    $ newt target set blinky compiler=arm-none-eabi-m4
>>>>>>>    Target blinky successfully set compiler to arm-none-eabi-m4
>>>>>>>    $ newt target set blinky project=blinky
>>>>>>>    Target blinky successfully set project to blinky
>>>>>>>    $ newt target set blinky compiler_def=debug
>>>>>>>    Target blinky successfully set compiler_def to debug
>>>>>>>    $ newt target set blinky bsp=hw/bsp/olimex_stm32-e407_devboard
>>>>>>>    Target blinky successfully set bsp to
>>>>>>> hw/bsp/olimex_stm32-e407_devboard
>>>>>>>    $ newt target show blinky
>>>>>>>    blinky
>>>>>>>        arch=cortex_m4
>>>>>>>        bsp=hw/bsp/olimex_stm32-e407_devboard
>>>>>>>        compiler=arm-none-eabi-m4
>>>>>>>        compiler_def=debug
>>>>>>>        name=blinky
>>>>>>>        project=blinky
>>>>>>> 
>>>>>>> Chris
>>>>>>> 
>>>>>>> On Fri, Mar 04, 2016 at 02:04:56AM +0100, Nges B wrote:
>>>>>>>> Have successfully run all the commands needed for the blinky
>>>>>>>> project.
>>>>>>>> Now wen I run  $ newt target build blinky
>>>>>>>> i get the error "Error: No configuration section exists"
>>>>>>>> Please can somebody help me and Identify where I went wrong or I
>>>>>>>> need
>>>>>>>> to to to get the Configuration section exists?
>>>>>>>> Thanks in advance
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> --
>>>>>> "it is good to dream and work for the dreams than not to dream"
>>>>> 
>>>> 
>>>> 
>>>> --
>>>> "it is good to dream and work for the dreams than not to dream"
>>>> 
>>> 
>>> 
>>> --
>>> "it is good to dream and work for the dreams than not to dream"
>> 
> 
> 
> -- 
> "it is good to dream and work for the dreams than not to dream"


Re: Build Blinky

Posted by Nges B <ng...@gmail.com>.
well UInderstood

On 3/4/16, Christopher Collins <ch...@runtime.io> wrote:
> On Fri, Mar 04, 2016 at 03:28:30AM +0100, Nges B wrote:
>> $ newt target create blinky command can not create a new project
>> because it already exist.
>
> Yes, you are right about that.  However, that should not be a problem.
> There are two steps in setting up a newt target:
>
>     1. Create the target (newt target create)
>     2. Configure the target (newt target set)
>
> So now you just need to perform step 2.  You can configure a target any
> time after it has been created.  For example:
>
>     $ newt target create blinky
>     Creating target blinky
>     Target blinky successfully created!
>     $ newt target show blinky
>     blinky
>             arch=sim
>             name=blinky
>
>     $ newt target set blinky arch=cortex_m4
>     Target blinky successfully set arch to cortex_m4
>     $ newt target show blinky
>     blinky
>             arch=cortex_m4
>             name=blinky
>
>     $ newt target set blinky compiler=arm-none-eabi-m4
>     Target blinky successfully set compiler to arm-none-eabi-m4
>     $ newt target show blinky
>     blinky
>             arch=cortex_m4
>             compiler=arm-none-eabi-m4
>             name=blinky
>
>     $ newt target set blinky project=blinky
>     Target blinky successfully set project to blinky
>     $ newt target show blinky
>     blinky
>             arch=cortex_m4
>             compiler=arm-none-eabi-m4
>             name=blinky
>             project=blinky
>
>     $ newt target set blinky bsp=hw/bsp/olimex_stm32-e407_devboard
>     Target blinky successfully set bsp to hw/bsp/olimex_stm32-e407_devboard
>     $ newt target show blinky
>     blinky
>             arch=cortex_m4
>             bsp=hw/bsp/olimex_stm32-e407_devboard
>             compiler=arm-none-eabi-m4
>             name=blinky
>             project=blinky
>
>     $ newt target set blinky compiler_def=debug
>     Target blinky successfully set compiler_def to debug
>     $ newt target show blinky
>     blinky
>             arch=cortex_m4
>             bsp=hw/bsp/olimex_stm32-e407_devboard
>             compiler=arm-none-eabi-m4
>             compiler_def=debug
>             name=blinky
>             project=blinky
>
> Chris
>


-- 
"it is good to dream and work for the dreams than not to dream"

Re: Build Blinky

Posted by Christopher Collins <ch...@runtime.io>.
On Fri, Mar 04, 2016 at 03:28:30AM +0100, Nges B wrote:
> $ newt target create blinky command can not create a new project
> because it already exist.

Yes, you are right about that.  However, that should not be a problem.
There are two steps in setting up a newt target:

    1. Create the target (newt target create)
    2. Configure the target (newt target set)

So now you just need to perform step 2.  You can configure a target any
time after it has been created.  For example:

    $ newt target create blinky
    Creating target blinky
    Target blinky successfully created!
    $ newt target show blinky
    blinky
            arch=sim
            name=blinky

    $ newt target set blinky arch=cortex_m4
    Target blinky successfully set arch to cortex_m4
    $ newt target show blinky
    blinky
            arch=cortex_m4
            name=blinky

    $ newt target set blinky compiler=arm-none-eabi-m4
    Target blinky successfully set compiler to arm-none-eabi-m4
    $ newt target show blinky
    blinky
            arch=cortex_m4
            compiler=arm-none-eabi-m4
            name=blinky

    $ newt target set blinky project=blinky
    Target blinky successfully set project to blinky
    $ newt target show blinky
    blinky
            arch=cortex_m4
            compiler=arm-none-eabi-m4
            name=blinky
            project=blinky

    $ newt target set blinky bsp=hw/bsp/olimex_stm32-e407_devboard
    Target blinky successfully set bsp to hw/bsp/olimex_stm32-e407_devboard
    $ newt target show blinky
    blinky
            arch=cortex_m4
            bsp=hw/bsp/olimex_stm32-e407_devboard
            compiler=arm-none-eabi-m4
            name=blinky
            project=blinky

    $ newt target set blinky compiler_def=debug
    Target blinky successfully set compiler_def to debug
    $ newt target show blinky
    blinky
            arch=cortex_m4
            bsp=hw/bsp/olimex_stm32-e407_devboard
            compiler=arm-none-eabi-m4
            compiler_def=debug
            name=blinky
            project=blinky

Chris

Re: Build Blinky

Posted by Nges B <ng...@gmail.com>.
Thanks everyone . +1

On 3/4/16, Nges B <ng...@gmail.com> wrote:
> remember the $ newt target create blinky command can not create a new
> project because it already exist.
>
> On 3/4/16, Nges B <ng...@gmail.com> wrote:
>> after running the commands I should continue with the normal commands
>> to build the image??
>>
>>  $ cd ~/dev/larva/hw/bsp/olimex_stm32-e407_devboard
>>         $ diff olimex_stm32-e407_devboard.ld run_from_sram.ld
>> cp run_from_sram.ld olimex_stm32-e407_devboard.ld
>>         $ cd ~/dev/larva/project/blinky/
>>         $ newt target build blinky
>>
>> right??
>>
>> On 3/4/16, Christopher Collins <ch...@runtime.io> wrote:
>>> On Fri, Mar 04, 2016 at 03:06:13AM +0100, Nges B wrote:
>>>> $ newt target build sim_test
>>>> Building target sim_test (project = test)
>>>> Building project test
>>>> Successfully run!
>>>>
>>>> $ newt target create blinky
>>>> Creating target blinky
>>>> Target blinky successfully created!
>>>>
>>>> $ newt target show
>>>> bin2img
>>>> 	arch=sim
>>>> 	bsp=hw/bsp/native
>>>> 	compiler=sim
>>>> 	compiler_def=debug
>>>> 	name=bin2img
>>>> 	project=bin2img
>>>> blinky
>>>> 	arch=sim
>>>> 	name=blinky
>>>> sim_test
>>>> 	arch=sim
>>>> 	bsp=hw/bsp/native
>>>> 	compiler=sim
>>>> 	compiler_def=debug
>>>> 	name=sim_test
>>>> 	project=test
>>>>
>>>>
>>>> I think this output is the expected.
>>>
>>> Great!  Don't forget to set the arch, bsp, compiler, compiler_def, and
>>> project variables.
>>>
>>> Please feel free to send your questions to this list if you encounter
>>> any more issues.
>>>
>>> Chris
>>>
>>
>>
>> --
>> "it is good to dream and work for the dreams than not to dream"
>>
>
>
> --
> "it is good to dream and work for the dreams than not to dream"
>


-- 
"it is good to dream and work for the dreams than not to dream"

Re: Build Blinky

Posted by Nges B <ng...@gmail.com>.
remember the $ newt target create blinky command can not create a new
project because it already exist.

On 3/4/16, Nges B <ng...@gmail.com> wrote:
> after running the commands I should continue with the normal commands
> to build the image??
>
>  $ cd ~/dev/larva/hw/bsp/olimex_stm32-e407_devboard
>         $ diff olimex_stm32-e407_devboard.ld run_from_sram.ld
> cp run_from_sram.ld olimex_stm32-e407_devboard.ld
>         $ cd ~/dev/larva/project/blinky/
>         $ newt target build blinky
>
> right??
>
> On 3/4/16, Christopher Collins <ch...@runtime.io> wrote:
>> On Fri, Mar 04, 2016 at 03:06:13AM +0100, Nges B wrote:
>>> $ newt target build sim_test
>>> Building target sim_test (project = test)
>>> Building project test
>>> Successfully run!
>>>
>>> $ newt target create blinky
>>> Creating target blinky
>>> Target blinky successfully created!
>>>
>>> $ newt target show
>>> bin2img
>>> 	arch=sim
>>> 	bsp=hw/bsp/native
>>> 	compiler=sim
>>> 	compiler_def=debug
>>> 	name=bin2img
>>> 	project=bin2img
>>> blinky
>>> 	arch=sim
>>> 	name=blinky
>>> sim_test
>>> 	arch=sim
>>> 	bsp=hw/bsp/native
>>> 	compiler=sim
>>> 	compiler_def=debug
>>> 	name=sim_test
>>> 	project=test
>>>
>>>
>>> I think this output is the expected.
>>
>> Great!  Don't forget to set the arch, bsp, compiler, compiler_def, and
>> project variables.
>>
>> Please feel free to send your questions to this list if you encounter
>> any more issues.
>>
>> Chris
>>
>
>
> --
> "it is good to dream and work for the dreams than not to dream"
>


-- 
"it is good to dream and work for the dreams than not to dream"

Re: Build Blinky

Posted by Nges B <ng...@gmail.com>.
after running the commands I should continue with the normal commands
to build the image??

 $ cd ~/dev/larva/hw/bsp/olimex_stm32-e407_devboard
        $ diff olimex_stm32-e407_devboard.ld run_from_sram.ld
cp run_from_sram.ld olimex_stm32-e407_devboard.ld
        $ cd ~/dev/larva/project/blinky/
        $ newt target build blinky

right??

On 3/4/16, Christopher Collins <ch...@runtime.io> wrote:
> On Fri, Mar 04, 2016 at 03:06:13AM +0100, Nges B wrote:
>> $ newt target build sim_test
>> Building target sim_test (project = test)
>> Building project test
>> Successfully run!
>>
>> $ newt target create blinky
>> Creating target blinky
>> Target blinky successfully created!
>>
>> $ newt target show
>> bin2img
>> 	arch=sim
>> 	bsp=hw/bsp/native
>> 	compiler=sim
>> 	compiler_def=debug
>> 	name=bin2img
>> 	project=bin2img
>> blinky
>> 	arch=sim
>> 	name=blinky
>> sim_test
>> 	arch=sim
>> 	bsp=hw/bsp/native
>> 	compiler=sim
>> 	compiler_def=debug
>> 	name=sim_test
>> 	project=test
>>
>>
>> I think this output is the expected.
>
> Great!  Don't forget to set the arch, bsp, compiler, compiler_def, and
> project variables.
>
> Please feel free to send your questions to this list if you encounter
> any more issues.
>
> Chris
>


-- 
"it is good to dream and work for the dreams than not to dream"

Re: Build Blinky

Posted by Christopher Collins <ch...@runtime.io>.
On Fri, Mar 04, 2016 at 03:06:13AM +0100, Nges B wrote:
> $ newt target build sim_test
> Building target sim_test (project = test)
> Building project test
> Successfully run!
> 
> $ newt target create blinky
> Creating target blinky
> Target blinky successfully created!
> 
> $ newt target show
> bin2img
> 	arch=sim
> 	bsp=hw/bsp/native
> 	compiler=sim
> 	compiler_def=debug
> 	name=bin2img
> 	project=bin2img
> blinky
> 	arch=sim
> 	name=blinky
> sim_test
> 	arch=sim
> 	bsp=hw/bsp/native
> 	compiler=sim
> 	compiler_def=debug
> 	name=sim_test
> 	project=test
> 
> 
> I think this output is the expected.

Great!  Don't forget to set the arch, bsp, compiler, compiler_def, and
project variables.

Please feel free to send your questions to this list if you encounter
any more issues.

Chris

Re: Build Blinky

Posted by Nges B <ng...@gmail.com>.
$ newt target build sim_test
Building target sim_test (project = test)
Building project test
Successfully run!

$ newt target create blinky
Creating target blinky
Target blinky successfully created!

$ newt target show
bin2img
	arch=sim
	bsp=hw/bsp/native
	compiler=sim
	compiler_def=debug
	name=bin2img
	project=bin2img
blinky
	arch=sim
	name=blinky
sim_test
	arch=sim
	bsp=hw/bsp/native
	compiler=sim
	compiler_def=debug
	name=sim_test
	project=test


I think this output is the expected.

On 3/4/16, Christopher Collins <ch...@runtime.io> wrote:
> On Fri, Mar 04, 2016 at 02:44:52AM +0100, Nges B wrote:
>> Is that ok or I should put the output in a file??
>>
>> On 3/4/16, Nges B <ng...@gmail.com> wrote:
>> > $   newt target show
>> > bin2img
>> > 	arch=sim
>> > 	bsp=hw/bsp/native
>> > 	compiler=sim
>> > 	compiler_def=debug
>> > 	name=bin2img
>> > 	project=bin2img
>> > sim_test
>> > 	arch=sim
>> > 	bsp=hw/bsp/native
>> > 	compiler=sim
>> > 	compiler_def=debug
>> > 	name=sim_test
>> > 	project=test
>
> Hi Nges,
>
> That is fine, no need for a file.
>
> Newt doesn't see the blinky target.  I am sorry to keep asking, but are
> you sure you created it?  The "getting started" mynewt page instructs
> the user to creates two targets:
>     * sim_test
>     * blinky
>
> It looks like sim_test was created successfully.
>
> Just to humor me, could you please try executing the below set of
> commands?
>
> $ newt target create blinky
> $ newt target set blinky arch=cortex_m4
> $ newt target set blinky compiler=arm-none-eabi-m4
> $ newt target set blinky project=blinky
> $ newt target set blinky compiler_def=debug
> $ newt target set blinky bsp=hw/bsp/olimex_stm32-e407_devboard
>
> Thanks,
> Chris
>
>> >
>> >
>> > $   newt -v -lDEBUG target build blinky
>> > 2016/03/04 02:42:45 [DEBUG] Searching for repository, starting in
>> > directory /home/ngesb/dev/larva/project/blinky
>> > 2016/03/04 02:42:45 [DEBUG] Searching for repo file at
>> > /home/ngesb/dev/larva/project/blinky/app.yml
>> > 2016/03/04 02:42:45 [DEBUG] Searching for repo file at
>> > /home/ngesb/dev/larva/project/app.yml
>> > 2016/03/04 02:42:45 [DEBUG] Searching for repo file at
>> > /home/ngesb/dev/larva/app.yml
>> > 2016/03/04 02:42:45 [DEBUG] Found repo file at
>> > /home/ngesb/dev/larva/app.yml!
>> > 2016/03/04 02:42:45 [DEBUG] Repo file found, directory
>> > /home/ngesb/dev/larva/app.yml, loading configuration...
>> > 2016/03/04 02:42:45 [DEBUG] Configuration loaded!  Initializing .app
>> > database
>> > 2016/03/04 02:42:45 [DEBUG] Populating Repo configuration from
>> > /home/ngesb/dev/larva/.app//app.db
>> > 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key arch to
>> > val
>> > sim
>> > 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key name to
>> > val bin2img
>> > 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key bsp to
>> > val hw/bsp/native
>> > 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key compiler
>> > to val sim
>> > 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key project
>> > to val bin2img
>> > 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key
>> > compiler_def to val debug
>> > 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key name to
>> > val sim_test
>> > 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key arch to
>> > val
>> > sim
>> > 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key project
>> > to val test
>> > 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key
>> > compiler_def to val debug
>> > 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key bsp to
>> > val hw/bsp/native
>> > 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key
>> > compiler to val sim
>> > 2016/03/04 02:42:45 [DEBUG] Database initialized.
>> > Importing all targets from /home/ngesb/dev/larva/autotargets  set
>> > default
>> > ident
>> > 2016/03/04 02:42:45 [DEBUG] Storing value sim into key _target_bin2img
>> > for section compiler
>> > 2016/03/04 02:42:45 [DEBUG] Key compiler, sect _target_bin2img
>> > successfully updated to sim
>> > 2016/03/04 02:42:45 [DEBUG] Storing value bin2img into key
>> > _target_bin2img for section project
>> > 2016/03/04 02:42:45 [DEBUG] Key project, sect _target_bin2img
>> > successfully updated to bin2img
>> > 2016/03/04 02:42:45 [DEBUG] Storing value debug into key
>> > _target_bin2img for section compiler_def
>> > 2016/03/04 02:42:45 [DEBUG] Key compiler_def, sect _target_bin2img
>> > successfully updated to debug
>> > 2016/03/04 02:42:45 [DEBUG] Storing value sim into key _target_bin2img
>> > for section arch
>> > 2016/03/04 02:42:45 [DEBUG] Key arch, sect _target_bin2img
>> > successfully updated to sim
>> > 2016/03/04 02:42:45 [DEBUG] Storing value bin2img into key
>> > _target_bin2img for section name
>> > 2016/03/04 02:42:45 [DEBUG] Key name, sect _target_bin2img
>> > successfully updated to bin2img
>> > 2016/03/04 02:42:45 [DEBUG] Storing value hw/bsp/native into key
>> > _target_bin2img for section bsp
>> > 2016/03/04 02:42:45 [DEBUG] Key bsp, sect _target_bin2img successfully
>> > updated to hw/bsp/native
>> > 2016/03/04 02:42:45 [DEBUG] goroutine 1 [running]:
>> > git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli.NewNewtError(0x8f2a20,
>> > 0x1f, 0xc820245bf8)
>> > 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli/util.go:67
>> > +0xe5
>> > git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli.(*Repo).GetConfigSect(0xc820079a80,
>> > 0xc820245bf8, 0xe, 0x7ffd57d5c330, 0x0, 0x0)
>> > 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli/repo.go:251
>> > +0x8a
>> > git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli.LoadTarget(0xc820079a80,
>> > 0x7ffd57d5c330, 0x6, 0xc82002a280, 0x0, 0x0)
>> > 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli/target.go:136
>> > +0xf3
>> > main.targetBuildCmd(0xc8200d9400, 0xc8201d68d0, 0x1, 0x3)
>> > 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/newt.go:206
>> > +0xca
>> > github.com/spf13/cobra.(*Command).execute(0xc8200d9400, 0xc820214540,
>> > 0x3, 0x4, 0x0, 0x0)
>> > 	/home/ccollins/dev/go/src/github.com/spf13/cobra/command.go:569 +0x85a
>> > github.com/spf13/cobra.(*Command).ExecuteC(0xc8200d8200, 0xc8200d9400,
>> > 0x0,
>> > 0x0)
>> > 	/home/ccollins/dev/go/src/github.com/spf13/cobra/command.go:656 +0x55c
>> > github.com/spf13/cobra.(*Command).Execute(0xc8200d8200, 0x0, 0x0)
>> > 	/home/ccollins/dev/go/src/github.com/spf13/cobra/command.go:615 +0x2d
>> > main.main()
>> > 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/newt.go:1454
>> > +0x25
>> >
>> > goroutine 17 [syscall, locked to thread]:
>> > runtime.goexit()
>> > 	/usr/local/go/src/runtime/asm_amd64.s:1998 +0x1
>> >
>> > goroutine 5 [syscall]:
>> > os/signal.signal_recv(0x0)
>> > 	/usr/local/go/src/runtime/sigqueue.go:116 +0x132
>> > os/signal.loop()
>> > 	/usr/local/go/src/os/signal/signal_unix.go:22 +0x18
>> > created by os/signal.init.1
>> > 	/usr/local/go/src/os/signal/signal_unix.go:28 +0x37
>> >
>> > goroutine 6 [chan receive]:
>> > database/sql.(*DB).connectionOpener(0xc820189080)
>> > 	/usr/local/go/src/database/sql/sql.go:727 +0x45
>> > created by database/sql.Open
>> > 	/usr/local/go/src/database/sql/sql.go:493 +0x33f
>> >
>> > Error: No configuration section exists
>> >
>> >
>> >
>> > On 3/4/16, Christopher Collins <ch...@runtime.io> wrote:
>> >> Hi Nges,
>> >>
>> >> Can you please run the following commands and send the output?
>> >>
>> >>     newt target show
>> >>     newt -v -lDEBUG target build blinky
>> >>
>> >> It is probably going to generate a lot of text.
>> >>
>> >> Thanks,
>> >> Chris
>> >>
>> >> On Fri, Mar 04, 2016 at 02:23:33AM +0100, Nges B wrote:
>> >>> Yes I have done all the above exactly as you have given and have the
>> >>> execpected results.
>> >>>
>> >>> Then from my reading here
>> >>> http://mynewt.apache.org/os/get_started/project1/#build-test-code-on-simulator
>> >>>
>> >>> it says I should run the following
>> >>>
>> >>> $ cd ~/dev/larva/hw/bsp/olimex_stm32-e407_devboard
>> >>> $ diff olimex_stm32-e407_devboard.ld run_from_sram.ld
>> >>> $ cp run_from_sram.ld olimex_stm32-e407_devboard.ld
>> >>> $ cd ~/dev/larva/project/blinky/
>> >>>
>> >>> all the above commands give me expected output.
>> >>> now when I run
>> >>>
>> >>> $ newt target build blinky
>> >>>
>> >>> I get the following error
>> >>>
>> >>> Error: No configuration section exists
>> >>>
>> >>> so I do not understand what the error is.
>> >>>
>> >>>
>> >>> On 3/4/16, Christopher Collins <ch...@runtime.io> wrote:
>> >>> > Hi Nges,
>> >>> >
>> >>> > Did you create the 'blinky' target using newt?  This process is a
>> >>> > bit
>> >>> > of
>> >>> > a hassle at the moment, but you only have to do it once.
>> >>> >
>> >>> > The following set of commands should do the trick:
>> >>> >
>> >>> >     $ newt target create blinky
>> >>> >     $ newt target set blinky arch=cortex_m4
>> >>> >     $ newt target set blinky compiler=arm-none-eabi-m4
>> >>> >     $ newt target set blinky project=blinky
>> >>> >     $ newt target set blinky compiler_def=debug
>> >>> >     $ newt target set blinky bsp=hw/bsp/olimex_stm32-e407_devboard
>> >>> >
>> >>> >
>> >>> > From http://mynewt.apache.org/os/get_started/project1/ :
>> >>> >
>> >>> >     $ newt target create blinky
>> >>> >     Creating target blinky
>> >>> >     Target blinky sucessfully created!
>> >>> >     $ newt target set blinky arch=cortex_m4
>> >>> >     Target blinky successfully set arch to arm
>> >>> >     $ newt target set blinky compiler=arm-none-eabi-m4
>> >>> >     Target blinky successfully set compiler to arm-none-eabi-m4
>> >>> >     $ newt target set blinky project=blinky
>> >>> >     Target blinky successfully set project to blinky
>> >>> >     $ newt target set blinky compiler_def=debug
>> >>> >     Target blinky successfully set compiler_def to debug
>> >>> >     $ newt target set blinky bsp=hw/bsp/olimex_stm32-e407_devboard
>> >>> >     Target blinky successfully set bsp to
>> >>> > hw/bsp/olimex_stm32-e407_devboard
>> >>> >     $ newt target show blinky
>> >>> >     blinky
>> >>> >         arch=cortex_m4
>> >>> >         bsp=hw/bsp/olimex_stm32-e407_devboard
>> >>> >         compiler=arm-none-eabi-m4
>> >>> >         compiler_def=debug
>> >>> >         name=blinky
>> >>> >         project=blinky
>> >>> >
>> >>> > Chris
>> >>> >
>> >>> > On Fri, Mar 04, 2016 at 02:04:56AM +0100, Nges B wrote:
>> >>> >> Have successfully run all the commands needed for the blinky
>> >>> >> project.
>> >>> >> Now wen I run  $ newt target build blinky
>> >>> >> i get the error "Error: No configuration section exists"
>> >>> >> Please can somebody help me and Identify where I went wrong or I
>> >>> >> need
>> >>> >> to to to get the Configuration section exists?
>> >>> >> Thanks in advance
>> >>> >
>> >>>
>> >>>
>> >>> --
>> >>> "it is good to dream and work for the dreams than not to dream"
>> >>
>> >
>> >
>> > --
>> > "it is good to dream and work for the dreams than not to dream"
>> >
>>
>>
>> --
>> "it is good to dream and work for the dreams than not to dream"
>


-- 
"it is good to dream and work for the dreams than not to dream"

Re: Build Blinky

Posted by Christopher Collins <ch...@runtime.io>.
On Fri, Mar 04, 2016 at 02:44:52AM +0100, Nges B wrote:
> Is that ok or I should put the output in a file??
> 
> On 3/4/16, Nges B <ng...@gmail.com> wrote:
> > $   newt target show
> > bin2img
> > 	arch=sim
> > 	bsp=hw/bsp/native
> > 	compiler=sim
> > 	compiler_def=debug
> > 	name=bin2img
> > 	project=bin2img
> > sim_test
> > 	arch=sim
> > 	bsp=hw/bsp/native
> > 	compiler=sim
> > 	compiler_def=debug
> > 	name=sim_test
> > 	project=test

Hi Nges,

That is fine, no need for a file.

Newt doesn't see the blinky target.  I am sorry to keep asking, but are
you sure you created it?  The "getting started" mynewt page instructs
the user to creates two targets:
    * sim_test
    * blinky

It looks like sim_test was created successfully.

Just to humor me, could you please try executing the below set of
commands?

$ newt target create blinky
$ newt target set blinky arch=cortex_m4
$ newt target set blinky compiler=arm-none-eabi-m4
$ newt target set blinky project=blinky
$ newt target set blinky compiler_def=debug
$ newt target set blinky bsp=hw/bsp/olimex_stm32-e407_devboard

Thanks,
Chris

> >
> >
> > $   newt -v -lDEBUG target build blinky
> > 2016/03/04 02:42:45 [DEBUG] Searching for repository, starting in
> > directory /home/ngesb/dev/larva/project/blinky
> > 2016/03/04 02:42:45 [DEBUG] Searching for repo file at
> > /home/ngesb/dev/larva/project/blinky/app.yml
> > 2016/03/04 02:42:45 [DEBUG] Searching for repo file at
> > /home/ngesb/dev/larva/project/app.yml
> > 2016/03/04 02:42:45 [DEBUG] Searching for repo file at
> > /home/ngesb/dev/larva/app.yml
> > 2016/03/04 02:42:45 [DEBUG] Found repo file at
> > /home/ngesb/dev/larva/app.yml!
> > 2016/03/04 02:42:45 [DEBUG] Repo file found, directory
> > /home/ngesb/dev/larva/app.yml, loading configuration...
> > 2016/03/04 02:42:45 [DEBUG] Configuration loaded!  Initializing .app
> > database
> > 2016/03/04 02:42:45 [DEBUG] Populating Repo configuration from
> > /home/ngesb/dev/larva/.app//app.db
> > 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key arch to val
> > sim
> > 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key name to
> > val bin2img
> > 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key bsp to
> > val hw/bsp/native
> > 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key compiler
> > to val sim
> > 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key project
> > to val bin2img
> > 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key
> > compiler_def to val debug
> > 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key name to
> > val sim_test
> > 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key arch to val
> > sim
> > 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key project
> > to val test
> > 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key
> > compiler_def to val debug
> > 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key bsp to
> > val hw/bsp/native
> > 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key
> > compiler to val sim
> > 2016/03/04 02:42:45 [DEBUG] Database initialized.
> > Importing all targets from /home/ngesb/dev/larva/autotargets  set default
> > ident
> > 2016/03/04 02:42:45 [DEBUG] Storing value sim into key _target_bin2img
> > for section compiler
> > 2016/03/04 02:42:45 [DEBUG] Key compiler, sect _target_bin2img
> > successfully updated to sim
> > 2016/03/04 02:42:45 [DEBUG] Storing value bin2img into key
> > _target_bin2img for section project
> > 2016/03/04 02:42:45 [DEBUG] Key project, sect _target_bin2img
> > successfully updated to bin2img
> > 2016/03/04 02:42:45 [DEBUG] Storing value debug into key
> > _target_bin2img for section compiler_def
> > 2016/03/04 02:42:45 [DEBUG] Key compiler_def, sect _target_bin2img
> > successfully updated to debug
> > 2016/03/04 02:42:45 [DEBUG] Storing value sim into key _target_bin2img
> > for section arch
> > 2016/03/04 02:42:45 [DEBUG] Key arch, sect _target_bin2img
> > successfully updated to sim
> > 2016/03/04 02:42:45 [DEBUG] Storing value bin2img into key
> > _target_bin2img for section name
> > 2016/03/04 02:42:45 [DEBUG] Key name, sect _target_bin2img
> > successfully updated to bin2img
> > 2016/03/04 02:42:45 [DEBUG] Storing value hw/bsp/native into key
> > _target_bin2img for section bsp
> > 2016/03/04 02:42:45 [DEBUG] Key bsp, sect _target_bin2img successfully
> > updated to hw/bsp/native
> > 2016/03/04 02:42:45 [DEBUG] goroutine 1 [running]:
> > git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli.NewNewtError(0x8f2a20,
> > 0x1f, 0xc820245bf8)
> > 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli/util.go:67
> > +0xe5
> > git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli.(*Repo).GetConfigSect(0xc820079a80,
> > 0xc820245bf8, 0xe, 0x7ffd57d5c330, 0x0, 0x0)
> > 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli/repo.go:251
> > +0x8a
> > git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli.LoadTarget(0xc820079a80,
> > 0x7ffd57d5c330, 0x6, 0xc82002a280, 0x0, 0x0)
> > 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli/target.go:136
> > +0xf3
> > main.targetBuildCmd(0xc8200d9400, 0xc8201d68d0, 0x1, 0x3)
> > 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/newt.go:206
> > +0xca
> > github.com/spf13/cobra.(*Command).execute(0xc8200d9400, 0xc820214540,
> > 0x3, 0x4, 0x0, 0x0)
> > 	/home/ccollins/dev/go/src/github.com/spf13/cobra/command.go:569 +0x85a
> > github.com/spf13/cobra.(*Command).ExecuteC(0xc8200d8200, 0xc8200d9400, 0x0,
> > 0x0)
> > 	/home/ccollins/dev/go/src/github.com/spf13/cobra/command.go:656 +0x55c
> > github.com/spf13/cobra.(*Command).Execute(0xc8200d8200, 0x0, 0x0)
> > 	/home/ccollins/dev/go/src/github.com/spf13/cobra/command.go:615 +0x2d
> > main.main()
> > 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/newt.go:1454
> > +0x25
> >
> > goroutine 17 [syscall, locked to thread]:
> > runtime.goexit()
> > 	/usr/local/go/src/runtime/asm_amd64.s:1998 +0x1
> >
> > goroutine 5 [syscall]:
> > os/signal.signal_recv(0x0)
> > 	/usr/local/go/src/runtime/sigqueue.go:116 +0x132
> > os/signal.loop()
> > 	/usr/local/go/src/os/signal/signal_unix.go:22 +0x18
> > created by os/signal.init.1
> > 	/usr/local/go/src/os/signal/signal_unix.go:28 +0x37
> >
> > goroutine 6 [chan receive]:
> > database/sql.(*DB).connectionOpener(0xc820189080)
> > 	/usr/local/go/src/database/sql/sql.go:727 +0x45
> > created by database/sql.Open
> > 	/usr/local/go/src/database/sql/sql.go:493 +0x33f
> >
> > Error: No configuration section exists
> >
> >
> >
> > On 3/4/16, Christopher Collins <ch...@runtime.io> wrote:
> >> Hi Nges,
> >>
> >> Can you please run the following commands and send the output?
> >>
> >>     newt target show
> >>     newt -v -lDEBUG target build blinky
> >>
> >> It is probably going to generate a lot of text.
> >>
> >> Thanks,
> >> Chris
> >>
> >> On Fri, Mar 04, 2016 at 02:23:33AM +0100, Nges B wrote:
> >>> Yes I have done all the above exactly as you have given and have the
> >>> execpected results.
> >>>
> >>> Then from my reading here
> >>> http://mynewt.apache.org/os/get_started/project1/#build-test-code-on-simulator
> >>>
> >>> it says I should run the following
> >>>
> >>> $ cd ~/dev/larva/hw/bsp/olimex_stm32-e407_devboard
> >>> $ diff olimex_stm32-e407_devboard.ld run_from_sram.ld
> >>> $ cp run_from_sram.ld olimex_stm32-e407_devboard.ld
> >>> $ cd ~/dev/larva/project/blinky/
> >>>
> >>> all the above commands give me expected output.
> >>> now when I run
> >>>
> >>> $ newt target build blinky
> >>>
> >>> I get the following error
> >>>
> >>> Error: No configuration section exists
> >>>
> >>> so I do not understand what the error is.
> >>>
> >>>
> >>> On 3/4/16, Christopher Collins <ch...@runtime.io> wrote:
> >>> > Hi Nges,
> >>> >
> >>> > Did you create the 'blinky' target using newt?  This process is a bit
> >>> > of
> >>> > a hassle at the moment, but you only have to do it once.
> >>> >
> >>> > The following set of commands should do the trick:
> >>> >
> >>> >     $ newt target create blinky
> >>> >     $ newt target set blinky arch=cortex_m4
> >>> >     $ newt target set blinky compiler=arm-none-eabi-m4
> >>> >     $ newt target set blinky project=blinky
> >>> >     $ newt target set blinky compiler_def=debug
> >>> >     $ newt target set blinky bsp=hw/bsp/olimex_stm32-e407_devboard
> >>> >
> >>> >
> >>> > From http://mynewt.apache.org/os/get_started/project1/ :
> >>> >
> >>> >     $ newt target create blinky
> >>> >     Creating target blinky
> >>> >     Target blinky sucessfully created!
> >>> >     $ newt target set blinky arch=cortex_m4
> >>> >     Target blinky successfully set arch to arm
> >>> >     $ newt target set blinky compiler=arm-none-eabi-m4
> >>> >     Target blinky successfully set compiler to arm-none-eabi-m4
> >>> >     $ newt target set blinky project=blinky
> >>> >     Target blinky successfully set project to blinky
> >>> >     $ newt target set blinky compiler_def=debug
> >>> >     Target blinky successfully set compiler_def to debug
> >>> >     $ newt target set blinky bsp=hw/bsp/olimex_stm32-e407_devboard
> >>> >     Target blinky successfully set bsp to
> >>> > hw/bsp/olimex_stm32-e407_devboard
> >>> >     $ newt target show blinky
> >>> >     blinky
> >>> >         arch=cortex_m4
> >>> >         bsp=hw/bsp/olimex_stm32-e407_devboard
> >>> >         compiler=arm-none-eabi-m4
> >>> >         compiler_def=debug
> >>> >         name=blinky
> >>> >         project=blinky
> >>> >
> >>> > Chris
> >>> >
> >>> > On Fri, Mar 04, 2016 at 02:04:56AM +0100, Nges B wrote:
> >>> >> Have successfully run all the commands needed for the blinky project.
> >>> >> Now wen I run  $ newt target build blinky
> >>> >> i get the error "Error: No configuration section exists"
> >>> >> Please can somebody help me and Identify where I went wrong or I need
> >>> >> to to to get the Configuration section exists?
> >>> >> Thanks in advance
> >>> >
> >>>
> >>>
> >>> --
> >>> "it is good to dream and work for the dreams than not to dream"
> >>
> >
> >
> > --
> > "it is good to dream and work for the dreams than not to dream"
> >
> 
> 
> -- 
> "it is good to dream and work for the dreams than not to dream"

Re: Build Blinky

Posted by Nges B <ng...@gmail.com>.
Is that ok or I should put the output in a file??

On 3/4/16, Nges B <ng...@gmail.com> wrote:
> $   newt target show
> bin2img
> 	arch=sim
> 	bsp=hw/bsp/native
> 	compiler=sim
> 	compiler_def=debug
> 	name=bin2img
> 	project=bin2img
> sim_test
> 	arch=sim
> 	bsp=hw/bsp/native
> 	compiler=sim
> 	compiler_def=debug
> 	name=sim_test
> 	project=test
>
>
> $   newt -v -lDEBUG target build blinky
> 2016/03/04 02:42:45 [DEBUG] Searching for repository, starting in
> directory /home/ngesb/dev/larva/project/blinky
> 2016/03/04 02:42:45 [DEBUG] Searching for repo file at
> /home/ngesb/dev/larva/project/blinky/app.yml
> 2016/03/04 02:42:45 [DEBUG] Searching for repo file at
> /home/ngesb/dev/larva/project/app.yml
> 2016/03/04 02:42:45 [DEBUG] Searching for repo file at
> /home/ngesb/dev/larva/app.yml
> 2016/03/04 02:42:45 [DEBUG] Found repo file at
> /home/ngesb/dev/larva/app.yml!
> 2016/03/04 02:42:45 [DEBUG] Repo file found, directory
> /home/ngesb/dev/larva/app.yml, loading configuration...
> 2016/03/04 02:42:45 [DEBUG] Configuration loaded!  Initializing .app
> database
> 2016/03/04 02:42:45 [DEBUG] Populating Repo configuration from
> /home/ngesb/dev/larva/.app//app.db
> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key arch to val
> sim
> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key name to
> val bin2img
> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key bsp to
> val hw/bsp/native
> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key compiler
> to val sim
> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key project
> to val bin2img
> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key
> compiler_def to val debug
> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key name to
> val sim_test
> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key arch to val
> sim
> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key project
> to val test
> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key
> compiler_def to val debug
> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key bsp to
> val hw/bsp/native
> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key
> compiler to val sim
> 2016/03/04 02:42:45 [DEBUG] Database initialized.
> Importing all targets from /home/ngesb/dev/larva/autotargets  set default
> ident
> 2016/03/04 02:42:45 [DEBUG] Storing value sim into key _target_bin2img
> for section compiler
> 2016/03/04 02:42:45 [DEBUG] Key compiler, sect _target_bin2img
> successfully updated to sim
> 2016/03/04 02:42:45 [DEBUG] Storing value bin2img into key
> _target_bin2img for section project
> 2016/03/04 02:42:45 [DEBUG] Key project, sect _target_bin2img
> successfully updated to bin2img
> 2016/03/04 02:42:45 [DEBUG] Storing value debug into key
> _target_bin2img for section compiler_def
> 2016/03/04 02:42:45 [DEBUG] Key compiler_def, sect _target_bin2img
> successfully updated to debug
> 2016/03/04 02:42:45 [DEBUG] Storing value sim into key _target_bin2img
> for section arch
> 2016/03/04 02:42:45 [DEBUG] Key arch, sect _target_bin2img
> successfully updated to sim
> 2016/03/04 02:42:45 [DEBUG] Storing value bin2img into key
> _target_bin2img for section name
> 2016/03/04 02:42:45 [DEBUG] Key name, sect _target_bin2img
> successfully updated to bin2img
> 2016/03/04 02:42:45 [DEBUG] Storing value hw/bsp/native into key
> _target_bin2img for section bsp
> 2016/03/04 02:42:45 [DEBUG] Key bsp, sect _target_bin2img successfully
> updated to hw/bsp/native
> 2016/03/04 02:42:45 [DEBUG] goroutine 1 [running]:
> git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli.NewNewtError(0x8f2a20,
> 0x1f, 0xc820245bf8)
> 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli/util.go:67
> +0xe5
> git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli.(*Repo).GetConfigSect(0xc820079a80,
> 0xc820245bf8, 0xe, 0x7ffd57d5c330, 0x0, 0x0)
> 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli/repo.go:251
> +0x8a
> git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli.LoadTarget(0xc820079a80,
> 0x7ffd57d5c330, 0x6, 0xc82002a280, 0x0, 0x0)
> 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli/target.go:136
> +0xf3
> main.targetBuildCmd(0xc8200d9400, 0xc8201d68d0, 0x1, 0x3)
> 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/newt.go:206
> +0xca
> github.com/spf13/cobra.(*Command).execute(0xc8200d9400, 0xc820214540,
> 0x3, 0x4, 0x0, 0x0)
> 	/home/ccollins/dev/go/src/github.com/spf13/cobra/command.go:569 +0x85a
> github.com/spf13/cobra.(*Command).ExecuteC(0xc8200d8200, 0xc8200d9400, 0x0,
> 0x0)
> 	/home/ccollins/dev/go/src/github.com/spf13/cobra/command.go:656 +0x55c
> github.com/spf13/cobra.(*Command).Execute(0xc8200d8200, 0x0, 0x0)
> 	/home/ccollins/dev/go/src/github.com/spf13/cobra/command.go:615 +0x2d
> main.main()
> 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/newt.go:1454
> +0x25
>
> goroutine 17 [syscall, locked to thread]:
> runtime.goexit()
> 	/usr/local/go/src/runtime/asm_amd64.s:1998 +0x1
>
> goroutine 5 [syscall]:
> os/signal.signal_recv(0x0)
> 	/usr/local/go/src/runtime/sigqueue.go:116 +0x132
> os/signal.loop()
> 	/usr/local/go/src/os/signal/signal_unix.go:22 +0x18
> created by os/signal.init.1
> 	/usr/local/go/src/os/signal/signal_unix.go:28 +0x37
>
> goroutine 6 [chan receive]:
> database/sql.(*DB).connectionOpener(0xc820189080)
> 	/usr/local/go/src/database/sql/sql.go:727 +0x45
> created by database/sql.Open
> 	/usr/local/go/src/database/sql/sql.go:493 +0x33f
>
> Error: No configuration section exists
>
>
>
> On 3/4/16, Christopher Collins <ch...@runtime.io> wrote:
>> Hi Nges,
>>
>> Can you please run the following commands and send the output?
>>
>>     newt target show
>>     newt -v -lDEBUG target build blinky
>>
>> It is probably going to generate a lot of text.
>>
>> Thanks,
>> Chris
>>
>> On Fri, Mar 04, 2016 at 02:23:33AM +0100, Nges B wrote:
>>> Yes I have done all the above exactly as you have given and have the
>>> execpected results.
>>>
>>> Then from my reading here
>>> http://mynewt.apache.org/os/get_started/project1/#build-test-code-on-simulator
>>>
>>> it says I should run the following
>>>
>>> $ cd ~/dev/larva/hw/bsp/olimex_stm32-e407_devboard
>>> $ diff olimex_stm32-e407_devboard.ld run_from_sram.ld
>>> $ cp run_from_sram.ld olimex_stm32-e407_devboard.ld
>>> $ cd ~/dev/larva/project/blinky/
>>>
>>> all the above commands give me expected output.
>>> now when I run
>>>
>>> $ newt target build blinky
>>>
>>> I get the following error
>>>
>>> Error: No configuration section exists
>>>
>>> so I do not understand what the error is.
>>>
>>>
>>> On 3/4/16, Christopher Collins <ch...@runtime.io> wrote:
>>> > Hi Nges,
>>> >
>>> > Did you create the 'blinky' target using newt?  This process is a bit
>>> > of
>>> > a hassle at the moment, but you only have to do it once.
>>> >
>>> > The following set of commands should do the trick:
>>> >
>>> >     $ newt target create blinky
>>> >     $ newt target set blinky arch=cortex_m4
>>> >     $ newt target set blinky compiler=arm-none-eabi-m4
>>> >     $ newt target set blinky project=blinky
>>> >     $ newt target set blinky compiler_def=debug
>>> >     $ newt target set blinky bsp=hw/bsp/olimex_stm32-e407_devboard
>>> >
>>> >
>>> > From http://mynewt.apache.org/os/get_started/project1/ :
>>> >
>>> >     $ newt target create blinky
>>> >     Creating target blinky
>>> >     Target blinky sucessfully created!
>>> >     $ newt target set blinky arch=cortex_m4
>>> >     Target blinky successfully set arch to arm
>>> >     $ newt target set blinky compiler=arm-none-eabi-m4
>>> >     Target blinky successfully set compiler to arm-none-eabi-m4
>>> >     $ newt target set blinky project=blinky
>>> >     Target blinky successfully set project to blinky
>>> >     $ newt target set blinky compiler_def=debug
>>> >     Target blinky successfully set compiler_def to debug
>>> >     $ newt target set blinky bsp=hw/bsp/olimex_stm32-e407_devboard
>>> >     Target blinky successfully set bsp to
>>> > hw/bsp/olimex_stm32-e407_devboard
>>> >     $ newt target show blinky
>>> >     blinky
>>> >         arch=cortex_m4
>>> >         bsp=hw/bsp/olimex_stm32-e407_devboard
>>> >         compiler=arm-none-eabi-m4
>>> >         compiler_def=debug
>>> >         name=blinky
>>> >         project=blinky
>>> >
>>> > Chris
>>> >
>>> > On Fri, Mar 04, 2016 at 02:04:56AM +0100, Nges B wrote:
>>> >> Have successfully run all the commands needed for the blinky project.
>>> >> Now wen I run  $ newt target build blinky
>>> >> i get the error "Error: No configuration section exists"
>>> >> Please can somebody help me and Identify where I went wrong or I need
>>> >> to to to get the Configuration section exists?
>>> >> Thanks in advance
>>> >
>>>
>>>
>>> --
>>> "it is good to dream and work for the dreams than not to dream"
>>
>
>
> --
> "it is good to dream and work for the dreams than not to dream"
>


-- 
"it is good to dream and work for the dreams than not to dream"

Re: Build Blinky

Posted by marko kiiskila <ma...@runtime.io>.
Hi,

this output does not show blinky as a possible target.

Try ‘newt target build sim_test’ instead.

Try issuing ‘newt target create blinky’ again, and then say ‘newt target show’
again. It should you blinky this time, with no other settings.

> On Mar 3, 2016, at 5:43 PM, Nges B <ng...@gmail.com> wrote:
> 
> $   newt target show
> bin2img
> 	arch=sim
> 	bsp=hw/bsp/native
> 	compiler=sim
> 	compiler_def=debug
> 	name=bin2img
> 	project=bin2img
> sim_test
> 	arch=sim
> 	bsp=hw/bsp/native
> 	compiler=sim
> 	compiler_def=debug
> 	name=sim_test
> 	project=test
> 
> 
> $   newt -v -lDEBUG target build blinky
> 2016/03/04 02:42:45 [DEBUG] Searching for repository, starting in
> directory /home/ngesb/dev/larva/project/blinky
> 2016/03/04 02:42:45 [DEBUG] Searching for repo file at
> /home/ngesb/dev/larva/project/blinky/app.yml
> 2016/03/04 02:42:45 [DEBUG] Searching for repo file at
> /home/ngesb/dev/larva/project/app.yml
> 2016/03/04 02:42:45 [DEBUG] Searching for repo file at
> /home/ngesb/dev/larva/app.yml
> 2016/03/04 02:42:45 [DEBUG] Found repo file at /home/ngesb/dev/larva/app.yml!
> 2016/03/04 02:42:45 [DEBUG] Repo file found, directory
> /home/ngesb/dev/larva/app.yml, loading configuration...
> 2016/03/04 02:42:45 [DEBUG] Configuration loaded!  Initializing .app database
> 2016/03/04 02:42:45 [DEBUG] Populating Repo configuration from
> /home/ngesb/dev/larva/.app//app.db
> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key arch to val sim
> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key name to
> val bin2img
> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key bsp to
> val hw/bsp/native
> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key compiler
> to val sim
> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key project
> to val bin2img
> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key
> compiler_def to val debug
> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key name to
> val sim_test
> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key arch to val sim
> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key project
> to val test
> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key
> compiler_def to val debug
> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key bsp to
> val hw/bsp/native
> 2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key
> compiler to val sim
> 2016/03/04 02:42:45 [DEBUG] Database initialized.
> Importing all targets from /home/ngesb/dev/larva/autotargets  set default ident
> 2016/03/04 02:42:45 [DEBUG] Storing value sim into key _target_bin2img
> for section compiler
> 2016/03/04 02:42:45 [DEBUG] Key compiler, sect _target_bin2img
> successfully updated to sim
> 2016/03/04 02:42:45 [DEBUG] Storing value bin2img into key
> _target_bin2img for section project
> 2016/03/04 02:42:45 [DEBUG] Key project, sect _target_bin2img
> successfully updated to bin2img
> 2016/03/04 02:42:45 [DEBUG] Storing value debug into key
> _target_bin2img for section compiler_def
> 2016/03/04 02:42:45 [DEBUG] Key compiler_def, sect _target_bin2img
> successfully updated to debug
> 2016/03/04 02:42:45 [DEBUG] Storing value sim into key _target_bin2img
> for section arch
> 2016/03/04 02:42:45 [DEBUG] Key arch, sect _target_bin2img
> successfully updated to sim
> 2016/03/04 02:42:45 [DEBUG] Storing value bin2img into key
> _target_bin2img for section name
> 2016/03/04 02:42:45 [DEBUG] Key name, sect _target_bin2img
> successfully updated to bin2img
> 2016/03/04 02:42:45 [DEBUG] Storing value hw/bsp/native into key
> _target_bin2img for section bsp
> 2016/03/04 02:42:45 [DEBUG] Key bsp, sect _target_bin2img successfully
> updated to hw/bsp/native
> 2016/03/04 02:42:45 [DEBUG] goroutine 1 [running]:
> git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli.NewNewtError(0x8f2a20,
> 0x1f, 0xc820245bf8)
> 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli/util.go:67
> +0xe5
> git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli.(*Repo).GetConfigSect(0xc820079a80,
> 0xc820245bf8, 0xe, 0x7ffd57d5c330, 0x0, 0x0)
> 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli/repo.go:251
> +0x8a
> git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli.LoadTarget(0xc820079a80,
> 0x7ffd57d5c330, 0x6, 0xc82002a280, 0x0, 0x0)
> 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli/target.go:136
> +0xf3
> main.targetBuildCmd(0xc8200d9400, 0xc8201d68d0, 0x1, 0x3)
> 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/newt.go:206
> +0xca
> github.com/spf13/cobra.(*Command).execute(0xc8200d9400, 0xc820214540,
> 0x3, 0x4, 0x0, 0x0)
> 	/home/ccollins/dev/go/src/github.com/spf13/cobra/command.go:569 +0x85a
> github.com/spf13/cobra.(*Command).ExecuteC(0xc8200d8200, 0xc8200d9400, 0x0, 0x0)
> 	/home/ccollins/dev/go/src/github.com/spf13/cobra/command.go:656 +0x55c
> github.com/spf13/cobra.(*Command).Execute(0xc8200d8200, 0x0, 0x0)
> 	/home/ccollins/dev/go/src/github.com/spf13/cobra/command.go:615 +0x2d
> main.main()
> 	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/newt.go:1454
> +0x25
> 
> goroutine 17 [syscall, locked to thread]:
> runtime.goexit()
> 	/usr/local/go/src/runtime/asm_amd64.s:1998 +0x1
> 
> goroutine 5 [syscall]:
> os/signal.signal_recv(0x0)
> 	/usr/local/go/src/runtime/sigqueue.go:116 +0x132
> os/signal.loop()
> 	/usr/local/go/src/os/signal/signal_unix.go:22 +0x18
> created by os/signal.init.1
> 	/usr/local/go/src/os/signal/signal_unix.go:28 +0x37
> 
> goroutine 6 [chan receive]:
> database/sql.(*DB).connectionOpener(0xc820189080)
> 	/usr/local/go/src/database/sql/sql.go:727 +0x45
> created by database/sql.Open
> 	/usr/local/go/src/database/sql/sql.go:493 +0x33f
> 
> Error: No configuration section exists
> 
> 
> 
> On 3/4/16, Christopher Collins <ch...@runtime.io> wrote:
>> Hi Nges,
>> 
>> Can you please run the following commands and send the output?
>> 
>>    newt target show
>>    newt -v -lDEBUG target build blinky
>> 
>> It is probably going to generate a lot of text.
>> 
>> Thanks,
>> Chris
>> 
>> On Fri, Mar 04, 2016 at 02:23:33AM +0100, Nges B wrote:
>>> Yes I have done all the above exactly as you have given and have the
>>> execpected results.
>>> 
>>> Then from my reading here
>>> http://mynewt.apache.org/os/get_started/project1/#build-test-code-on-simulator
>>> 
>>> it says I should run the following
>>> 
>>> $ cd ~/dev/larva/hw/bsp/olimex_stm32-e407_devboard
>>> $ diff olimex_stm32-e407_devboard.ld run_from_sram.ld
>>> $ cp run_from_sram.ld olimex_stm32-e407_devboard.ld
>>> $ cd ~/dev/larva/project/blinky/
>>> 
>>> all the above commands give me expected output.
>>> now when I run
>>> 
>>> $ newt target build blinky
>>> 
>>> I get the following error
>>> 
>>> Error: No configuration section exists
>>> 
>>> so I do not understand what the error is.
>>> 
>>> 
>>> On 3/4/16, Christopher Collins <ch...@runtime.io> wrote:
>>>> Hi Nges,
>>>> 
>>>> Did you create the 'blinky' target using newt?  This process is a bit
>>>> of
>>>> a hassle at the moment, but you only have to do it once.
>>>> 
>>>> The following set of commands should do the trick:
>>>> 
>>>>    $ newt target create blinky
>>>>    $ newt target set blinky arch=cortex_m4
>>>>    $ newt target set blinky compiler=arm-none-eabi-m4
>>>>    $ newt target set blinky project=blinky
>>>>    $ newt target set blinky compiler_def=debug
>>>>    $ newt target set blinky bsp=hw/bsp/olimex_stm32-e407_devboard
>>>> 
>>>> 
>>>> From http://mynewt.apache.org/os/get_started/project1/ :
>>>> 
>>>>    $ newt target create blinky
>>>>    Creating target blinky
>>>>    Target blinky sucessfully created!
>>>>    $ newt target set blinky arch=cortex_m4
>>>>    Target blinky successfully set arch to arm
>>>>    $ newt target set blinky compiler=arm-none-eabi-m4
>>>>    Target blinky successfully set compiler to arm-none-eabi-m4
>>>>    $ newt target set blinky project=blinky
>>>>    Target blinky successfully set project to blinky
>>>>    $ newt target set blinky compiler_def=debug
>>>>    Target blinky successfully set compiler_def to debug
>>>>    $ newt target set blinky bsp=hw/bsp/olimex_stm32-e407_devboard
>>>>    Target blinky successfully set bsp to
>>>> hw/bsp/olimex_stm32-e407_devboard
>>>>    $ newt target show blinky
>>>>    blinky
>>>>        arch=cortex_m4
>>>>        bsp=hw/bsp/olimex_stm32-e407_devboard
>>>>        compiler=arm-none-eabi-m4
>>>>        compiler_def=debug
>>>>        name=blinky
>>>>        project=blinky
>>>> 
>>>> Chris
>>>> 
>>>> On Fri, Mar 04, 2016 at 02:04:56AM +0100, Nges B wrote:
>>>>> Have successfully run all the commands needed for the blinky project.
>>>>> Now wen I run  $ newt target build blinky
>>>>> i get the error "Error: No configuration section exists"
>>>>> Please can somebody help me and Identify where I went wrong or I need
>>>>> to to to get the Configuration section exists?
>>>>> Thanks in advance
>>>> 
>>> 
>>> 
>>> --
>>> "it is good to dream and work for the dreams than not to dream"
>> 
> 
> 
> -- 
> "it is good to dream and work for the dreams than not to dream"


Re: Build Blinky

Posted by Nges B <ng...@gmail.com>.
$   newt target show
bin2img
	arch=sim
	bsp=hw/bsp/native
	compiler=sim
	compiler_def=debug
	name=bin2img
	project=bin2img
sim_test
	arch=sim
	bsp=hw/bsp/native
	compiler=sim
	compiler_def=debug
	name=sim_test
	project=test


$   newt -v -lDEBUG target build blinky
2016/03/04 02:42:45 [DEBUG] Searching for repository, starting in
directory /home/ngesb/dev/larva/project/blinky
2016/03/04 02:42:45 [DEBUG] Searching for repo file at
/home/ngesb/dev/larva/project/blinky/app.yml
2016/03/04 02:42:45 [DEBUG] Searching for repo file at
/home/ngesb/dev/larva/project/app.yml
2016/03/04 02:42:45 [DEBUG] Searching for repo file at
/home/ngesb/dev/larva/app.yml
2016/03/04 02:42:45 [DEBUG] Found repo file at /home/ngesb/dev/larva/app.yml!
2016/03/04 02:42:45 [DEBUG] Repo file found, directory
/home/ngesb/dev/larva/app.yml, loading configuration...
2016/03/04 02:42:45 [DEBUG] Configuration loaded!  Initializing .app database
2016/03/04 02:42:45 [DEBUG] Populating Repo configuration from
/home/ngesb/dev/larva/.app//app.db
2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key arch to val sim
2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key name to
val bin2img
2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key bsp to
val hw/bsp/native
2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key compiler
to val sim
2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key project
to val bin2img
2016/03/04 02:42:45 [DEBUG] Setting sect _target_bin2img, key
compiler_def to val debug
2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key name to
val sim_test
2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key arch to val sim
2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key project
to val test
2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key
compiler_def to val debug
2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key bsp to
val hw/bsp/native
2016/03/04 02:42:45 [DEBUG] Setting sect _target_sim_test, key
compiler to val sim
2016/03/04 02:42:45 [DEBUG] Database initialized.
Importing all targets from /home/ngesb/dev/larva/autotargets  set default ident
2016/03/04 02:42:45 [DEBUG] Storing value sim into key _target_bin2img
for section compiler
2016/03/04 02:42:45 [DEBUG] Key compiler, sect _target_bin2img
successfully updated to sim
2016/03/04 02:42:45 [DEBUG] Storing value bin2img into key
_target_bin2img for section project
2016/03/04 02:42:45 [DEBUG] Key project, sect _target_bin2img
successfully updated to bin2img
2016/03/04 02:42:45 [DEBUG] Storing value debug into key
_target_bin2img for section compiler_def
2016/03/04 02:42:45 [DEBUG] Key compiler_def, sect _target_bin2img
successfully updated to debug
2016/03/04 02:42:45 [DEBUG] Storing value sim into key _target_bin2img
for section arch
2016/03/04 02:42:45 [DEBUG] Key arch, sect _target_bin2img
successfully updated to sim
2016/03/04 02:42:45 [DEBUG] Storing value bin2img into key
_target_bin2img for section name
2016/03/04 02:42:45 [DEBUG] Key name, sect _target_bin2img
successfully updated to bin2img
2016/03/04 02:42:45 [DEBUG] Storing value hw/bsp/native into key
_target_bin2img for section bsp
2016/03/04 02:42:45 [DEBUG] Key bsp, sect _target_bin2img successfully
updated to hw/bsp/native
2016/03/04 02:42:45 [DEBUG] goroutine 1 [running]:
git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli.NewNewtError(0x8f2a20,
0x1f, 0xc820245bf8)
	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli/util.go:67
+0xe5
git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli.(*Repo).GetConfigSect(0xc820079a80,
0xc820245bf8, 0xe, 0x7ffd57d5c330, 0x0, 0x0)
	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli/repo.go:251
+0x8a
git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli.LoadTarget(0xc820079a80,
0x7ffd57d5c330, 0x6, 0xc82002a280, 0x0, 0x0)
	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/cli/target.go:136
+0xf3
main.targetBuildCmd(0xc8200d9400, 0xc8201d68d0, 0x1, 0x3)
	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/newt.go:206
+0xca
github.com/spf13/cobra.(*Command).execute(0xc8200d9400, 0xc820214540,
0x3, 0x4, 0x0, 0x0)
	/home/ccollins/dev/go/src/github.com/spf13/cobra/command.go:569 +0x85a
github.com/spf13/cobra.(*Command).ExecuteC(0xc8200d8200, 0xc8200d9400, 0x0, 0x0)
	/home/ccollins/dev/go/src/github.com/spf13/cobra/command.go:656 +0x55c
github.com/spf13/cobra.(*Command).Execute(0xc8200d8200, 0x0, 0x0)
	/home/ccollins/dev/go/src/github.com/spf13/cobra/command.go:615 +0x2d
main.main()
	/home/ccollins/dev/go/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt/newt/newt.go:1454
+0x25

goroutine 17 [syscall, locked to thread]:
runtime.goexit()
	/usr/local/go/src/runtime/asm_amd64.s:1998 +0x1

goroutine 5 [syscall]:
os/signal.signal_recv(0x0)
	/usr/local/go/src/runtime/sigqueue.go:116 +0x132
os/signal.loop()
	/usr/local/go/src/os/signal/signal_unix.go:22 +0x18
created by os/signal.init.1
	/usr/local/go/src/os/signal/signal_unix.go:28 +0x37

goroutine 6 [chan receive]:
database/sql.(*DB).connectionOpener(0xc820189080)
	/usr/local/go/src/database/sql/sql.go:727 +0x45
created by database/sql.Open
	/usr/local/go/src/database/sql/sql.go:493 +0x33f

Error: No configuration section exists



On 3/4/16, Christopher Collins <ch...@runtime.io> wrote:
> Hi Nges,
>
> Can you please run the following commands and send the output?
>
>     newt target show
>     newt -v -lDEBUG target build blinky
>
> It is probably going to generate a lot of text.
>
> Thanks,
> Chris
>
> On Fri, Mar 04, 2016 at 02:23:33AM +0100, Nges B wrote:
>> Yes I have done all the above exactly as you have given and have the
>> execpected results.
>>
>> Then from my reading here
>> http://mynewt.apache.org/os/get_started/project1/#build-test-code-on-simulator
>>
>> it says I should run the following
>>
>> $ cd ~/dev/larva/hw/bsp/olimex_stm32-e407_devboard
>> $ diff olimex_stm32-e407_devboard.ld run_from_sram.ld
>> $ cp run_from_sram.ld olimex_stm32-e407_devboard.ld
>> $ cd ~/dev/larva/project/blinky/
>>
>> all the above commands give me expected output.
>> now when I run
>>
>> $ newt target build blinky
>>
>> I get the following error
>>
>> Error: No configuration section exists
>>
>> so I do not understand what the error is.
>>
>>
>> On 3/4/16, Christopher Collins <ch...@runtime.io> wrote:
>> > Hi Nges,
>> >
>> > Did you create the 'blinky' target using newt?  This process is a bit
>> > of
>> > a hassle at the moment, but you only have to do it once.
>> >
>> > The following set of commands should do the trick:
>> >
>> >     $ newt target create blinky
>> >     $ newt target set blinky arch=cortex_m4
>> >     $ newt target set blinky compiler=arm-none-eabi-m4
>> >     $ newt target set blinky project=blinky
>> >     $ newt target set blinky compiler_def=debug
>> >     $ newt target set blinky bsp=hw/bsp/olimex_stm32-e407_devboard
>> >
>> >
>> > From http://mynewt.apache.org/os/get_started/project1/ :
>> >
>> >     $ newt target create blinky
>> >     Creating target blinky
>> >     Target blinky sucessfully created!
>> >     $ newt target set blinky arch=cortex_m4
>> >     Target blinky successfully set arch to arm
>> >     $ newt target set blinky compiler=arm-none-eabi-m4
>> >     Target blinky successfully set compiler to arm-none-eabi-m4
>> >     $ newt target set blinky project=blinky
>> >     Target blinky successfully set project to blinky
>> >     $ newt target set blinky compiler_def=debug
>> >     Target blinky successfully set compiler_def to debug
>> >     $ newt target set blinky bsp=hw/bsp/olimex_stm32-e407_devboard
>> >     Target blinky successfully set bsp to
>> > hw/bsp/olimex_stm32-e407_devboard
>> >     $ newt target show blinky
>> >     blinky
>> >         arch=cortex_m4
>> >         bsp=hw/bsp/olimex_stm32-e407_devboard
>> >         compiler=arm-none-eabi-m4
>> >         compiler_def=debug
>> >         name=blinky
>> >         project=blinky
>> >
>> > Chris
>> >
>> > On Fri, Mar 04, 2016 at 02:04:56AM +0100, Nges B wrote:
>> >> Have successfully run all the commands needed for the blinky project.
>> >> Now wen I run  $ newt target build blinky
>> >> i get the error "Error: No configuration section exists"
>> >> Please can somebody help me and Identify where I went wrong or I need
>> >> to to to get the Configuration section exists?
>> >> Thanks in advance
>> >
>>
>>
>> --
>> "it is good to dream and work for the dreams than not to dream"
>


-- 
"it is good to dream and work for the dreams than not to dream"

Re: Build Blinky

Posted by Christopher Collins <ch...@runtime.io>.
Hi Nges,

Can you please run the following commands and send the output?

    newt target show
    newt -v -lDEBUG target build blinky

It is probably going to generate a lot of text.

Thanks,
Chris

On Fri, Mar 04, 2016 at 02:23:33AM +0100, Nges B wrote:
> Yes I have done all the above exactly as you have given and have the
> execpected results.
> 
> Then from my reading here
> http://mynewt.apache.org/os/get_started/project1/#build-test-code-on-simulator
> 
> it says I should run the following
> 
> $ cd ~/dev/larva/hw/bsp/olimex_stm32-e407_devboard
> $ diff olimex_stm32-e407_devboard.ld run_from_sram.ld
> $ cp run_from_sram.ld olimex_stm32-e407_devboard.ld
> $ cd ~/dev/larva/project/blinky/
> 
> all the above commands give me expected output.
> now when I run
> 
> $ newt target build blinky
> 
> I get the following error
> 
> Error: No configuration section exists
> 
> so I do not understand what the error is.
> 
> 
> On 3/4/16, Christopher Collins <ch...@runtime.io> wrote:
> > Hi Nges,
> >
> > Did you create the 'blinky' target using newt?  This process is a bit of
> > a hassle at the moment, but you only have to do it once.
> >
> > The following set of commands should do the trick:
> >
> >     $ newt target create blinky
> >     $ newt target set blinky arch=cortex_m4
> >     $ newt target set blinky compiler=arm-none-eabi-m4
> >     $ newt target set blinky project=blinky
> >     $ newt target set blinky compiler_def=debug
> >     $ newt target set blinky bsp=hw/bsp/olimex_stm32-e407_devboard
> >
> >
> > From http://mynewt.apache.org/os/get_started/project1/ :
> >
> >     $ newt target create blinky
> >     Creating target blinky
> >     Target blinky sucessfully created!
> >     $ newt target set blinky arch=cortex_m4
> >     Target blinky successfully set arch to arm
> >     $ newt target set blinky compiler=arm-none-eabi-m4
> >     Target blinky successfully set compiler to arm-none-eabi-m4
> >     $ newt target set blinky project=blinky
> >     Target blinky successfully set project to blinky
> >     $ newt target set blinky compiler_def=debug
> >     Target blinky successfully set compiler_def to debug
> >     $ newt target set blinky bsp=hw/bsp/olimex_stm32-e407_devboard
> >     Target blinky successfully set bsp to hw/bsp/olimex_stm32-e407_devboard
> >     $ newt target show blinky
> >     blinky
> >         arch=cortex_m4
> >         bsp=hw/bsp/olimex_stm32-e407_devboard
> >         compiler=arm-none-eabi-m4
> >         compiler_def=debug
> >         name=blinky
> >         project=blinky
> >
> > Chris
> >
> > On Fri, Mar 04, 2016 at 02:04:56AM +0100, Nges B wrote:
> >> Have successfully run all the commands needed for the blinky project.
> >> Now wen I run  $ newt target build blinky
> >> i get the error "Error: No configuration section exists"
> >> Please can somebody help me and Identify where I went wrong or I need
> >> to to to get the Configuration section exists?
> >> Thanks in advance
> >
> 
> 
> -- 
> "it is good to dream and work for the dreams than not to dream"

Re: Build Blinky

Posted by Nges B <ng...@gmail.com>.
Yes I have done all the above exactly as you have given and have the
execpected results.

Then from my reading here
http://mynewt.apache.org/os/get_started/project1/#build-test-code-on-simulator

it says I should run the following

$ cd ~/dev/larva/hw/bsp/olimex_stm32-e407_devboard
$ diff olimex_stm32-e407_devboard.ld run_from_sram.ld
$ cp run_from_sram.ld olimex_stm32-e407_devboard.ld
$ cd ~/dev/larva/project/blinky/

all the above commands give me expected output.
now when I run

$ newt target build blinky

I get the following error

Error: No configuration section exists

so I do not understand what the error is.


On 3/4/16, Christopher Collins <ch...@runtime.io> wrote:
> Hi Nges,
>
> Did you create the 'blinky' target using newt?  This process is a bit of
> a hassle at the moment, but you only have to do it once.
>
> The following set of commands should do the trick:
>
>     $ newt target create blinky
>     $ newt target set blinky arch=cortex_m4
>     $ newt target set blinky compiler=arm-none-eabi-m4
>     $ newt target set blinky project=blinky
>     $ newt target set blinky compiler_def=debug
>     $ newt target set blinky bsp=hw/bsp/olimex_stm32-e407_devboard
>
>
> From http://mynewt.apache.org/os/get_started/project1/ :
>
>     $ newt target create blinky
>     Creating target blinky
>     Target blinky sucessfully created!
>     $ newt target set blinky arch=cortex_m4
>     Target blinky successfully set arch to arm
>     $ newt target set blinky compiler=arm-none-eabi-m4
>     Target blinky successfully set compiler to arm-none-eabi-m4
>     $ newt target set blinky project=blinky
>     Target blinky successfully set project to blinky
>     $ newt target set blinky compiler_def=debug
>     Target blinky successfully set compiler_def to debug
>     $ newt target set blinky bsp=hw/bsp/olimex_stm32-e407_devboard
>     Target blinky successfully set bsp to hw/bsp/olimex_stm32-e407_devboard
>     $ newt target show blinky
>     blinky
>         arch=cortex_m4
>         bsp=hw/bsp/olimex_stm32-e407_devboard
>         compiler=arm-none-eabi-m4
>         compiler_def=debug
>         name=blinky
>         project=blinky
>
> Chris
>
> On Fri, Mar 04, 2016 at 02:04:56AM +0100, Nges B wrote:
>> Have successfully run all the commands needed for the blinky project.
>> Now wen I run  $ newt target build blinky
>> i get the error "Error: No configuration section exists"
>> Please can somebody help me and Identify where I went wrong or I need
>> to to to get the Configuration section exists?
>> Thanks in advance
>


-- 
"it is good to dream and work for the dreams than not to dream"

Re: Build Blinky

Posted by Christopher Collins <ch...@runtime.io>.
Hi Nges,

Did you create the 'blinky' target using newt?  This process is a bit of
a hassle at the moment, but you only have to do it once.

The following set of commands should do the trick:

    $ newt target create blinky
    $ newt target set blinky arch=cortex_m4
    $ newt target set blinky compiler=arm-none-eabi-m4
    $ newt target set blinky project=blinky
    $ newt target set blinky compiler_def=debug
    $ newt target set blinky bsp=hw/bsp/olimex_stm32-e407_devboard


>From http://mynewt.apache.org/os/get_started/project1/ :

    $ newt target create blinky
    Creating target blinky
    Target blinky sucessfully created!
    $ newt target set blinky arch=cortex_m4
    Target blinky successfully set arch to arm
    $ newt target set blinky compiler=arm-none-eabi-m4
    Target blinky successfully set compiler to arm-none-eabi-m4
    $ newt target set blinky project=blinky
    Target blinky successfully set project to blinky
    $ newt target set blinky compiler_def=debug
    Target blinky successfully set compiler_def to debug
    $ newt target set blinky bsp=hw/bsp/olimex_stm32-e407_devboard
    Target blinky successfully set bsp to hw/bsp/olimex_stm32-e407_devboard
    $ newt target show blinky
    blinky
        arch=cortex_m4
        bsp=hw/bsp/olimex_stm32-e407_devboard
        compiler=arm-none-eabi-m4
        compiler_def=debug
        name=blinky
        project=blinky

Chris

On Fri, Mar 04, 2016 at 02:04:56AM +0100, Nges B wrote:
> Have successfully run all the commands needed for the blinky project.
> Now wen I run  $ newt target build blinky
> i get the error "Error: No configuration section exists"
> Please can somebody help me and Identify where I went wrong or I need
> to to to get the Configuration section exists?
> Thanks in advance