<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: About MSCAN module on 56F82xx in Classic/Legacy CodeWarrior</title>
    <link>https://community.nxp.com/t5/Classic-Legacy-CodeWarrior/About-MSCAN-module-on-56F82xx/m-p/149318#M1964</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No reply?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 28 Mar 2012 16:15:36 GMT</pubDate>
    <dc:creator>emb_developer</dc:creator>
    <dc:date>2012-03-28T16:15:36Z</dc:date>
    <item>
      <title>About MSCAN module on 56F82xx</title>
      <link>https://community.nxp.com/t5/Classic-Legacy-CodeWarrior/About-MSCAN-module-on-56F82xx/m-p/149317#M1963</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I just wonder why sequential MSCAN registers increments &amp;nbsp;by one in the memory space. Since these DSCs are 16 bit, a register should occupy two bytes in memory. &amp;nbsp;I investigated both the datasheet and IO_map.h. In the IO_map.h they are defined as word. But in the datasheet it is word also but occupies only one byte of memory. What's wrong with it? If I define a struct aligned to CAN receive message buffer, is that correct?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;typedef struct{&lt;BR /&gt;UNSIGNED16 ident;&lt;BR /&gt;UNSIGNED16 extIdent;&lt;BR /&gt;UNSIGNED16 data[8];&lt;BR /&gt;UNSIGNED16 DLC :12; // big endian&lt;BR /&gt;UNSIGNED16 DLCrest :4;&lt;BR /&gt;}CANrxMsg_t;&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Mar 2012 14:00:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Classic-Legacy-CodeWarrior/About-MSCAN-module-on-56F82xx/m-p/149317#M1963</guid>
      <dc:creator>emb_developer</dc:creator>
      <dc:date>2012-03-27T14:00:14Z</dc:date>
    </item>
    <item>
      <title>Re: About MSCAN module on 56F82xx</title>
      <link>https://community.nxp.com/t5/Classic-Legacy-CodeWarrior/About-MSCAN-module-on-56F82xx/m-p/149318#M1964</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No reply?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Mar 2012 16:15:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Classic-Legacy-CodeWarrior/About-MSCAN-module-on-56F82xx/m-p/149318#M1964</guid>
      <dc:creator>emb_developer</dc:creator>
      <dc:date>2012-03-28T16:15:36Z</dc:date>
    </item>
    <item>
      <title>Re: About MSCAN module on 56F82xx</title>
      <link>https://community.nxp.com/t5/Classic-Legacy-CodeWarrior/About-MSCAN-module-on-56F82xx/m-p/149319#M1965</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No help...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Apr 2012 12:47:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Classic-Legacy-CodeWarrior/About-MSCAN-module-on-56F82xx/m-p/149319#M1965</guid>
      <dc:creator>emb_developer</dc:creator>
      <dc:date>2012-04-02T12:47:15Z</dc:date>
    </item>
    <item>
      <title>Re: About MSCAN module on 56F82xx</title>
      <link>https://community.nxp.com/t5/Classic-Legacy-CodeWarrior/About-MSCAN-module-on-56F82xx/m-p/149320#M1966</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is only about a month late, but I was just looking through the data sheet for the DSP56F800E core.&lt;/P&gt;&lt;P&gt;I am using an MC56F8037 part, but I think they both use the same core. Anyway, in the section of the core reference manual,&lt;/P&gt;&lt;P&gt;part 6.4 Byte and Word addresses, it says the 56F800E core supprts two methods of addressing - word and byte.&lt;/P&gt;&lt;P&gt;It says when Word addressing is used each unique adress corresponds to a word in memory, so you count up:&lt;/P&gt;&lt;P&gt;$4002 (15......0) etc&lt;/P&gt;&lt;P&gt;$4001 (15......0)&lt;/P&gt;&lt;P&gt;$4000 (15......0)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When Byte addressing is used you can access individual bytes, and it counts up like:&lt;/P&gt;&lt;P&gt;$4004 (7....0)(7....0) etc&lt;/P&gt;&lt;P&gt;$4002 (7....0)(7....0)&lt;/P&gt;&lt;P&gt;$4000 (7....0)(7....0)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope this helps!!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am also working on getting MSCAN up and running on my controller. I can get data out of it, but I have screwed up something in the way I am collecting data from buffers in my program to put in the CAN tx buffers, so my data is coming out in a mixed order - ie not the way it is being accessed out of the program buffer.&lt;/P&gt;&lt;P&gt;If you have any tips on CAN isr and sending approaches, I would be most grateful!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Laurence&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 May 2012 15:07:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Classic-Legacy-CodeWarrior/About-MSCAN-module-on-56F82xx/m-p/149320#M1966</guid>
      <dc:creator>Law</dc:creator>
      <dc:date>2012-05-03T15:07:00Z</dc:date>
    </item>
  </channel>
</rss>

