TWI/I2C

Unachievable speeds

  • 1
  • 2
  • Page 2 of 2
Avra
Schreiberling
Avatar
Gender:
Location: Belgrade, Serbia
Age: 53
Homepage: rs.linkedin.com/in…
Posts: 653
Registered: 07 / 2002
Subject:

Re: TWI/I2C

 · 
Posted: 07.03.2022 - 22:43  ·  #9
Quote by Merlin

My concern with a warning is that if you generate your base application with the AppWizz, which I think most do, Warnings are disabled by default, so you would never see a problem.

Do you mean global warnings checkbox in AppWiz is disabled by default? If so, why should I care? Couldn't AppWiz simply show a summary in some memo below that checkbox or on separate tab, or a simplified warning in status bar, or just add comment to generated source code where it clearly says what error percentage is for TWI, SERIAL or whatever, so that we can decide if we can tolerate it? Even displaying calculated error percentage below TWI prescaler spinedit field triggered by onchange event of spinedit would be ok, and would even behave interactive so we can immediately play with different settings.
Merlin
Administrator
Avatar
Gender:
Age: 24
Posts: 1409
Registered: 03 / 2005
Subject:

Re: TWI/I2C

 · 
Posted: 08.03.2022 - 10:02  ·  #10
Hi Avra.

My concern is not with AppWizz per se. I always tended to use it to generate a skeleton (select the processor and just keep pressing 'Next') then build it up from there, step by step. I was a few projects in before I realised that warnings were turned off. I imagine I am not alone in that.

I will try and keep AppWizz up t o date but my first priority is the compiler.

I will take everyone's opinions into account.
  • 1
  • 2
  • Page 2 of 2
Selected quotes for multi-quoting:   0

Registered users in this topic

Currently no registered users in this section

The statistic shows who was online during the last 5 minutes. Updated every 90 seconds.
MySQL Queries: 15 · Cache Hits: 14   46   60 · Page-Gen-Time: 0.020906s · Memory Usage: 2 MB · GZIP: on · Viewport: SMXL-HiDPI