Anonymous | Login | Signup for a new account | 2021-01-25 00:20 UTC | ![]() |
Main | My View | View Issues | Roadmap | Repositories |
View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
0000663 | Loader | Serial Monitor Comms | public | 2012-08-28 21:40 | 2012-08-29 02:16 | ||||||
Reporter | Fred | ||||||||||
Assigned To | sean94z | ||||||||||
Priority | immediate | Severity | feature | Reproducibility | N/A | ||||||
Status | assigned | Resolution | open | ||||||||
Platform | All | OS | All | OS Version | All | ||||||
Product Version | 0.1.0-SNAPSHOT | ||||||||||
Target Version | 0.1.0 | Fixed in Version | |||||||||
Summary | 0000663: Show all four SM version blocks in the UI | ||||||||||
Description | first one is used as date, so the hex should be displayed as hex to be correct for most versions, eg softwareID1 = 0x0723 ;Software revision (date) softwareID2 = 0x2004 ;Software revision (year) softwareID3 = 0x0202 ;Software revision (ver) softwareID4 = 0x1001 ;device ID (H256 for example) 7th month, 23rd day, 2004AD year, 2.2 version. | ||||||||||
Additional Information | Marked as immediate such that I can use this during my testing and SM dev. Should be a piece of cake anyway and won't slow loads more than a fraction of a second. | ||||||||||
Tags | No tags attached. | ||||||||||
Issue Type | New Feature | ||||||||||
Risk of Breakage | very low | ||||||||||
Attached Files | |||||||||||
![]() |
|
![]() sean94z (reporter) 2012-08-29 01:07 |
np, can you shoot me an s19 for testing with ? I'll see if I can get it knocked out tonight, I will be down for a day or two soon :) |
![]() sean94z (reporter) 2012-08-29 01:12 |
After parsing out the date, I should be able to verify that it's a valid time stamp and if not, display a warning.... What do you think? 7th month, 23rd day, 2004AD year, |
![]() Fred (administrator) 2012-08-29 01:23 |
Display as is, as hex digits, you never know what some arsehole might use them for ;-) Same dude may add a new call/field too, we'll see. what do you want an s19 for? |
![]() sean94z (reporter) 2012-08-29 01:29 edited on: 2012-08-29 01:41 |
Well that makes it easy. I have to ask though, what happened to that statement that you made some time ago? It sounds like someone else is working on it. http://forum.diyefi.org/viewtopic.php?f=8&t=1243 [^] |
![]() Fred (administrator) 2012-08-29 01:41 |
Get some sleep? :-/ |
![]() sean94z (reporter) 2012-08-29 01:43 |
Lol, I have been working so hard lately I could sleep for days. Therefor I shall stay up :) Almost done, just have to hope mrs and mother in-law doesn’t come back soonish. |
![]() sean94z (reporter) 2012-08-29 01:59 |
So this data will always precede the current S0 data? Maybe you can put a special string right before the actual data you want ?? FreeEMS0xFF ?? Example S19 built via binutils: S02B00006669726D776172652F46726565454D532D302E322E302D534E415053484F542D33332D6766333339FD S214E08800000000000000000100000002000000037D S214E08810000000040000000500000006000000075D S214E0882000000008000000090000000A0000000B3D S214E088300000000C0000000D0000000E0000000F1D S214E0884000000010000000110000001200000013F |
![]() Fred (administrator) 2012-08-29 02:09 |
I have no idea what you're smoking, but the S0 stuff and the "display sm version fields" issues are entirely and completely unrelated. |
![]() Fred (administrator) 2012-08-29 02:16 |
$B7 — Device_info B7/DC/IDID — Returns the constant $DC (Device C=12) and the 2-byte HCS12 device ID register. Please refer to selected device guides for device ID register contents. Turns out that this isn't (currently) possible. I'll likely fix it in future to return more than it currently does in a new call. Pull the device ID, though. |
Copyright © 2000 - 2011 MantisBT Group |