AVR Freaks

I claim mine....

Neat! I'll certainly follow it, but count me out for the module, the commenter below probably needs it more than i do :)

Too late to hope for a nice AVR-BLE board?

The best kind of board! Zero hardware problems

I'll take one! I think this is the post you mentioned in your livestream.. 

Thanks!

I registered for the IoT event and also saw that this was the place to get the free sample.  If you still have any left, I would like one, please.  I've been hoping Microchip would get more of a presence in this market.

Thanks!

If there are any FREE AVR-BLE development boards left, I'd sure like to have one!

   Thanks!

Hi Rachel and the team.

Thank you very much for your time and efforts to put this all together. The community most certainly appreciates it.

If available, I will take one of the AVR-IoT WA.

We look forward to the rest of the series.

John.

I've used AWS for a while now and this AVR-IoT for AWS looks like it would be a great board for my next project. I'd like one!

Loved the livestream today, by the way.

I will definitely take an AWS board if available!!!

I would like a  AVR-IoT WA* board as well.  I know I chimed in yesterday for the AVR-BLE board but I'm totally up for demoing more than one model you have :-)

If any left I will be really happy to receive a AVR-BLE board with it's shinny origami box. 

Also thanks a lot for your efforts Rachel and the team.

authentication
ensuring right user is at
decryption

Secure IoT
Microchip will keep you safe
Claiming my third board

IOT is great

Security is very hard

Microchip please help

I think that is a valid one!

Meandering thoughts
How security runs right
near the encryption

A hacker does try

CryptoAuth library starts

the vault stays locked down

Aws or Google, Which to choose?

Choose anyone of both!

Microchip Supports All!!

In Spring all was free

In Summer came the vandals

Winter discontent

An A.V.R. Gift

To the madly curious

Will keep them at home.

  S.

Security through

Obscurity is not a

Very good practice.

Design Week Twenty

And corona viruses

Best wishes to all.

S.

Run at the lowest acceptable clock frequency, those megahertz burn power.

Sleep as much as possible.

Run at the lowest acceptable voltage.

Use lighter protocols.

I agree with the previous post: "Low-power is harder than you think!"

My advice:

- As stated above, low-power modes, sleep, clock frequencies, etc.

- Utilize your 32kHz clock!

- Utilize your RTC and its ability to wake the core!

- Utilize "sleep-walking" where possible

- Look at your peripherals!

- Put your peripherals to sleep, particularly radios

- Remove any unnecessary LEDs from your design

- Use the Power Debugger or similar tools

There are probably many more ideals I'm missing here, too.

Turn off all unused peripherals

Understand the impact of clock speed

Ensure you understand all the potential sleep states and use appropriately

Historically on this channel, the power drains have been the pullup resistors.

It's a tradeoff between noise immunity and power consumption.  It's engineering - there is no free lunch.  Change the bus pullups to 100k instead of 10k - and accept a few bus errors.  Change the /RESET pullup from 4.7k to 47k - and accept an occasional accidental reset.  Or refuse them all, demand minimum power despite the specifications, and order the tides to obey you, HRH Canute.

S.

My advice:

1. Choose proper micro controller frequency and proper micro controller architecture, 8-bit or 32-bit. Sometimes it is better to have 8-bit running at lower power, sometimes 32-bit, which can makeup very quickly from sleep mode, process all sensors and go to sleep mode again.

2. Do not use higher bit sensors when not necessary, use 8-bit sensors when possible to simplify subsequent processing.

3. Simplify processing as much as possible to have shorter processing loop. Invest in profiling and optimizing, may be rewrite "hot" fragments of the program using assembler to improve speed and as a result reduce power consumption.

4. Use event-based program structure (which can be more complicated to develop), instead of polling (which is easier to implement, but which consumes more resources of processor).

5. Use wired connection instead of wireless to reduce consumption and additionally improve reliability.

6. Examine and use all possible low power modes, which the micro controller supports.

7. Using RTOS may help too as it is normal nowadays, than RTOSes already have support for low power consumption modes.

8. Invest in high quality sensors, which produce lower noise data, instead of filtering noise later, say by DSP algorithms.

1) Do a power profiling with a multimeter and a special debugging session

2) Eliminate waiting loops for state chart scheduler with a sleeping period

3) replace output electromagnetic relays with a bipolar (bistate) version ones which do consume power only during transition

May I get AVR kit?

Did anyone get a PM.. just wanted to make sure I'm looking in the correct place. (Assume it would show up in messages)

Not yet for me.  I'm assuming recent events have slowed things down so I am being patient.

Yes - I wouldn't have even asked except for the reference to sending them out shortly.. 

Nothing yet...

Even if I tried all the surveys and comments, also I didn't received any reply.

I didn't receive any reply :-(

Were the expo ticket winners announced?

For AWS account setup the "zero touch provisioning kit" has a lot of relevant documentation:

https://github.com/MicrochipTech...

Then there is also an "IoT Provisioning Tool" which is linked from the AVR-IOT product page:

https://www.microchip.com/develo...

which has executables which can be used for custom provisioning as well as some basic documentation.

Just got mine! Thank you Rachel, Wayne and everyone at Microchip! Stay safe!