Getting Started with Atmel Studio 7 - Episode 10 - I/O View & Bare Metal Programming References
Vložit
- čas přidán 27. 08. 2024
- Hands-on: goo.gl/8MHDwv
Context:
• Turn on LED, then blink with delay.
Programming References:
(How to easily access & what to use each for)
• Device datasheet
• Datasheet (from IO view)
• IO view (debugging)
• Kit user-guide & schematics
• Device header files
• Editor (Visual Assist)
• AVR® LibC
• Atmel START
For more information, visit:
www.microchip.c...
Very well made tutorial
If anyone's puzzled around 3:58, this may help. We know his project is for an ATtiny817, but where did the image of the Xplained Pro board appear from?
For example, the simulator can be linked to pictures of certain boards (e.g. the Butterfly). When that's done, toggling a line in the debug I/O window can make a LED in the image appear lit, even though it's only happening in a simulator window. Is that what we're seeing, and if so how did he achieve it?
The answer's "No, we're seeing something else." The key is at 1:32 when in passing he says he has the board plugged in. The image is live video of that real board, that he's just overlaid in front of his Studio screen-capture while recording the tutorial. That makes it look like some magical simulation window launched from Studio itself, but it's not; we'd see his hand if he waved it near the board.
The other trick here is live output on that board, driven from the debug I/O window even before he's written any code that affects the LED. That's a useful feature of Studio: in-circuit emulation is integrated with features that are also available for source-level debugging.
Remember though, that it's not enough just to have the board connected and powered up: toggling a LED (for example) from the I/O window can only be done in a debug session. Again he hints at this in passing: at 3:51 he mentions that he first hits "Start debugging and break".
Until then, even though the board is connected and powered, the debug I/O window is available but what it's displaying isn't "live" - it doesn't reflect the state of port registers, because it's not communicating with the board. "Start debugging and break" is enough to launch a debug session, allowing what he does in the I/O window to change what happens on the board (and, of course, to show up in that live-video image).
HTH.
Maybe from here: czcams.com/video/6JEbnyz2Mac/video.html
Thanks a lot
OUTCLR and OUTTGL don't work in i/o view as expected, why?
Hi Igor, thanks for reaching out! Which target device and version of the Microchip Studio are using? This will help us troubleshoot. Thanks!
@@MicrochipTechnology atmel sam d20 xplained pro on atmel studio 7 last release
I am using Atmel ICE and an atmega328P, using ICSP interface. What steps are needed to get "start debugging and break" going with this hardware setup? Is it possible at all with this setup?
what does it mean, when an Inpu/Output square is blue?
red: it chenged it's value from 0 -> 1 or 1-> 0 - that's clear
Kindly visit support.microchip.com for assistance. We do not provide support via CZcams. Thank you.
Why did you assign PORTB.DIR to PIN4_bm (bitmask?)
I am an absolute rookie, but I wonder if this is really bare metal programming as the gentleman is still using macros, structs, etc. Nonetheless a well made tutorial.
Just get the E70 Xplained and download the v1.5 softpack it has lots of low level examples. Use at least an i5-2400 PC- Atmel Studio (derivative of Visual Studio) is a hog! Albeit these are FOUR years old. Makes one wonder if the E7x/V7x are dead. No new E7/V71 code from Microchip, nor version like the STM32H7 at 400MHZ. Milking a dead cow?
And see this barebones work github.com/sidneycadot/same70
Sounds like an Australian accent.
South African :)
I lived 15 years in South Africa and I wasn't able to catch that.
I left SA end of 1979. I suppose the accent now is quite different due to the influence of American TV.