Matrix user forums

Looking at the code generated... void FCD_05481_cal_uart__SendString(MX_CHAR *FCL_DATA, MX_UINT16 FCLsz_DATA) { //Local variable definitions MX_UINT8 FCL_IDX; MX_UINT8 FCL_LEN; So - in FC8 at least you will be limited to a maximum of 255 characters if you use SendString. Note this seems to be fixed ...

Are you actually sending a string or an array of data?

- in a string 0 marks the end of string. If it was an array of data then 0 might be a valid value - and you would typically also pass a length to.

Martin

Hi Brendan, Have a look at the c generated - if there is a X = str_len(str) type statement or an index while (str[X])... then the max length will be determined by the size of this and other variables if x is 8 bit then 255 characters is probably your lot. It would be easy to write a new routine usin...

A visual bug. Using an ATTiny MCU (I tried 88 and 22 others maybe affected too) - set the clock speed to > max speed (so for I tried 16 and 32MHz) - this (correctly) says 'greater than max speed' - but then displays the 'loading targets' with whirly. This stays until clicking 'cancel' which gets rid...

No problem...

Martin

Hi Brendan,

The easiest way to check this is to define some code that does it and then look at the C generated..

For example in a calculation I do : This 'expands to' (using customize C code or view C) Martin

Currently reading 'Algorithms Illuminated' by Tim Roughgarden - and first algorithm I tried to implement in Flowcode was Quicksort. This is a great sorting algorithm - quick (as the name suggests) and also light on memory use (although it can use a fair bit on recursion calls...) So - using a very n...

I did a simple component for an i2c eeprom eeprom.fcfx - Which I've modified and used extensively since I posted it (above is a copy of the last posted version... (It's simplest and program rather than a component)) It should be fairly straightforward to get it to work with the 24c64 chip (note this...

Hi Ben,

Hope you had a good Christmas - any progress on this - it seems to affect all the chips with the USI interface.

Martin

Wishing everyone a merry Christmas and hoping that 2021 is a prosperous and happy New year.

I think Martin's house looks the cosiest...

Martin

The flowcode password doesn't seem to be properly linked to the forum password.. I changed mine for the matrix site - but the old password still works on the v9 forum.

Martin

So many displays (or is it display drivers?)

Will have a look and see - what features would you like to see though

d.. it

- good advice for holes in the socks?

Martin

No worries. If you change your mind then PM - but hopefully Matrix can get things up and running for you. I'd experiment - but without something to test on it's not an easy ask. There are a lot of good screens that are easy to use and work with - so if you are needing to get something working quickl...

As I offered with another display - if you supply me with the hardware - I'll try and get something working.

As it's a commercial project then payment would be good.

I've 'done' a component for ST7789 so have some experience with displays.

PM if you are interested..

Martin

Hi Clive, If you send me a display - I'll try and get it working. I've just been working with the st7789 and got it to work pretty well... I can return it when done. If you're interested I'll pm you my details Note I'm only offering basic functionality so no simulation . But see the st7789 topic. I ...

This seems to be a 'nomenclature' issue.

See https://github.com/JChristensen/tinySPI/issues/2 for example
MOSI / MISO are only used for programming purposes and DO (data out) and DI (data in) actually refer to the USI pin functions (and PB1 is DO...)

Martin

The MOSI pin is 'silent' in hardware mode - good signal in software. Just tested again - using a smartscope connected to PB0 or PB1 (channel 1) and channel 2 to PB2 (SCL) (Both checked for output - and in hardware mode there is none (SCL is ok)) Also just checked with code above (attiny85 spi) - and...

Hi Ben,

Any thoughts - it seems to be a case of needing to set PB1 as output instead of PB0?

Martin

Perhaps you could send me a working display. I can make another driver board.

Not sure why none of my other boards work - perhaps a bad batch?

I'll PM my details..

Martin

thanks Jorgen. Looks like a good resource.

How goes the testing? Do all your displays work okay?

Martin

Phew - it still works :D I was beginning to think I'd dreamed it.... It would be very interesting to know if any of the other displays work or not - it could just be my soldering technique really sucks and the board is getting a bit 'warm'. I'd really like to test it with the ATTiny85 and my SPI (1....

Crikes - that took a time...

If it survived the journey - just move the display from it's 'parking' place to correct place and add USB power... Has the last program 'installed'..

Martin

See https://www.matrixtsl.com/mmforums/view ... it=uart%21 - there are examples of receiving a variable length 'string' and converting this to a number. The 'trick' is to have a 'marker' for the end of string (for example a newline character)

Martin

My 'five cents' worth.. I do (to a degree) see why the packs are limited - they seem to have more 'problems' due to the complexity of the target (so, only software i2c on ARM for example) - I suspect they cause a lot more trouble per 'user' than other (possibly more mature) chip packs? I'd like to s...

Give us a pointer to the exact type of display you are using - there are lots using the same controller.... I don't think the MCU is the problem - speed / memory should be sufficient so that leads to: 1) Hardware error. Something in the setup doesn't work. So display is faulty / wiring is faulty / M...