CAN ROM routine response question

[gregwilson-lind]

I've run into a confusion when trying to implement a bootloader for CAN on an LPC1517.  I'm trying to allow the NMT to access the Device Name OD1008. When the NMT accesses OD1008 using a expedited SDO (OD1008 is a visible string, should probably be accessed by a segmented SDO), the ROM CAN api code is returning a message with the first byte as 0xEB. This means that the scs (top 3 bits of 1st byte) of the returned message are 0x7, which I can't find defined anywhere, valid values are from 0-6. I'm wondering what the 0x7 is supposed to mean.

Does anybody have an idea as to what's going on here?

[Carlos_Mendoza]

Hi Greg,

Have you tried using the LPC15xx CAN Open example that comes with the LPCOpen package for the LPCXpresso LPC1549 board  to see if the same behavior is present? This example demonstrates sending and receiving of data using CAN open stack (in ROM). It will transmit the 'TEST' packet, wait for 15 bit time periods and re-transmit the 'TEST' packet.  This will continue until a node responds with a valid ACK.

LPCOpen Software for LPC15XX|NXP 

Let me know the result!

Best Regards,
Carlos Mendoza
Technical Support Engineer