Search Results
Search results 1-19 of 19.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
VAR_ALLOW_BMA_EMULATION is on and has been - hence i said I have seen and understood the massive difference in update rates for this mode of operation being limited to 5Hz but sample rate is no issue for this this is what happens when i try and use this "tick" is added as a watch, set to refresh at 1Hz and it does indeed update in the watch window at 1Hz when then try to graph "tick" then you just spit out a bunch of error messages in the console which contradicts what the manual / you say
-
you can't graph watched variables when using the emulated background JTAG refreshing [ Cortex A5D27 doesn't support high speed live watches according to ozone so is starting and stopping the MPU to read the values ] they do happily slowly update which is fine given you only get 5Hz updating but you can't graph the vatiables
-
given you can refresh watched data at up to a few Hz in the background on MPUs that don't support the full high speed sampling mechanism over JTAG, why does the Timeline / data sampling? using J-Trace with Cortex A5D27 which doesn't support the full high speed background refresh this appears in the console Hardware setup does not support data sampling. Current setup does not support background memory access mode Error (84): Failed to start high speed sampling (HSS). i don't see why the mechanism…
-
it's compiled under IAR this is a dump out of that union + another one using the iar ielfdumper tool 0x1'a743: | + union_type (82) | | sibling 0x1'a7d1 | | name UnControlReg | | byte_size 0x4 0x1'a756: | | member (86) | | type 0x1'a76c | | accessibility public | | data_member_location [plus_uconst 0] 0x1'a75f: | | member (49) | | type 0x1'a9a5 | | accessibility public | | name u32 | | data_member_location [plus_uconst 0] 0x1'a76c: | | + structure_type (87) | | | sibling 0x1'a7d0 | | | byte_size …
-
it answers the question , however it doesn't mean it is an entirely sensible philosophy its not uncommon to have different elf files for the same project that you would want to switch between without the rest of the environment changing as it is still the same "thing" just different version of code given it takes a split second to delete watches and significantly longer to add them back in I would much rather you didnt try and be clever and guess what the user is trying to do by changing the obj…
-
no typedef union { struct { uint32_t SldEn : 1; uint32_t TecEn : 1; uint32_t IntegrationCap : 1; uint32_t : 1; uint32_t SaveCal : 1; uint32_t LoadCal : 1; uint32_t LoadCalToSystem: 1; uint32_t RebootFpga : 1; uint32_t StopAnMux : 8; uint32_t EraseFgpaFirmware1 : 8; uint32_t EraseFgpaFirmware2 : 8; }; uint32_t U32; } UnControlReg; you can see in the picture the bottom 2 bits are set in the U32 but you dont display any of the struct values
-
[SOLVED] ability to set refresh rate / display format on multiple watches
AndyR - - Ozone related
Postin the watched data window you cannot select multiple items with shift / control and apply the auto refresh time ( 1Hz, 10 Hz etc ) to the items you have selected
-
[SOLVED] ability to set refresh rate / display format on multiple watches
AndyR - - Ozone related
Postwhy can you select multiple things and apply the refresh rate ditto hex/dec view : yes i know you can apply to all but that is not overly helpful either
-
union with struct overlaying with U32 & array of 2 U16 U32 & 2 U16s show ok struct doesn't but all show as the same address [ as you would expect ] typedef union { struct { uint32_t PowerEnable : 1; uint32_t Startup : 1; uint32_t Fault : 1; uint32_t HwFault : 1; uint32_t Present : 1; uint32_t xExpanderPresent : 1; uint32_t xExpanderOk: 1; uint32_t : 1; uint32_t xChargerPresent : 1; uint32_t xChargerOk : 1; uint32_t SmartBattPresent : 1; uint32_t SmartBattOk : 1; uint32_t : 4; uint32_t HwFaultSha…
-
is there any way to get slower sample rates than 100Hz for the data sampling / graphing? quite a lot of things I do run for a long time but dont notionally change very quickly eg a battery discharging over hours so having samples at 100Hz ( minimum rate ) leads to an awful lot of data that is pointlessly the same. 1Hz or even 0.1 Hz would be more than sufficient for a lot of things, especially when they are floats to inherently float around with noise on them that change detection would always t…