
and will not impact the ability to build or debug the project .
To reproduce:
* File, New, CrossCore Project. Select 609 and silicon rev any. Next.
* Deselect MCAPI, Startup/LDF and pin muxing. Select RTOS.
* Everything else default.
* In Project Explorer, click on any of the files in system/uC-
LIB/Source.
Workaround: None
Boot fails when Start
Address (-p) with
Initialization File (- init) due
to incorrect NEXT PTR
argument in initialization
FIRST block
Do not use "Start address (-p <alternate- address>)" when building a
ldr file with "Boot format Intel HEX (-f hex)" and "Initialization file (-
init <init.dxe>)" at this release. Either:
1) Build the ldr file with "Boot format ASCII (-f ASCII)" with the
default start address and specify the offset when programming the
memory using the Device Programmer:
cldp -offset <alternate-address> ...
or
2) Build the ldr file with "Boot format HEX (-f hex)" and add "-kp
<alternate-address>" in Additional Options instead of "Start address
(-p <alternate-address>)".
String comparison functions
fail on signed values
String comparison functions (strcmp, strncmp and memcp) can
return the wrong result if the parameter strings contain non-ASCII
characters.
BF60x def headers have
incorrect casts for some
registers in the EMAC
module
In the "cdef" header files for BF60x processors (which contain C
register and bitfield definitions), a number of macros for memory-
mapped registers in the EMAC module are incorrect.The macros
should use (volatile uint32_t *) instead of (void * volatile *). The list
of incorrect macros is given below, followed by correct definitions:
pREG_EMAC0_DMA_RXDSC_ADDR
pREG_EMAC0_DMA_TXDSC_ADDR
pREG_EMAC0_DMA_TXDSC_CUR
pREG_EMAC0_DMA_RXDSC_CUR
pREG_EMAC0_DMA_TXBUF_CUR
pREG_EMAC0_DMA_RXBUF_CUR
pREG_EMAC1_DMA_RXDSC_ADDR
pREG_EMAC1_DMA_TXDSC_ADDR
pREG_EMAC1_DMA_TXDSC_CUR
pREG_EMAC1_DMA_RXDSC_CUR
pREG_EMAC1_DMA_TXBUF_CUR
pREG_EMAC1_DMA_RXBUF_CUR
Kommentare zu diesen Handbüchern