Windows error 0x00000184, 388

Detailed Error Information

HRESULT analysis[1]

This is probably not the correct interpretation of this error. The Win32 error above is more likely to indicate the actual problem.
FlagsSeveritySuccess

This code indicates success, rather than an error. This may not be the correct interpretation of this code, or possibly the program is handling errors incorrectly.

Reserved (R)false
OriginMicrosoft
NTSTATUSfalse
Reserved (X)false
FacilityCode0 (0x000)
NameFACILITY_NULL[1][2]
DescriptionThe default facility code.[1][2]
Error Code388 (0x0184)

Possible solutions

2

Can't debug after using SysTick_Config

debugging
embedded
inline
stm32

I have a strong feeling that the entry point isn't specified correctly in the compiler options or linker script...

And whatever code comes first at link time in the ".text" section, it gets to have the entry point.

The entry point, however, should point to a special "init" function that would set up the stack, initialize the ".bss" section (and maybe some other sections as well), initialize any hardware that's necessary for basic operation (e.g. the interrupt controller and maybe some system timer) and any remaining portions of the and standard libraries before actually transferring control to main().

I'm not familiar with the tools and your hardware, so I can't say exactly what that special "init" function is, but that's pretty much the problem. It's not being pointed to by the entry point of the compiled program. NVIC_SetPriority() doesn't make any sense there.

answered on Stack Overflow Jul 5, 2012 by Alexey Frunze

Comments

Leave a comment

(plain text only)

Sources

  1. https://msdn.microsoft.com/en-us/library/cc231198.aspx
  2. winerror.h from Windows SDK 10.0.14393.0

User contributions licensed under CC BY-SA 3.0