I downloaded latest ChibiStudio for Linux. My local openocd version 0.12.0.
Config options are next:
-f interface/stlink.cfg -f target/stm32f1x.cfg -c "$_TARGETNAME configure -rtos chibios"
But there is no success.
Warn : ChibiOS/RT memory signature claims to be bigger than expected ...
Search found 26 matches
- Sun Feb 23, 2025 3:18 pm
- Forum: ChibiStudio
- Topic: openocd -rtos "chibios"
- Replies: 4
- Views: 36193
- Wed Jun 21, 2023 8:55 am
- Forum: Bug Reports
- Topic: GCC 10 lto
- Replies: 4
- Views: 6877
Re: GCC 10 lto
I can't check on very old GCC. On GCC 7 auto is good.
- Tue Jun 20, 2023 9:30 am
- Forum: Bug Reports
- Topic: GCC 10 lto
- Replies: 4
- Views: 6877
GCC 10 lto
Hi All,
After migration from older GCC to 10.2 linker produces warning regarding incorrect usage of -flto
I found that in ChibiOS it without value but should be with value.
I added next thing and warning doesn't appear anymore. Is it correct way?
--- a/os/common/startup/ARMCMx/compilers/GCC/mk ...
After migration from older GCC to 10.2 linker produces warning regarding incorrect usage of -flto
I found that in ChibiOS it without value but should be with value.
I added next thing and warning doesn't appear anymore. Is it correct way?
--- a/os/common/startup/ARMCMx/compilers/GCC/mk ...
- Tue Jun 20, 2023 9:17 am
- Forum: Bug Reports
- Topic: STM32L496 (4A6) missing TIM16 info
- Replies: 1
- Views: 6731
STM32L496 (4A6) missing TIM16 info
Hi All,
I have found that it's impossible to use TIM16 without fix becuase of missing STM32_TIM16_CHANNELS def.
There is a simple patch:
diff --git a/os/hal/ports/STM32/STM32L4xx/stm32_registry.h b/os/hal/ports/STM32/STM32L4xx/stm32_registry.h
index fdec353fa..8a795ba00 100644 ...
I have found that it's impossible to use TIM16 without fix becuase of missing STM32_TIM16_CHANNELS def.
There is a simple patch:
diff --git a/os/hal/ports/STM32/STM32L4xx/stm32_registry.h b/os/hal/ports/STM32/STM32L4xx/stm32_registry.h
index fdec353fa..8a795ba00 100644 ...
- Fri Jun 10, 2022 3:05 pm
- Forum: Small Change Requests
- Topic: STM32F401CCU6 board
- Replies: 2
- Views: 33238
STM32F401CCU6 board
Hi All,
I started a small experimental project on this board: https://stm32-base.org/boards/STM32F401 ... -Mini-F401
By the way I extracted a demo fro this board in ChibiOS and committed to separate branch on github. https://github.com/tuxford/chibios_hw84 ... 48_21.11.x
I think it has sense to add it to your main stream.
I started a small experimental project on this board: https://stm32-base.org/boards/STM32F401 ... -Mini-F401
By the way I extracted a demo fro this board in ChibiOS and committed to separate branch on github. https://github.com/tuxford/chibios_hw84 ... 48_21.11.x
I think it has sense to add it to your main stream.
- Mon Apr 04, 2022 6:19 pm
- Forum: General Support
- Topic: Events limitations
- Replies: 7
- Views: 7896
Re: Events limitations
Hi Giovanni,
You are right!
I missed a case when one message was sent twice with different flags that were handled in wrong way.
I case EVENT_MASK it's good. I used it instead of lshift operation.
But I still have a question about chEvtWaitOne.
Does it wait one message and if other of the same id ...
You are right!
I missed a case when one message was sent twice with different flags that were handled in wrong way.
I case EVENT_MASK it's good. I used it instead of lshift operation.
But I still have a question about chEvtWaitOne.
Does it wait one message and if other of the same id ...
- Sun Apr 03, 2022 5:14 pm
- Forum: General Support
- Topic: Events limitations
- Replies: 7
- Views: 7896
Re: Events limitations
EVENTSOURCE_DECL(spindle_state_es);
EVENTSOURCE_DECL(spindle_es);
#define EVENT_STATE EVENT_MASK(0)
#define EVENT_TRIGGER_VALUE EVENT_MASK(1)
#define EVENT_ENC1HS_SLOW EVENT_MASK(2)
#define SUBEVENT_TICK EVENT_MASK(0)
#define SUBEVENT_ATTACH EVENT_MASK(1)
#define SUBEVENT_ATTACH_FAILED EVENT ...
- Sun Apr 03, 2022 3:51 pm
- Forum: General Support
- Topic: Events limitations
- Replies: 7
- Views: 7896
Re: Events limitations
I understand difference between events and flags. There no problems. Code is too long to show it.
I was investigating how broadcasting works but I haven't have a clear idea how it's better to find out where event gets lost internally.
I was investigating how broadcasting works but I haven't have a clear idea how it's better to find out where event gets lost internally.
- Sat Apr 02, 2022 1:16 pm
- Forum: General Support
- Topic: Events limitations
- Replies: 7
- Views: 7896
Events limitations
Hi,
I faced with a problem when I use events. I have declared 29 events using macro EVENTSOURCE_DECL. But after adding flag for event I found that chEvtBroadcastFlags doesn't send it or chEvtWaitOne(ALL_EVENTS) doesn't receive one exact event. Other important thing is that if I drop one evtTableHook ...
I faced with a problem when I use events. I have declared 29 events using macro EVENTSOURCE_DECL. But after adding flag for event I found that chEvtBroadcastFlags doesn't send it or chEvtWaitOne(ALL_EVENTS) doesn't receive one exact event. Other important thing is that if I drop one evtTableHook ...
- Tue Feb 15, 2022 8:01 am
- Forum: Bug Reports
- Topic: I2C fallback doesn't work after first failure
- Replies: 3
- Views: 6392
I2C fallback doesn't work after first failure
I2C driver stop working after first failed command. E.g.
uint8_t addr = 0xFF << 1;
i2cMasterReceiveTimeout(drv, addr, NULL, 0, TIME_S2I(2));
On oscilloscope i have next case. SCL is on low state and that's finish. No operations are allowed until restart of board.
tlv493d.png
I have added ...
uint8_t addr = 0xFF << 1;
i2cMasterReceiveTimeout(drv, addr, NULL, 0, TIME_S2I(2));
On oscilloscope i have next case. SCL is on low state and that's finish. No operations are allowed until restart of board.
tlv493d.png
I have added ...