I can feel with you. My laptop just died also.
No booting, no bios. So bad.
Search found 121 matches
- Thu May 07, 2020 10:11 pm
- Forum: Development and Feedback
- Topic: [PROBLEM] Dead PC...
- Replies: 16
- Views: 8163
- Tue Mar 17, 2020 4:04 pm
- Forum: Bug Reports
- Topic: priority order violation Topic is solved
- Replies: 2
- Views: 9937
priority order violation Topic is solved
Hi, I just saw an issue with a "priority order violation" after an unlock. My code looks like: chSysLock(); chEvtBroadcastFlagsI(&menu_es, 0); chMtxUnlockAllS(); chSysUnlock(); Shouldn't the chMtxUnlockAllS() reschedule in any case? I was stepping with the debugger in a second thread w...
- Tue Mar 10, 2020 9:55 am
- Forum: STM32 Support
- Topic: ChibiOS crashes when my firmware is not at beginning of flash memory
- Replies: 32
- Views: 17229
Re: ChibiOS crashes when my firmware is not at beginning of flash memory
I successfully jump from HAL bootloader to ChibiOS main application.
Be sure that you will set VTOR, MSP etc. correctly AND jump before halInit and chInit etc.
Be sure that you will set VTOR, MSP etc. correctly AND jump before halInit and chInit etc.
- Mon Feb 03, 2020 7:26 am
- Forum: Bug Reports
- Topic: chVTIsSystemTimeWithin (chvt.h) return comment true->false with #1060 Topic is solved
- Replies: 1
- Views: 8171
chVTIsSystemTimeWithin (chvt.h) return comment true->false with #1060 Topic is solved
Hi,
with revert Bug#1060 the comment in chvt becomes wrong for chVTIsSystemTimeWithinX and chVTIsSystemTimeWithin.
It will return always false.
with revert Bug#1060 the comment in chvt becomes wrong for chVTIsSystemTimeWithinX and chVTIsSystemTimeWithin.
Code: Select all
* @note When start==end then the function returns always true because the
* whole time range is specified.
It will return always false.
- Fri Jan 31, 2020 11:29 am
- Forum: General Support
- Topic: sdcDisconnect wait forever
- Replies: 3
- Views: 5434
Re: sdcDisconnect wait forever
I should enable the CHIBIOS debug options...
The sdcDisconnect will stop, because it is not BKL_READY.
Before I make a sdcDisconnect I wait now for a sdcSync will return HAL_SUCCESS.
The sdcDisconnect will stop, because it is not BKL_READY.
Before I make a sdcDisconnect I wait now for a sdcSync will return HAL_SUCCESS.
- Fri Jan 31, 2020 10:23 am
- Forum: General Support
- Topic: sdcDisconnect wait forever
- Replies: 3
- Views: 5434
Re: sdcDisconnect wait forever
Hi Giovanni,
yes the card is any time in the slot.
It could be an hardware issue, because I can see this issue mainly, when the wifi-module, close to it, will create a connection, which could draw more current in that situation.
yes the card is any time in the slot.
It could be an hardware issue, because I can see this issue mainly, when the wifi-module, close to it, will create a connection, which could draw more current in that situation.
- Fri Jan 31, 2020 9:27 am
- Forum: General Support
- Topic: sdcDisconnect wait forever
- Replies: 3
- Views: 5434
sdcDisconnect wait forever
Hi, I'm trying to find an issue with my SD-card slot. Actually I trigger a manual disconnect from the sd-card. After some disconnects the driver will hang in a while loop: hal_sdc.c bool sdcDisconnect(SDCDriver *sdcp) { //...snip...// /* Waits for eventual pending operations completion.*/ if (_sdc_w...
- Thu Jan 23, 2020 7:43 pm
- Forum: General Support
- Topic: Zip compression on a micro
- Replies: 7
- Views: 4855
Re: Zip compression on a micro
Do you need zip or something to decompress? LZ4?
https://community.arm.com/developer/ip- ... -and-later
https://community.arm.com/developer/ip- ... -and-later
- Thu Jan 23, 2020 12:27 pm
- Forum: ChibiOS/RT
- Topic: HardFault on chRescheduleAhead
- Replies: 4
- Views: 3050
Re: HardFault on chRescheduleAhead
Thanks for your advice.
I will check some options.
I will check some options.
- Thu Jan 23, 2020 11:28 am
- Forum: ChibiOS/RT
- Topic: HardFault on chRescheduleAhead
- Replies: 4
- Views: 3050
Re: HardFault on chRescheduleAhead
Yes, I will try to check this with debug options again.
Unfortunately this occure only once for now, just after a reboot.
How much space should the main stack have? I can see it will go down to 100bytes free.
Unfortunately this occure only once for now, just after a reboot.
How much space should the main stack have? I can see it will go down to 100bytes free.