Using UART through solder jumpers J7 and J9 requires Toolstick Terminal - which seems to be Windows-only.

Is there a Linux version - or can Toolstick Terminal be run using Wine?

Hello all,

I am trying to get C inline assembler to work as recommended:

#pragma src
...

#pragma asm
...
#pragma endasm

This works i.e. the C file is compiled into an assembler file SRC with the inline assembler in it.

But then this needs to be manually assembled and linked and converted into a HEX file.

Can this be done automatically? I would guess this requires some change in the Simplicity Studio project options: A modification of the C compiler / linker command line calls?

Thanks

Lothar

Datasheet says CLU3 carries to CLU0 so by wasting CLU3 one could route C to CLU0CARRY

Not sure how to do this in Configurator though. And it would introduce a tiny delay in C but possibly not important.

Regarding circuit:

(A+B)(BC)' = (A+B)(B'+C') = AB'+AC'+BB'+BC' = AB'+AC'+BC' = AB'+BC'

https://en.wikipedia.org/wiki/Consensus_theorem

or

https://en.wikipedia.org/wiki/Karnaugh_map

But if Configurator can do original circuit then no need to simplify.

> I did not see this in information in Silabs website

Not on Silabs website my question was about buying from distributors.

In Mouser TOOLSTICK560DC is listed as Non-stocked Request Delivery Quote. C8051F560-IM as Stock 0 Factory Lead Time 2 weeks. C8051F560-IQ is in stock.

Another distributor lists TOOLSTICK560DC as discontinued. Or does this mean the distributor only discontinued to sell it? If yes where to buy?

https://americas.rsdelivers.com/product/silicon-labs/toolstick560dc/c8051f560-toolstick-daughter-card/7570424

In Mouser C8051F560-IQ is still available but C8051F560-IM and TOOLSTICK560DC no longer.

Is C8051F560 EOL?

If yes what is a possible replacement?

According to datasheet, the serial bootloader takes 512 byte at the top. So only 15872 byte should be available.

I do use the bootloader for programming, but if you have C2 programmer, you should be able to erase the flash completely, and then you should have 16384 bytes

Your project is not set up for EFM8BB3 device. I cannot say how this can happen. Possibly you started from a project for another device. Or when you set up the project, something went wrong with the configurator. Possibly someone from Silabs can answer.

In the meantime I suggest you start from scratch. Either copy sample project from SLSTK2022A e.g. Blinky and if it works for you, copy your source code there.

Or you could try import my attached sample project. If this works for you, copy your source code there.

One problem you will get: all EFM8BB3 sample projects are for 4K XRAM. If you have only 2K XRAM, you will get no warning, your program will crash, if it uses more than 2K in total. Therefore you need to check Program Size message you have shown in the beginning of your question, if xdata exceeds 2K for your code.

Your project is not set up for EFM8BB3 device. I cannot say how this can happen. Possibly you started from a project for another device. Or when you set up the project, something went wrong with the configurator. Possibly someone from Silabs can answer.

In the meantime I suggest you start from scratch. Either copy sample project from SLSTK2022A e.g. Blinky and if it works for you, copy your source code there.

Or you could try import my attached sample project. If this works for you, copy your source code there.

One problem you will get: all EFM8BB3 sample projects are for 4K XRAM. If you have only 2K XRAM, you will get no warning, your program will crash. Therefore you need to check Program Size message you have shown in the beginning of your question, if xdata exceeds 2K

> So unavailable XRAM size you said can be assumed to 1024

Yes but the compiler does not know that therefore in a project xdata start address and size are specified. For example in the EFM8UB3 if the USB is not used, the complete XRAM can be setup for use.

So possibly in your EFM8BB3 project accidentally the xdata start address or size are not set correctly.

Therefore either test with one EFM8BB3 project from the available examples, which should be correct. Or upload a small project to here so it can be checked.

Or look in your project for a file with ending .m51 for EFM8BB3 the correct output should be:

LX51 ... XDATA (X:0X0-X:0XFFF)

> So unavailable XRAM size you said can be assumed to 1024

Yes but the compiler does not know that therefore in a project xdata start address and size are specified. For example in the EFM8UB3 if the USB is not used, the complete XRAM can be setup for use.

So possibly in your EFM8BB3 project accidentally the xdata start address or size are not set correctly.

Therefore either test with one EFM8BB3 project from the available examples, which should be correct. Or upload a small project to here so it can be checked.