Atmel Studio - new project from Makefile error (shell related)

ChibiOS public support forum for topics related to the Atmel AVR family of micro-controllers.

Moderators: utzig, tfAteba

vctrvlad
Posts: 21
Joined: Mon Aug 28, 2017 2:27 pm
Location: Timisoara, Romania
Has thanked: 1 time
Been thanked: 3 times

Re: Atmel Studio - new project from Makefile error (shell related)

Postby vctrvlad » Sun Sep 17, 2017 7:55 pm

Hi,

I managed to put together some info which is stored for the moment in the following place:
http://atelieruldigital.ro/tiki/tiki-view_articles.php

Please have a look in the following order:
http://atelieruldigital.ro/tiki/tiki-re ... rticleId=1
http://atelieruldigital.ro/tiki/tiki-re ... rticleId=2

and leave a comment on the articles, or here for any observations.

Have a nice weekend,
Victor


Sorry about that guys, images were not visible outside of admin group, [lease check the articles out now:)

User avatar
tfAteba
Posts: 526
Joined: Fri Oct 16, 2015 11:03 pm
Location: Chartres, France
Has thanked: 81 times
Been thanked: 46 times

Re: Atmel Studio - new project from Makefile error (shell related)

Postby tfAteba » Sun Sep 17, 2017 9:52 pm

Hi vctrvlad,

I will try to see if I can also resolve this problem in the stable release version.


The current stable release can not be updated. But I have made changes so that for the next stable release, the problem with the EXT will be solved.

Thanks.
regards,

Theo.

vctrvlad
Posts: 21
Joined: Mon Aug 28, 2017 2:27 pm
Location: Timisoara, Romania
Has thanked: 1 time
Been thanked: 3 times

Re: Atmel Studio - new project from Makefile error (shell related)

Postby vctrvlad » Mon Sep 18, 2017 6:49 am

HI Theodore, ext int works now, thanks for the fix.

User avatar
tfAteba
Posts: 526
Joined: Fri Oct 16, 2015 11:03 pm
Location: Chartres, France
Has thanked: 81 times
Been thanked: 46 times

Re: Atmel Studio - new project from Makefile error (shell related)

Postby tfAteba » Mon Sep 18, 2017 8:47 am

Thanks for the feedback :D .
regards,

Theo.

User avatar
tfAteba
Posts: 526
Joined: Fri Oct 16, 2015 11:03 pm
Location: Chartres, France
Has thanked: 81 times
Been thanked: 46 times

Re: Atmel Studio - new project from Makefile error (shell related)

Postby tfAteba » Tue Sep 19, 2017 8:02 am

Hi Victor,

Thanks for your feedback. For what I understand, you give a feedback about the ChibiOS documentation, so this post is not the good place for.
You should open a new post for example in Development and feedback to give your feedback.

Can you delete the post here and open another post as suggest, if you can't I can do it for you.

Thanks in advance.
regards,

Theo.

User avatar
Giovanni
Site Admin
Posts: 13085
Joined: Wed May 27, 2009 8:48 am
Location: Salerno, Italy
Has thanked: 759 times
Been thanked: 637 times
Contact:

Re: Atmel Studio - new project from Makefile error (shell related)

Postby Giovanni » Tue Sep 19, 2017 12:10 pm

It should go in bug reports.

Giovanni

vctrvlad
Posts: 21
Joined: Mon Aug 28, 2017 2:27 pm
Location: Timisoara, Romania
Has thanked: 1 time
Been thanked: 3 times

Re: Atmel Studio - new project from Makefile error (shell related)

Postby vctrvlad » Tue Sep 19, 2017 7:00 pm

Indeed, feedback is for documentation, because I am trying to learg this OS, but anyway, I don't know what's the right way to do it.
I have never been good to learn the right way by my self...so I started by observing the filex in ...ChibiOS_17.6.0\testhal\AVR\EXT\ folder, and I came across these...

Anyhow, if someone can point a better way to understand it fast, I'll make sure to give a beer, or to send a postcard. :D :))

