Part Number: F28M35H52C
Hello,
I'm implementing a client for F28M35 BOOT ROM using CAN interface. The client is running on a TIVA TM4C129.
As stated in the Concerto Technical Reference Manual (6.5.15.3.3 M-Boot ROM CAN Boot Mode Protocol),
1. LM_API_UPD_PING
This command is used to receive an acknowledge
command from the bootloader indicating that
communication has been established. This command has
no data. If the device is present it will respond with a
LM_API_UPD_PING back to the sender.
In my application running on a TM4C129 used as client for F28M35 BOOT ROM, I receive back an ACK packet instead of a PING. I also gave a look to file bl_can.c of TivaWare boot_loader folder and I found this code in UpdaterCAN function:
//
// This is a ping packet.
//
case LM_API_UPD_PING:
{
//
// This packet is ignored (other than generating an ACK).
//
break;
}
(I couldn't find the BOOT ROM source code for Concerto but I suppose it should be the same as TIVA), so this seems to confirm what happens in my setup.
Is the documentation wrong or am I missing something or doing something wrong in my client's code ?
Thanks
Fabio
