cypherbridge comments

Results 6 comments of


                                            cypherbridge

Whether threadx supports arm64 and x86-64

Hi ThreadX is supported on 64 bit ARM for sure

Why ThreadX entry function use `ULONG` as entry input instead of a `void *`?

Hi we run across this often. The purpose of the formal parameter is to pass either a start code scalar integer, or alternatively an opaque pointer to a context structure....

Why ThreadX entry function use `ULONG` as entry input instead of a `void *`?

C99 defines uintptr_t is defined in such a way to transparently convert between a pointer and and scalar. With the benefit of cross-platform code, 32bit 64 bit, whatever. Its true...

fx_media_opened_file_count becomes -1 (0xFFFF FFFF) which in turn sends fx_file_open and other functions into endless loop

Patch this with conditional test if (media_ptr -> fx_media_opened_file_count > 0) { media_ptr -> fx_media_opened_file_count--; }

fx_media_opened_file_count becomes -1 (0xFFFF FFFF) which in turn sends fx_file_open and other functions into endless loop

The top of fx_file_close() checks for a validated file handle file_ptr -> fx_file_id != FX_FILE_ID then when its done closing invalidates it file_ptr -> fx_file_id = FX_FILE_CLOSED_ID; By inspection it...

The interrupt vector table offset register should not be set.

not sure if this is a bug, feature, or preference my experience is VTOR set here is not a problem