Search Results

why is there still no windows Dark theme option? it's really horrible moving back from all the dark editors to a glaring white, in your face white windows. i alwasy run with the windows Dark mode as well so you aren't even honouring the same thing as you do with Linux / OsX still

well just download it, find the instance of the structure and just change the U32 / memory fundamental value . that is all you need to show the issue as "Registers" is a global static variable with the union structs inside it

why does ozone not report when newer versions are available and support the really not difficult to implement auto updating ?

how do I know what boards you have ? this elf file is for a samd20J17 it won't run on any hardware you have but you can find the "Registers" global object to find a bunch of examples of those structures

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 …

sorry I read it as is it fixed in latest version as you normally put , but yes the point is its not fixed

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…

why do the watches clear whe you open a new .elf / c.out etc? that I think is more likely the way i am loosing them

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

3.26c

3.26c

in 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

why 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…

am i missing something or is there no way for the list of watches to be remembered with the project file? it's a PITA if you have a lot of watches setup and then you close the machine, ozone crashes or you restart it , re-open the project and all the watches are gone

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…