Home/Support/Support Forum/Values not being set at init when observed with Multilink
New and improved user forum site coming soon

Values not being set at init when observed with Multilink

0 votes
Is this ever experienced by anyone?

I'll simply initialize in main() at startup a uint8_t variable = 0. This value seems to like the value 221 a lot, but I'm not sure I can wrap my head around why that is. Stepping through it line for line, I've also tried an unsigned char type and it still sets it to 221. I am representing the value in the debugger as an unsigned char, decimal display. Not sure what's going on or why.

I did notice for these particular u8's, that the 3 of them had specified locations at 0x727,0x728,0x729, which doesn't make sense to me either (half the size at 1 nibble). Do these Freescale processors not take well to certain data types?

asked Jul 27, 2020 in DigiMesh Proprietary Mesh Networking by D2K New to the Community (16 points)

Please log in or register to answer this question.

1 Answer

0 votes
No not that I am aware of.
answered Jul 27, 2020 by mvut Veteran of the Digi Community (15,515 points)