Theodore, could you, please, delete my post regarding documentation issues(I don't have the rights to do this), and I will post it again in the proper place?

Thank you in advance,
victor

User avatar
tfAteba
Posts: 526
Joined: Fri Oct 16, 2015 11:03 pm
Location: Chartres, France
Has thanked: 81 times
Been thanked: 46 times

Re: Atmel Studio - new project from Makefile error (shell related)

Postby tfAteba » Tue Sep 19, 2017 7:48 pm

The post is now deleted. You can create another to the right place.

Thanks.
regards,

Theo.

vctrvlad
Posts: 21
Joined: Mon Aug 28, 2017 2:27 pm
Location: Timisoara, Romania
Has thanked: 1 time
Been thanked: 3 times

Re: Atmel Studio - new project from Makefile error (shell related)

Postby vctrvlad » Fri Sep 22, 2017 10:42 pm

while trying out the ...ChibiOs\trunk\demos\AVR\RT-ARDUINO-MEGA\ example, I was not able to reproduce the behavior described in the readme file.

Out of the box, by only modifying the makefile according to my setup, I get this on pin13 of ArduinoMega (2560):
2017-09-22 21_47_52-PicoScope 6.png


It seems that the system is periodically resetting;

by commenting out the following line:
" test_execute((BaseSequentialStream *)&SD1);"

it seems that the system is not resetting anymore, but the described behavior in the readme file is still not observable.
I would expect a rectangular signal 50% dutycicle with a frequency of 0.5Hz.
What I am getting instead is this:
2017-09-22 23_28_46-PicoScope 6.png

with a 1s/div time base

2017-09-22 23_30_06-PicoScope 6.png

with a 500us/div timebase

Can anyone confirm that this is happening, or am I doing something wrong???

Anyhow, what is the purpose of test_execute((BaseSequentialStream *)&SD1);???

Regards,
Victor

User avatar
tfAteba
Posts: 526
Joined: Fri Oct 16, 2015 11:03 pm
Location: Chartres, France
Has thanked: 81 times
Been thanked: 46 times

Re: Atmel Studio - new project from Makefile error (shell related)

Postby tfAteba » Fri Sep 22, 2017 11:05 pm

Hi Victor,

It seems that the system is periodically resetting;

The system is not resetting, if you connect to the serial console, you will see the output of the ChibiOS bench mark also called ChibiOS Test suite.

by commenting out the following line:
" test_execute((BaseSequentialStream *)&SD1);"

By commenting this you are simply remove the execution of the bench mark. So your LED can immediately blink every second.

Anyhow, what is the purpose of test_execute((BaseSequentialStream *)&SD1);???

The purpose of this instruction is to make un bunch of test depending of the configuration you made. So some features can be tested: Here is for example the output of my board:

Code: Select all

*** ChibiOS/RT Test Suite
***
*** Compiled:     Sep 22 2017 - 23:49:18
*** Platform:     AVR
*** Test Board:   Arduino Mega
*** Compiler:     GCC 4.9.2
*** Architecture: MegaAVR
*** Port Info:    None

----------------------------------------------------------------------------
--- Test Case 1.1 (Kernel Info)
--- Product:                   ChibiOS/RT
--- Stable Flag:               0
--- Version String:            4.0.0
--- Major Number:              4
--- Minor Number:              0
--- Patch Number:              0
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 1.2 (Kernel Settings)
--- CH_CFG_ST_RESOLUTION:      16
--- CH_CFG_ST_FREQUENCY:       15624
--- CH_CFG_ST_TIMEDELTA:       2
--- CH_CFG_TIME_QUANTUM:       0
--- CH_CFG_MEMCORE_SIZE:       128
--- CH_CFG_NO_IDLE_THREAD:     0
--- CH_CFG_OPTIMIZE_SPEED:     1
--- CH_CFG_USE_TM:             0
--- CH_CFG_USE_REGISTRY:       1
--- CH_CFG_USE_WAITEXIT:       1
--- CH_CFG_USE_SEMAPHORES:     1
--- CH_CFG_USE_SEMAPHORES_PRI: 0
--- CH_CFG_USE_MUTEXES:        1
--- CH_CFG_USE_MUTEXES_RECURS: 0
--- CH_CFG_USE_CONDVARS:       1
--- CH_CFG_USE_CONDVARS_TIMEO: 1
--- CH_CFG_USE_EVENTS:         1
--- CH_CFG_USE_EVENTS_TIMEOUT: 1
--- CH_CFG_USE_MESSAGES:       1
--- CH_CFG_USE_MESSAGES_PRI:   0
--- CH_CFG_USE_MAILBOXES:      1
--- CH_CFG_USE_MEMCORE:        0
--- CH_CFG_USE_HEAP:           0
--- CH_CFG_USE_MEMPOOLS:       0
--- CH_CFG_USE_DYNAMIC:        0
--- CH_DBG_STATISTICS:         0
--- CH_DBG_SYSTEM_STATE_CHECK: 0
--- CH_DBG_ENABLE_CHECKS:      0
--- CH_DBG_ENABLE_ASSERTS:     0
--- CH_DBG_TRACE_MASK:         255
--- CH_DBG_TRACE_BUFFER_SIZE:  128
--- CH_DBG_ENABLE_STACK_CHECK: 0
--- CH_DBG_FILL_THREADS:       0
--- CH_DBG_THREADS_PROFILING:  0
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 2.1 (System integrity functionality)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 2.2 (Critical zones functionality)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 2.3 (Interrupts handling functionality)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 2.4 (System Tick Counter functionality)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 3.1 (Thread Sleep functionality)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 3.2 (Ready List functionality, threads priority order)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 3.3 (Priority change test)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 3.4 (Priority change test with Priority Inheritance)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 4.1 (Suspend and Resume functionality)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 5.1 (Semaphore primitives, no state change)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 5.2 (Semaphore enqueuing test)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 5.3 (Semaphore timeout test)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 5.4 (Testing chSemAddCounterI() functionality)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 5.5 (Testing chSemWaitSignal() functionality)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 5.6 (Testing Binary Semaphores special case)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 6.1 (Priority enqueuing test)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 6.2 (Priority return verification)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 6.3 (Repeated locks, non recursive scenario)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 6.4 (Condition Variable signal test)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 6.5 (Condition Variable broadcast test)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 6.6 (Condition Variable priority boost test)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 7.1 (Messages Server loop)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 8.1 (Events registration)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 8.2 (Event Flags dispatching)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 8.3 (Events Flags wait using chEvtWaitOne())
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 8.4 (Events Flags wait using chEvtWaitAny())
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 8.5 (Events Flags wait using chEvtWaitAll())
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 8.6 (Events Flags wait timeouts)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 8.7 (Broadcasting using chEvtBroadcast())
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 9.1 (Mailbox normal API, non-blocking tests)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 9.2 (Mailbox I-Class API, non-blocking tests)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 9.3 (Mailbox timeouts)
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 10.1 (Messages performance #1)
--- Score : 32850 msgs/S, 65700 ctxswc/S
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 10.2 (Messages performance #2)
--- Score : 25353 msgs/S, 50706 ctxswc/S
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 10.3 (Messages performance #3)
--- Score : 25353 msgs/S, 50706 ctxswc/S
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 10.4 (Context Switch performance)
--- Score : 91616 ctxswc/S
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 10.5 (Threads performance, full cycle)
--- Score : 20831 threads/S
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 10.6 (Threads performance, create/exit only)
--- Score : 27823 threads/S
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 10.7 (Mass reschedule performance)
--- Score : 7984 reschedules/S, 47904 ctxswc/S
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 10.8 (Round-Robin voluntary reschedule)
--- Score : 62680 ctxswc/S
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 10.9 (Virtual Timers set/reset performance)
--- Score : 61668 timers/S
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 10.10 (Semaphores wait/signal performance)
--- Score : 243320 wait+signal/S
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 10.11 (Mutexes lock/unlock performance)
--- Score : 123300 lock+unlock/S
--- Result: SUCCESS
----------------------------------------------------------------------------
--- Test Case 10.12 (RAM Footprint)
--- System: 51 bytes
--- Thread: 28 bytes
--- Timer : 10 bytes
--- Semaph: 5 bytes
--- Mutex : 8 bytes
--- CondV.: 4 bytes
--- EventS: 2 bytes
--- EventL: 7 bytes
--- MailB.: 18 bytes
--- Result: SUCCESS
----------------------------------------------------------------------------

Final result: SUCCESS


When the Test suite is finished, only in that time, you can have a led that blink correctly. Before that, the blink thread is preempted by the test suite.

Can you first test that? I'm going to try to find why your blink period is not the good one.

Thanks!
regards,

Theo.


Return to “AVR Support”

Who is online

Users browsing this forum: No registered users and 3 guests