Dear Mikroe Team, Life time upgrades for the compilers sounds great, but only until there is no money left to add new MCUs and fix bugs. And we need to get new MCUs added and to get bugs fixed. How about making a Subscription Service for all your compilers, where customers can vote to get their MCUs...

Hi mikroe Team, something very important is missing in that list. A tool to generate defs files for new MCU. This has been requested many times. Then we don't have to wait 2 years or more to use new devices. I understand files generated with such a tool cannot be supported by mikroe, but once it ca...

Hi, I'm not sure if this is related to your code or not, but you should be aware of a bug inside the ATtiny828, that affects TWI and SPI communication. The bug has been acknowledged by Atmel in the latest datasheet, in the Errata section: 30. Errata The revision letters in this section refer to the ...

Hi, I'm writing this in case someone else has a problem getting the ATtiny828 to work as an SPI Slave. -------------------------------- Getting the ATtiny828 in SPI Slave mode turned out a few surprises... I used different ATtiny828 devices, to rule out faulty devices, but the bug was still there. T...

Hi Yes, I've tried the SPI1_XXX functions, in all thinkable combinations. In master mode they seem to work fine, but in slave mode they don't work. I've tried just about everything I can think of, for a week, but no luck. I'm starting to suspect there is a bug in the ATtiny828 definition file or the...

Hi, I tried what should be a straight forward little SPI test, but for some reason it fails every time. A master (an ATtiny828) is copying the byte on its PINA port and sends it through SPI to a slave (also an ATtiny828). The oscilloscope shows perfect signals from the master: - SS is pulled low by ...

Ah, thanks, that certainly helps for millisecond delays.

Then my wish for the future is a delay routine for variables, that takes microsecond delays.

Thanks,
Bengt

Yes, finally we agree :) If you read my first post, you will see that this is exactly my point. Delay_us() and Delay_ms() can only take constant expressions, not variables. Which is my reason for writing this post here in the wish list. It would be most convenient if the Delay_us() and Delay_ms() ro...

Hi, I tried this: procedure TestDelay1(const sTestDelay: dword); begin Delay_us(sTestDelay); end; procedure TestDelay2; var zTestDelay: dword; begin zTestDelay := 1000; Delay_us(zTestDelay); end; Both procedures fail to compile and the compiler message is: Syntax error: Expected "constant expression...

It would be most convenient if the
Delay_us() and Delay_ms() routines could take variables, not just constant expressions.

Bengt

Recreate the problem like this: 1. Click F9 to go to debug mode. 2. Arrange the windows the way you want them, write a name for the layout, e.g "My Debug Layout" and click the "Save Layout" button. 3. Click "Set Layout" button to tell the IDE that "My Debug Layout" is the one to use when debugging. ...

I switch them off in Editor Settings, but they keep coming back.
A minor issue, I know, but somewhat annoying.

Overloaded procedures and functions, distinguished by parameters, similar to what Delphi has.

Hi, Scenario: I'm single stepping my code in the debugger and have a list of 50 values in the "Watch Values" window. These values have several different representations. (Some are hex, some are binaries and some are decimal) Problem: When I abort the debugging, all the representations for the values...