> On Nov 4, 2015, at 12:30 PM, Sterling Hughes wrote:
>
> I think this is documentation. You may want it to be the highest
> priority task, but what if somebody has two interfaces, and doesn't
> care if they miss packets or data on the BLE link?
>
> I think it should just
+1 -- very nice first report! Thanks, Aditi!
Marvin Humphrey
On Wed, Nov 4, 2015 at 11:57 AM, P. Taylor Goetz wrote:
> +1 looks good to me.
>
> Nice work on responding to and incorporating feedback into the report.
>
> -Taylor
>
>> On Nov 3, 2015, at 6:14 PM, aditi hilbert
Thank you for your active mentorship! I have requested write access on the
Incubator Wiki to be able to post the reports after our feedback rounds.
thanks,
aditi
> On Nov 4, 2015, at 4:56 PM, Marvin Humphrey wrote:
>
> +1 -- very nice first report! Thanks, Aditi!
>
>
I dont have an answer but I would like to add something using the BLE stack as
an example. The BLE stack wants to create tasks or a task and it wants the
highest priority task. How do we let people know that the BLE stack must have
the highest priority task? Through documentation? If we let
Howdy,
I'm working on getting blinky a bit more developed as an initial
project. First part of that is getting console running on sim, which
I have working.
One thing I've been looking at, is the hal_uart starts an OS task when
initialized. The priority of that task, and stack size is defined