I am working on a project and need a bit of help here and there.
I am working on it with someone who knows a lot more than I do but he
is available only 1 day a week, so instead of posting questions on
various forums (mostly never answered) I am considering looking for
someone who can work on a retainer of X per year or something like
that and would be able to provide support.
It ranges from CPU specific stuff like how to set up one of the DACs
to generate a sinewave from precomputed values in RAM (yes lots of
examples on the web; mostly not usable except for hints) to C
questions. I have written a fair bit of C but use it as a "basic"
language, avoiding pointers and using arrays instead :) etc. And right
now I am trying to sort out STLINK V3 and why the GDB log level (shown
in Console) has mysteriously changed from 31 to 1...
On 22/04/2021 07:22, John-Smith wrote:
I am working on a project and need a bit of help here and there.
I am working on it with someone who knows a lot more than I do but he
is available only 1 day a week, so instead of posting questions on
various forums (mostly never answered) I am considering looking for
someone who can work on a retainer of X per year or something like
that and would be able to provide support.
It ranges from CPU specific stuff like how to set up one of the DACsThis is near second nature though the ST Cube hal libraries try to be
to generate a sinewave from precomputed values in RAM (yes lots of
examples on the web; mostly not usable except for hints) to C
questions. I have written a fair bit of C but use it as a "basic"
language, avoiding pointers and using arrays instead :) etc. And right
now I am trying to sort out STLINK V3 and why the GDB log level (shown
in Console) has mysteriously changed from 31 to 1...
all things for all men and so have a number of flaws.
Nothing wrong with arrays!
On Wednesday, April 28, 2021 at 7:52:07 AM UTC-7, Mike Perkins wrote:
On 22/04/2021 07:22, John-Smith wrote:
I am working on a project and need a bit of help here and there.This is near second nature though the ST Cube hal libraries try to be
I am working on it with someone who knows a lot more than I do but he
is available only 1 day a week, so instead of posting questions on
various forums (mostly never answered) I am considering looking for
someone who can work on a retainer of X per year or something like
that and would be able to provide support.
It ranges from CPU specific stuff like how to set up one of the DACs
to generate a sinewave from precomputed values in RAM (yes lots of
examples on the web; mostly not usable except for hints) to C
questions. I have written a fair bit of C but use it as a "basic"
language, avoiding pointers and using arrays instead :) etc. And right
now I am trying to sort out STLINK V3 and why the GDB log level (shown
in Console) has mysteriously changed from 31 to 1...
all things for all men and so have a number of flaws.
Nothing wrong with arrays!
Nothing wrong with pointers either.
ADC1->XXX, USART1->XXX and GPIOA->XXX are all pointers. How can you avoid pointers?
On Wednesday, April 28, 2021 at 7:52:07 AM UTC-7, Mike Perkins wrote:
On 22/04/2021 07:22, John-Smith wrote:
I am working on a project and need a bit of help here and there.This is near second nature though the ST Cube hal libraries try to be
I am working on it with someone who knows a lot more than I do but he
is available only 1 day a week, so instead of posting questions on
various forums (mostly never answered) I am considering looking for
someone who can work on a retainer of X per year or something like
that and would be able to provide support.
It ranges from CPU specific stuff like how to set up one of the DACs
to generate a sinewave from precomputed values in RAM (yes lots of
examples on the web; mostly not usable except for hints) to C
questions. I have written a fair bit of C but use it as a "basic"
language, avoiding pointers and using arrays instead :) etc. And right
now I am trying to sort out STLINK V3 and why the GDB log level (shown
in Console) has mysteriously changed from 31 to 1...
all things for all men and so have a number of flaws.
Nothing wrong with arrays!
Nothing wrong with pointers either.
ADC1->XXX, USART1->XXX and GPIOA->XXX are all pointers. How can you avoid pointers?
On 28/04/2021 16:08, Ed Lee wrote:
On Wednesday, April 28, 2021 at 7:52:07 AM UTC-7, Mike Perkins wrote:
On 22/04/2021 07:22, John-Smith wrote:
I am working on a project and need a bit of help here and there.This is near second nature though the ST Cube hal libraries try to be
I am working on it with someone who knows a lot more than I do but he
is available only 1 day a week, so instead of posting questions on
various forums (mostly never answered) I am considering looking for
someone who can work on a retainer of X per year or something like
that and would be able to provide support.
It ranges from CPU specific stuff like how to set up one of the DACs
to generate a sinewave from precomputed values in RAM (yes lots of
examples on the web; mostly not usable except for hints) to C
questions. I have written a fair bit of C but use it as a "basic"
language, avoiding pointers and using arrays instead :) etc. And right >>>> now I am trying to sort out STLINK V3 and why the GDB log level (shown >>>> in Console) has mysteriously changed from 31 to 1...
all things for all men and so have a number of flaws.
Nothing wrong with arrays!
Nothing wrong with pointers either.
ADC1->XXX, USART1->XXX and GPIOA->XXX are all pointers. How can you avoid pointers?
I'm not saying you can't. The STM32Cube suite removes some of the need
to understand pointers as everything is done through libraries. A good >example is GPIO access:
HAL_GPIO_WritePin(Port, Pin, value);
The HAL libraries are weak in some areas. By example it won't natively >implement a fast SPI slave.
On 28/04/2021 16:08, Ed Lee wrote:
On Wednesday, April 28, 2021 at 7:52:07 AM UTC-7, Mike Perkins wrote:
On 22/04/2021 07:22, John-Smith wrote:
I am working on a project and need a bit of help here and there.This is near second nature though the ST Cube hal libraries try to be
I am working on it with someone who knows a lot more than I do but he
is available only 1 day a week, so instead of posting questions on
various forums (mostly never answered) I am considering looking for
someone who can work on a retainer of X per year or something like
that and would be able to provide support.
It ranges from CPU specific stuff like how to set up one of the DACs
to generate a sinewave from precomputed values in RAM (yes lots of
examples on the web; mostly not usable except for hints) to C
questions. I have written a fair bit of C but use it as a "basic"
language, avoiding pointers and using arrays instead :) etc. And right >>>> now I am trying to sort out STLINK V3 and why the GDB log level (shown >>>> in Console) has mysteriously changed from 31 to 1...
all things for all men and so have a number of flaws.
Nothing wrong with arrays!
Nothing wrong with pointers either.
ADC1->XXX, USART1->XXX and GPIOA->XXX are all pointers. How can you avoid pointers?
I'm not saying you can't. The STM32Cube suite removes some of the need
to understand pointers as everything is done through libraries. A good >example is GPIO access:
HAL_GPIO_WritePin(Port, Pin, value);
The HAL libraries are weak in some areas. By example it won't natively >implement a fast SPI slave.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 293 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 215:55:53 |
| Calls: | 6,620 |
| Calls today: | 2 |
| Files: | 12,169 |
| Messages: | 5,317,557 |