Hello,
I am looking to migrate from the MOD5282 to a newer platform that is pin-compatible with it.
On the MOD5282, other than power and ground, I am currently using the following pins on J1:
- 6: Chip Select 2
- 7: Chip Select 3
- 8: Output Enable
- 11: Transfer-in-progress
And the following pins on J2:
- 3, 4: UART0 RX, TX
- 21, 22: UART1 RX, TX
- 39, 42: I2C Data, Clk
- 41, 44: CAN RX, TX
The CAN function is the only one which is critical for my application, so I require a replacement for MOD5282 which has the same form factor for the headers, and that pins 41 and 44 on header J2 are dedicated for CAN. I am flexible on the functions of the other pins in the replacement (other than power and ground, of course).
I notice that MOD5441X may be a good replacement. I have some questions:
1. Is that correct? Does MOD5441X satisfy my requirement for pin-compatibility with MOD5282?
2. Are there other options which also satisfy this requirement? https://www.netburner.com/products/syst ... s/#compare
3. If I decide to migrate to MOD5441X, what changes would need to be made in software? I would appreciate some information similar to this Migration Guide https://www.netburner.com/learn/upgradi ... modm7ae70/ but for MOD5441X
Please feel free to let me know.
Thanks.
Migrating from EOL MOD5282 to a replacement supporting CAN
Re: Migrating from EOL MOD5282 to a replacement supporting CAN
Hello AlokD,
1. Yes, those pin functions all match. Mechanically, the headers, mounting holes and Ethernet jacks are the same across the MODxxxx product line. The length of the MOD5441x is about 0.25 inches longer than the MOD5282. This is the dimension opposite the RJ-45 jack. So it does not affect mechanical positions of any connectors or mounting.
2. The other option would be the MODM7AE70. You have referenced the link to the information on compatibility. Since the MOD54415 uses a ColdFire processor, it is more similar to the MOD5282, but either can be used. The MODM7AE70 uses an ARM processor and the peripherals are slightly different from a hardware perspective.
3. Minor changes in software between the MOD5282 and MOD54415, depending on the software tools revision you are using. The MOD5282 is 20 years old, so if you have a tools release that old it might be more effort than if you are using the latest 2.9.7 release. It also depends on how the code was written. So far most 5282 ports have taken 1-2 days. But like I said, longer depending on how the code was written, and whether any 5282 specific registers were used that need to be converted to 54415.
From a tools perspective, if you were using anything earlier than 2.8, you should port to 2.9.7 first. You then have the option to use the 3.x tools if you wish, which add a bunch of IoT, security and configuration capabilities. Here are the docs: https://www.netburner.com/NBDocs/Develo ... index.html. The Configuration and Migration sections would be very helpful.
Please let me know if you have any additional questions.
1. Yes, those pin functions all match. Mechanically, the headers, mounting holes and Ethernet jacks are the same across the MODxxxx product line. The length of the MOD5441x is about 0.25 inches longer than the MOD5282. This is the dimension opposite the RJ-45 jack. So it does not affect mechanical positions of any connectors or mounting.
2. The other option would be the MODM7AE70. You have referenced the link to the information on compatibility. Since the MOD54415 uses a ColdFire processor, it is more similar to the MOD5282, but either can be used. The MODM7AE70 uses an ARM processor and the peripherals are slightly different from a hardware perspective.
3. Minor changes in software between the MOD5282 and MOD54415, depending on the software tools revision you are using. The MOD5282 is 20 years old, so if you have a tools release that old it might be more effort than if you are using the latest 2.9.7 release. It also depends on how the code was written. So far most 5282 ports have taken 1-2 days. But like I said, longer depending on how the code was written, and whether any 5282 specific registers were used that need to be converted to 54415.
From a tools perspective, if you were using anything earlier than 2.8, you should port to 2.9.7 first. You then have the option to use the 3.x tools if you wish, which add a bunch of IoT, security and configuration capabilities. Here are the docs: https://www.netburner.com/NBDocs/Develo ... index.html. The Configuration and Migration sections would be very helpful.
Please let me know if you have any additional questions.