{"action":"created","issue":{"url":"https://api.github.com/repos/grandideastudio/jtagulator/issues/23","repository_url":"https://api.github.com/repos/grandideastudio/jtagulator","labels_url":"https://api.github.com/repos/grandideastudio/jtagulator/issues/23/labels{/name}","comments_url":"https://api.github.com/repos/grandideastudio/jtagulator/issues/23/comments","events_url":"https://api.github.com/repos/grandideastudio/jtagulator/issues/23/events","html_url":"https://github.com/grandideastudio/jtagulator/issues/23","id":343624078,"node_id":"MDU6SXNzdWUzNDM2MjQwNzg=","number":23,"title":"Perhaps UART Buffering Problem ?","user":{"login":"shuber1","id":7080375,"node_id":"MDQ6VXNlcjcwODAzNzU=","avatar_url":"https://avatars1.githubusercontent.com/u/7080375?v=4","gravatar_id":"","url":"https://api.github.com/users/shuber1","html_url":"https://github.com/shuber1","followers_url":"https://api.github.com/users/shuber1/followers","following_url":"https://api.github.com/users/shuber1/following{/other_user}","gists_url":"https://api.github.com/users/shuber1/gists{/gist_id}","starred_url":"https://api.github.com/users/shuber1/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/shuber1/subscriptions","organizations_url":"https://api.github.com/users/shuber1/orgs","repos_url":"https://api.github.com/users/shuber1/repos","events_url":"https://api.github.com/users/shuber1/events{/privacy}","received_events_url":"https://api.github.com/users/shuber1/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-07-23T13:03:54Z","updated_at":"2018-07-23T15:57:18Z","closed_at":null,"author_association":"NONE","body":"Hi\r\nI have a UART connection to a device which has a dump command writing memory content in hexdump style to the console. When I trigger this command to dump a longer range I have strange interrupts and line breaks in the output:\r\n\r\n> 0x8102A9D0: 00 00 00 00 00 00 00 00 81 02 A9 C8 81 02 A9 D8 ................\r\n> 0x8102A9E0: 00 00 00 00 00 00 00 00 FE FF FF FF 00 00 00 00 ................\r\n> 0x8102A9F0: 00 00 00 00 00 00 00 00 81 02 A8102AA60: 00 00 00 00 00 00 00 00 FE 7F FF FF 00 00 00 00 ................\r\n> 0x8102AA70: 00 00 00 00 00 00 00 00 81 02 AA 78 81 02 AA 78 ...........x...x\r\n> 0x8102AA80: 00 00 00 00 00 00 00 00 FF FF EF FF 00 00 00 00 ................\r\n> 0x8102AA90: 00 00 00 00 00 00 00 00 81 02 AA 98 81 02 A2 98 ................\r\n\r\nor here:\r\n\r\n> 0x810660B0: 83 05 43 A0 00 00 07 9F 81 06 60 88 81 04 58 38 ..C..........X8\r\n> 0x810660C0: 00 00 08 24 00 00 00 02 FF 7F FF FF 83 47 FE 3C ...$.........G.<\r\n> 0x810660D0: 83 40 2D 6... ...\"..a...`X\r\n> 0x81066140: 00 00 00 2C 00 00 00 01 FF FF FF FF 00 00 00 00 ...,............\r\n> 0x81066150: 83 47 DA 20 00 00 00 23 81 04 61 38 81 06 61 78 .G. ...#..a8..ax\r\n\r\nI assume it is some kind of buffering problem, because this break/ disturbance happens ever 2864 byte ?\r\nWhen I use a FT232R breakout board I don't have the problem with the interruption but then I have wrong values in the output ?\r\nMy jtagulator firmware is version 1.5 llatest from release.\r\nAs console tool I used minicom, but had the same problem with screen. Perhaps some has an idea."},"comment":{"url":"https://api.github.com/repos/grandideastudio/jtagulator/issues/comments/407108481","html_url":"https://github.com/grandideastudio/jtagulator/issues/23#issuecomment-407108481","issue_url":"https://api.github.com/repos/grandideastudio/jtagulator/issues/23","id":407108481,"node_id":"MDEyOklzc3VlQ29tbWVudDQwNzEwODQ4MQ==","user":{"login":"joegrand","id":4250259,"node_id":"MDQ6VXNlcjQyNTAyNTk=","avatar_url":"https://avatars0.githubusercontent.com/u/4250259?v=4","gravatar_id":"","url":"https://api.github.com/users/joegrand","html_url":"https://github.com/joegrand","followers_url":"https://api.github.com/users/joegrand/followers","following_url":"https://api.github.com/users/joegrand/following{/other_user}","gists_url":"https://api.github.com/users/joegrand/gists{/gist_id}","starred_url":"https://api.github.com/users/joegrand/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/joegrand/subscriptions","organizations_url":"https://api.github.com/users/joegrand/orgs","repos_url":"https://api.github.com/users/joegrand/repos","events_url":"https://api.github.com/users/joegrand/events{/privacy}","received_events_url":"https://api.github.com/users/joegrand/received_events","type":"User","site_admin":false},"created_at":"2018-07-23T15:57:18Z","updated_at":"2018-07-23T15:57:18Z","author_association":"MEMBER","body":"If you're seeing a similar (but not exact) problem when using a standalone FT232R breakout board, it sounds like it's not specifically a JTAGulator problem. I'm wondering if your device is the one outputting an incorrect byte every 2864 bytes, which causes either the JTAGulator or breakout board to behave strangely and handle that one byte in a different way. The JTAGulator does not use interrupts, so it may be the buffer is full and needs a moment to catch up, but I think that's unlikely. You could verify by looking directly at your target output with an oscilloscope to see what that character is ever 2864 bytes."}}
{"actor":{"display_login":"joegrand"}}