Microchip Studio 7.0.2542

Go To Last Post
63 posts / 0 new

Pages

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The Live Watch function seriously affects The execution of The program, which makes me feel very bad.

 

Expect register ports are as visible as Visual Studio.

 

 

Last Edited: Sun. Nov 15, 2020 - 01:11 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Your point being ..?

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

dongran wrote:
The Live Watch function seriously affects The execution of The program, which makes me feel very bad.

 

Care to explain that in better detail?  THe part about how live watch seriously affecting program execution.  Like what Micro you are debugging, and teh interface being used.  As far as you feeling bad about it....thats on you to resolve.  We can offer no solutions for that.

 

Jim

I would rather attempt something great and fail, than attempt nothing and succeed - Fortune Cookie

 

"The critical shortage here is not stuff, but time." - Johan Ekdahl

 

"Step N is required before you can do step N+1!" - ka7ehk

 

"If you want a career with a known path - become an undertaker. Dead people don't sue!" - Kartman

"Why is there a "Highway to Hell" and only a "Stairway to Heaven"? A prediction of the expected traffic load?"  - Lee "theusch"

 

Speak sweetly. It makes your words easier to digest when at a later date you have to eat them ;-)  - Source Unknown

Please Read: Code-of-Conduct

Atmel Studio6.2/AS7, DipTrace, Quartus, MPLAB, RSLogix user

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I have tested the latest IDE on UC3C-EK, and as with previous versions, The Live Watch function seriously interfere with the running of the program, and registers and IO ports are still not visible in real time.

 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

When I add 2 variables to the Live Watch window, and then run the program, the program execution becomes significantly slower.

 

When debugging is halt, microchip studio and visual studio 2015 are same. When debugging is running, the peripheral window will be invalid. Can you change it? Just like visual studio 2015, when running, The peripheral window is still valid,we can observe the value of peripheral ? 

Thanks.

Last Edited: Sun. Nov 15, 2020 - 02:04 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

dongran wrote:
The Live Watch function seriously interfere with the running of the program, and registers and IO ports are still not visible in real time.

 

Help me out here....I know of a Watch Window where you can see variables and registers Etc., but they are only viewable when you pause the execution of the program.  Are you referring to that window or something else?  If you are referring to teh Watch window, that has no bearing on your programs execution.

 

JIm

I would rather attempt something great and fail, than attempt nothing and succeed - Fortune Cookie

 

"The critical shortage here is not stuff, but time." - Johan Ekdahl

 

"Step N is required before you can do step N+1!" - ka7ehk

 

"If you want a career with a known path - become an undertaker. Dead people don't sue!" - Kartman

"Why is there a "Highway to Hell" and only a "Stairway to Heaven"? A prediction of the expected traffic load?"  - Lee "theusch"

 

Speak sweetly. It makes your words easier to digest when at a later date you have to eat them ;-)  - Source Unknown

Please Read: Code-of-Conduct

Atmel Studio6.2/AS7, DipTrace, Quartus, MPLAB, RSLogix user

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

When debugging is halt, microchip studio and visual studio 2015 are same. When debugging is running, the peripheral window will be invalid. Can you change it? Just like visual studio 2015, when running, The peripheral window is still valid,we can observe the value of peripheral ? 

Thanks.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Post a screenshot of what you are referring to.  If it' teh peripheral window I am thinking of the answer is no.  During runtime the peripheral watch window is inactive.  When you halt the program execution the window is updated with the latest contents of the peripherals.  It has NO bearing on program execution.

 

Jim

I would rather attempt something great and fail, than attempt nothing and succeed - Fortune Cookie

 

"The critical shortage here is not stuff, but time." - Johan Ekdahl

 

"Step N is required before you can do step N+1!" - ka7ehk

 

"If you want a career with a known path - become an undertaker. Dead people don't sue!" - Kartman

"Why is there a "Highway to Hell" and only a "Stairway to Heaven"? A prediction of the expected traffic load?"  - Lee "theusch"

 

Speak sweetly. It makes your words easier to digest when at a later date you have to eat them ;-)  - Source Unknown

Please Read: Code-of-Conduct

Atmel Studio6.2/AS7, DipTrace, Quartus, MPLAB, RSLogix user

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Any form of "live watch" involves the code not running at full speed but running one step, stopping, reading/updating the state of the variable then continuing. It's bound to be slow, what were you expecting? (To be honest such a function is a bit of a toy and of little practical use anyway).

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Actually, the UPDI unit can read some parts of memory, including SRAM and most I/O registers, without pausing execution (i.e. not using any debug commands, which are proprietary anyway...).

Probably if the CPU unit and UPDI unit try to read at the same time, a delay will happen, but still, true live monitoring seems to be possible for UPDI devices, in theory.

 

note: only for variables that the updi can read atomically, that is, 8 and possibly 16 bit in size.

Last Edited: Sun. Nov 15, 2020 - 05:05 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Don't know how much of UC3 OCD is implemented in Microchip Studio.

UC3C-EK has a NEXUS connector for AVR ONE!; the data is into AVR ONE! though I don't know where the data goes (hope a UC3 operator follows this thread)

IIRC, UC3 NanoTraceTM is in Atmel-ICE.

 

AVR® UC3 On-Chip Debug System | Atmel-ICE

...

  • Real-time Program Counter branch tracing, data trace, process trace (supported only by debuggers with parallel trace capture port)

...

Auxiliary (AUX) Physical (including JTAG) | AVR ONE!

Atmel Studio 6.2 Service Pack 1 | Microchip Studio Release Note

...

  • Support for trace buffers for Arm (MTB) and 32-bit AVR UC3 (NanoTrace)

...

 


UC3C-EK

AVR ONE!

 

"Dare to be naïve." - Buckminster Fuller

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

El Tangas wrote:
... without pausing execution ...
to elaborate, arbitration between UPDI and CPU is a part of the instruction timing.

El Tangas wrote:
(i.e. not using any debug commands, ...
iow, uses the UPDI instructions per the datasheet.

El Tangas wrote:
... true live monitoring seems to be possible for UPDI devices, in theory.
Would be useful when actualized (UPDI PDY is akin to a 1-wire UART, PDI PHY is akin to a USART)

 


Instruction Set Summary | AVR® Instruction Set Manual

[mid-page, AVRxt]

Table 4. Data Transfer Instructions

Instruction Set Summary | AVR® Instruction Set Manual

[bottom]

2.Cycle time for data memory access assumes internal RAM access, and are not valid for access to NVM. A minimum of one extra cycle must be added when accessing NVM. The additional time varies dependent on the NVM module implementation. See the NVMCTRL section in the specific devices data sheet for more information.

 

AVR - Calibration & Daq toolchain? | AVR Freaks

 

"Dare to be naïve." - Buckminster Fuller

Pages