Info on arm cortex-m debug techniques - Page 1
Forum section: electronics / general

author: mubes
author_rank: Regular Contributor
timestamp: July 28, 2017, 08:11:31 pm
content: Folks,A bit of shameless self-promotion. I started writing up some material on SemiHosting, SWO and associated subjects, specifically focussed on CORTEX-M. There's no commercial angle to this, it's just done the hope that it's useful and in the spirit of giving something back. You can find ithttp://shadetail.com/.Comments gratefully accepted.Dave

author: stmdude
author_rank: Frequent Contributor
timestamp: August 09, 2017, 06:40:43 am
content: Pretty good overview. What I would have added is a performance comparison between UART/Semihosting/SWO to show how much faster/slower they are compared to each other. (In my experience, Semihosting is way too slow to be useful)If you want some material for another series, I would recommend writing a bit about how to write gdb "scripts" to help you debug (there's precious little information/examples out there) various hardware blocks.For example, a simple gdb "macro" that will output (and make human-readable) the state of the STMs RCC registers.

author: r0d3z1
author_rank: Regular Contributor
timestamp: April 10, 2019, 02:25:01 pm
content: the ARM debug features available on common MCU are commonly misunderstood and understimated. Thank you for your blog articles.

author: capt bullshot
author_rank: Super Contributor
timestamp: April 10, 2019, 03:42:05 pm
content: Just read the first post as you suggested to do.Nice write up, though that method was known to me in general.What I'm missing: Add a link on the bottom of each post to the next (and maybe previous) in the series. Otherwise the typical blog structure (just a wild guess: Wordpress) makes it rather difficult for me to follow the series of posts.

author: legacy
author_rank: Super Contributor
timestamp: April 10, 2019, 11:54:33 pm
content: Quote from: mubes on July 28, 2017, 08:11:31 pmUsually, this assumption is weak with open source.

author: legacy
author_rank: Super Contributor
timestamp: April 11, 2019, 12:06:07 am
content: QuoteThis is a good trick to fool the GDPR, which is not applicable to UK, anyway.Very smart!

author: gmb42
author_rank: Frequent Contributor
timestamp: April 11, 2019, 11:07:32 am
content: Quote from: legacy on April 11, 2019, 12:06:07 amOh really? TheData Protection Act 2018is the UK transcription of the EU GDPR into UK law (with other stuff added as well).

author: legacy
author_rank: Super Contributor
timestamp: April 11, 2019, 11:23:58 am
content: Quote from: gmb42 on April 11, 2019, 11:07:32 amso that trick is no good.

author: 2N3055
author_rank: Super Contributor
timestamp: April 11, 2019, 11:59:29 am
content: Quote from: legacy on April 11, 2019, 12:06:07 amGDPR is applicable to whole world. If you have EU customers you have to conform to it..

author: legacy
author_rank: Super Contributor
timestamp: April 11, 2019, 12:22:23 pm
content: Quote from: 2N3055 on April 11, 2019, 11:59:29 amI have opened awebsiterecently, and comments on the MessageWall (sort of feedbacks from visitors) are telling me that the most guys who are not located in the European Area, do not think so, but rather they find "irritating" that they have to accept cookies and privacy-agree-on-something for accessing a website.Recent statistics report that the 90% of disagreement (on about ~2K visitors) comes from outside the Europe area.

author: 2N3055
author_rank: Super Contributor
timestamp: April 11, 2019, 12:41:23 pm
content: Quote from: legacy on April 11, 2019, 12:22:23 pmWell in theory it goes like this: Anybody anywhere in the world must protect personal data of EU citizens. In theory, if you could know if somebody is not from EU you don't have to comply with GDPR for them. But you carry the burden to make sure you do it for EU citizens.And despite all the complaining they should be happy that you care for their privacy and do not misuse their data.People are funny.

author: SiliconWizard
author_rank: Super Contributor
timestamp: April 11, 2019, 02:22:51 pm
content: I admit this point is funny. There is a lot of EU crap, but the GPDR is not one (even though it's probably still way too permissive when it comes to personal data).Regarding cookies and such, all it does is warn people (and give them the opportunity to decline) instead of storing them behind their back. What's the problem? Are people annoyed we ask them for permission?Reminds me of how many people reacted to Windows UAC, which was actually a gigantic progress for security. Lazyness.Regarding locating users, it's never 100% foolproof depending on their network, so relying on that to decide whether they are or are not EU citizens is way slippery and a potential way to infringe on the GPDR. Many or most businesses will not even bother.

author: 2N3055
author_rank: Super Contributor
timestamp: April 11, 2019, 03:07:39 pm
content: Quote from: SiliconWizard on April 11, 2019, 02:22:51 pmThat is why said in theory. In practice, you just apply it to all.

author: legacy
author_rank: Super Contributor
timestamp: April 11, 2019, 03:17:27 pm
content: Quote from: SiliconWizard on April 11, 2019, 02:22:51 pmbut to be truly 100% compliant, you also have to tell them- what exactly is stored- where it is stored- how long will it be stored- a person to be called for more information and/or for asking personal data removedDTB is a no-profit not commercial website, and a lawyer suggested us to writethispage (don't worry, it's a php that only loads a text file).so, I assume a true GDPR agreement should look this way, with points and a name/email/contact to someone who cares. In our case .. it's me (and I am not the web admin).Someone commented "too much semi-legalese", which means "not clear, and it sounds too much lawyer's stuff", well ...Quote from: SiliconWizard on April 11, 2019, 02:22:51 pmprecisely what we found in our comments on MessageWalland I do find it a bit "funny"Quote from: SiliconWizard on April 11, 2019, 02:22:51 pmA lot of websites, including Amazon and eBay, use the "whois" service to geo-locate users because this makes sense for choosing the correct language.e.g.if the incoming IP is located in Italy, then the website chooses language=Italianif the incoming IP is located in UK, then website chooses language=Englishetc ...(if the incoming IP is located ... try to access those websites from a Proxy located somewhere else, and see how the website reacts about the default-language)Amazon has an internal statistical engine that also tries to understand the psychology of users, e.g. which color is the best option regarding users of a specific area comparing the color of the button with the number of click on it and purchases ...I have never read it, neither clicked on "I do understand and I agree with this", I know it because there is a friend who works for Amazon and she told me it.In theory, a website should ask for the permission, even for checking the correct language(p.s. about permissions ... in theory,Giano(it's our defensive system) is violating the GDPR when someone doesn't agree with the site agreement because the firewall always logs and checks the IP's localization, banning the visitor if the IP comes from a VPN, Proxy, or public area ... which is exactly from where spamming-bots usually come)

author: legacy
author_rank: Super Contributor
timestamp: April 11, 2019, 03:27:43 pm
content: Quote from: mubes on July 28, 2017, 08:11:31 pmI do like the "form" you are presenting your articles.It's good and easy to read even on a smartphone!

author: 2N3055
author_rank: Super Contributor
timestamp: April 11, 2019, 03:49:12 pm
content: Thing is, it is NOT that restrictive but is also not that simple.GDPR is about personal data. IP address on a transient server is P.D.. Even cookie is not a personal data per se.You have to collect identifiable user data that will reveal to you who is user.So simple site with cookies is not a problem. Having personal user accounts with a real name of the user is.If you are not registering users, and only have cookies and IP logs AND you don't give that data for third parties for processing, pretty much a statement on site that explains what you do is good enough.There is a lot of paranoia about the GDPR. There are many categories of web sites and businesses that are exempt because they don't do and significant data processing per GDPR.

author: mubes
author_rank: Regular Contributor
timestamp: April 12, 2019, 06:48:37 pm
content: Well, we seem to have diverted into ahttp://bikeshed.com/discussion. There is nothing GDPR-affect{ing|ed} stored by that website. There's an EU directive (2002/58/EC IIRC) requiring your users to give 'Informed Consent' that you are storing information on their computer, but that's about it. The site could be improved a bit to do the job with a pop-up (there are WordPress plugins for that nowadays) but the only reason for having tracking on there at all is to see if anyone is interested in the stuff....no one is being sold for medical research, or any other reason.The site was specifically set up to be easy to read and not get in your way with banggood-style adverts. I like sites with good meaty content and I was just trying to contribute to the corpus of knowledge. I take on board the point about ease of navigation though, I'll lift the hood to see if there's anything that can be done on that.Reading through it (with a bit of time-distance now) there is quite a lot of useful material in there, especially when you get up to the more sophisticated tools like kcachegrind to surf around the execution history of your code. The material never really got good traction though...I don't know if that's because it was too specialised, to difficult to find or just simply because the audience is too small. When I started writing I did consider taking it, and other material expanding on it, and forming it into a into a book incorporating, for example, more material showing how to understand and debug hard realtime systems. (Likehttp://shadetail.com/blog/vga-video-out-on-bluepill/.... I don't know of any other practical examples showing you how to get realtime CPU loading output on your scope!)... but given the limited resonance it's had so far I'm not sure there would be too much point - in this 30 second attention span world folks don't seem too interested in learning what'sreallygoing on, and would rather gawp at the shiny.Anyway, pleased its tickled someone's cranium. Every now and again I throw something else up there. Next sizeable thing will probably be an open sourced MIMXRT1021 board, running NuttX in preparation forwww.nuttx2019.org.RegardsDAVE

author: wrynczuk
author_rank: Newbie
timestamp: April 15, 2019, 07:42:29 am
content: I like the site and already bookmarked it. I think I will give a try to the BluePill which seems just cool.Anyway I encourage you also to visiting my placehttps://vcdmaker.org. It's open and free software facilitating text log analysis. No matter the format it is created in. The tool was created as a mean to simplify systems analysis and debugging. Another tool to your library.

author: ali_asadzadeh
author_rank: Super Contributor
timestamp: April 15, 2019, 11:09:44 am
content: Thanks for sharing

author: NorthGuy
author_rank: Super Contributor
timestamp: April 15, 2019, 02:47:59 pm
content: Quote from: SiliconWizard on April 11, 2019, 02:22:51 pmI am. I come to a Website and they cover the third of the screen with their "cookies" statements and refuse to remove the banner unless I agree to their policies (which I most likely don't have time to read). I can tolerate when DigiKey, or some other important site, do this. But for most others I simply leave.If I enabled cookies, this means that I'm Ok with cookies. No need to ask. If I don't like any cookies, I can delete them - they're not on the server, but on my own browser.

author: agehall
author_rank: Frequent Contributor
timestamp: April 15, 2019, 02:56:10 pm
content: Quote from: NorthGuy on April 15, 2019, 02:47:59 pmI couldn't have put it better myself. All those cookie warnings are just insane and I find them very annoying. There are better ways to accomplish privacy protection that would not be intrusive to the consumer.

author: legacy
author_rank: Super Contributor
timestamp: April 15, 2019, 03:23:21 pm
content: Quote from: agehall on April 15, 2019, 02:56:10 pmlike the solution used on DTB? We are not using any popup or similar, the first time the visitor sees the page there is a little box informing about the GDPR &C. Do you think it's nice? OK, lets' talk about results ... with this solution, on 2944 visitors only 16 have clicked on "yes, I understand and agree"only 16/2944it means we cannot process any statistical information on them, neither which page they click on mostly, nor which is the resolution of their screen (which is useful to understand if we'd better change the template for something that better suits for smartphones and tablets)Really guys, I am so depressed by this experience that I am tempted to shut down the server.

author: legacy
author_rank: Super Contributor
timestamp: April 15, 2019, 03:29:50 pm
content: Quote from: NorthGuy on April 15, 2019, 02:47:59 pmThat is what makes everything confused: someone calls them "cookies", and it's not what "cookies" means because data are NOT on the browser, but rather on the server.It's a sneaky trick, I know, but a lot of websites do it, and it's even more depressing for those who respect the rules

author: agehall
author_rank: Frequent Contributor
timestamp: April 15, 2019, 03:36:03 pm
content: What? Exactly when are cookies not on your local computer? That is sort of the whole point of them - they stay with the browser and user.

author: legacy
author_rank: Super Contributor
timestamp: April 17, 2019, 06:30:19 am
content: Quote from: agehall on April 15, 2019, 03:36:03 pmwhen there is a javascript part that sends information remotely to a server, so the information is not really locally stored, and you cannot disable javascript because pages use a lot of java scripts to work.

author: NorthGuy
author_rank: Super Contributor
timestamp: April 17, 2019, 12:58:58 pm
content: Quote from: legacy on April 17, 2019, 06:30:19 amEven though Javascript can set cookies (which will be visible on the server at next HTTP request), they're still stored on the browser side. This certainly can be used to pass information to the server, but Javascript already has the ability to pass information to the server through direct HTTP requests.