We're trying to track down occasional SD card read/write errors...
Latest evidence suggests a hardware problem. I'll update if a ChibiOS bug is found.
Search found 10 matches
- Mon Apr 14, 2014 3:49 pm
- Forum: Bug Reports
- Topic: [possible BUG] Bug 458 might not be fixed completely
- Replies: 40
- Views: 35537
- Tue Apr 08, 2014 4:26 pm
- Forum: Bug Reports
- Topic: [possible BUG] Bug 458 might not be fixed completely
- Replies: 40
- Views: 35537
Re: [possible BUG] Bug 458 might not be fixed completely
Thanks.
I hope he's right...
I hope he's right...
- Tue Apr 08, 2014 1:12 pm
- Forum: Bug Reports
- Topic: [possible BUG] Bug 458 might not be fixed completely
- Replies: 40
- Views: 35537
[possible BUG] Bug 458 might not be fixed completely
Hi,
I was looking over the changes in ChibiOS and found the following.
m
This produces the diff:
m
The same constellation of DCTL, sdc_lld_prepare.. and sdc_lld_wait_transaction_end is present in
sdc_lld_write_aligned() and sdc_lld_read_aligned() but the bugfix only changed one of them ...
I was looking over the changes in ChibiOS and found the following.
m
This produces the diff:
m
The same constellation of DCTL, sdc_lld_prepare.. and sdc_lld_wait_transaction_end is present in
sdc_lld_write_aligned() and sdc_lld_read_aligned() but the bugfix only changed one of them ...
- Mon Nov 25, 2013 10:06 pm
- Forum: Development and Feedback
- Topic: BUG: chThdSleepMilliseconds() sleeps 1 clock cycle too short
- Replies: 4
- Views: 3783
Re: BUG: chThdSleepMilliseconds() sleeps 1 clock cycle too s
Thanks, I found out the correct way to do things immediately after my post so I edited the post to remove the second question.
But please clarify the docu!
I introduced:
// Do not use chThdSleepMilliseconds()/Microseconds() because these functions
// will in fact sleep at least 1 clock cycle ...
But please clarify the docu!
I introduced:
// Do not use chThdSleepMilliseconds()/Microseconds() because these functions
// will in fact sleep at least 1 clock cycle ...
- Mon Nov 25, 2013 9:37 pm
- Forum: Development and Feedback
- Topic: BUG: chThdSleepMilliseconds() sleeps 1 clock cycle too short
- Replies: 4
- Views: 3783
Re: BUG: chThdSleepMilliseconds() sleeps 1 clock cycle too s
Thanks for your quick reply.
The documentation says: "The specified time is rounded up to a value allowed by the real system tick clock."
To me, this means what I just described above: That the delay can be longer but not shorter.
This is also what just about everybody will expect. An API like ...
The documentation says: "The specified time is rounded up to a value allowed by the real system tick clock."
To me, this means what I just described above: That the delay can be longer but not shorter.
This is also what just about everybody will expect. An API like ...
- Mon Nov 25, 2013 8:05 pm
- Forum: Development and Feedback
- Topic: BUG: chThdSleepMilliseconds() sleeps 1 clock cycle too short
- Replies: 4
- Views: 3783
BUG: chThdSleepMilliseconds() sleeps 1 clock cycle too short
Hi,
as I understand, both chThdSleepMilliseconds(x) and ..Microseconds(x) are supposed to sleep AT LEAST the time x.
The actual time should be between x and x+"1 clock cycle" (which might typically be 1ms).
However, what we find when measuring with an oscilloscope is that chThdSleepMilliseconds ...
as I understand, both chThdSleepMilliseconds(x) and ..Microseconds(x) are supposed to sleep AT LEAST the time x.
The actual time should be between x and x+"1 clock cycle" (which might typically be 1ms).
However, what we find when measuring with an oscilloscope is that chThdSleepMilliseconds ...
- Mon Nov 25, 2013 8:01 pm
- Forum: Development and Feedback
- Topic: [DONE] CFGR in STM32F4xx/hal_lld.c and maybe other STM32
- Replies: 3
- Views: 3307
Re: [DONE] CFGR in STM32F4xx/hal_lld.c and maybe other STM32
Thanks.
Just posted another bug...
Just posted another bug...
- Thu Sep 12, 2013 7:05 pm
- Forum: Development and Feedback
- Topic: [DONE] CFGR in STM32F4xx/hal_lld.c and maybe other STM32
- Replies: 3
- Views: 3307
[DONE] CFGR in STM32F4xx/hal_lld.c and maybe other STM32
Hi,
Looking at os/hal/platforms/STM32F4xx/hal_lld.c, around line 209:
/* Other clock-related settings (dividers, MCO etc).*/
RCC->CFGR |= STM32_MCO2PRE | STM32_MCO2SEL | STM32_MCO1PRE | STM32_MCO1SEL |
STM32_RTCPRE | STM32_PPRE2 | STM32_PPRE1 | STM32_HPRE;
I'm wondering why ORing is used ...
Looking at os/hal/platforms/STM32F4xx/hal_lld.c, around line 209:
/* Other clock-related settings (dividers, MCO etc).*/
RCC->CFGR |= STM32_MCO2PRE | STM32_MCO2SEL | STM32_MCO1PRE | STM32_MCO1SEL |
STM32_RTCPRE | STM32_PPRE2 | STM32_PPRE1 | STM32_HPRE;
I'm wondering why ORing is used ...
- Fri Aug 30, 2013 5:26 pm
- Forum: Development and Feedback
- Topic: [DONE] Bug in STM32F407xG.ld and possibly others
- Replies: 10
- Views: 8399
Re: [TODO] Bug in STM32F407xG.ld and possibly others
Hi,
as a side note, it might be a good idea to split the linker scripts:
You need STM32F207xY.ld (several of them). Each of them should contain:
__main_stack_size__ = 4096;
__process_stack_size__ = 2048;
MEMORY
{
flash : org = 0x08000000, len = 1M
ram : org = 0x20000000, len = 112k ...
as a side note, it might be a good idea to split the linker scripts:
You need STM32F207xY.ld (several of them). Each of them should contain:
__main_stack_size__ = 4096;
__process_stack_size__ = 2048;
MEMORY
{
flash : org = 0x08000000, len = 1M
ram : org = 0x20000000, len = 112k ...
- Mon Aug 19, 2013 4:35 pm
- Forum: Development and Feedback
- Topic: [DONE] Bug in STM32F407xG.ld and possibly others
- Replies: 10
- Views: 8399
[DONE] Bug in STM32F407xG.ld and possibly others
Hi,
there's a bug in STM32F407xG.ld (and possible other linker scipts)
which prevents static variables to be initialized in certain cases:
In STM32F407xG.ld, we have:
...
_etext = .;
_textdata = _etext;
...
Now, _etext can be an odd address e.g. if the last ...
there's a bug in STM32F407xG.ld (and possible other linker scipts)
which prevents static variables to be initialized in certain cases:
In STM32F407xG.ld, we have:
...
_etext = .;
_textdata = _etext;
...
Now, _etext can be an odd address e.g. if the last ...