Then I soldered wires to them and connected to Waveshare’s STLink V2 clone. Although it’s intended to be used with STM32s only, it happily works with this NXP MCU as wellpic.twitter.com/w07LxEkLU4
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Add this Tweet to your website by copying the code below. Learn more
Add this video to your website by copying the code below. Learn more
By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.
| Country | Code | For customers of |
|---|---|---|
| United States | 40404 | (any) |
| Canada | 21212 | (any) |
| United Kingdom | 86444 | Vodafone, Orange, 3, O2 |
| Brazil | 40404 | Nextel, TIM |
| Haiti | 40404 | Digicel, Voila |
| Ireland | 51210 | Vodafone, O2 |
| India | 53000 | Bharti Airtel, Videocon, Reliance |
| Indonesia | 89887 | AXIS, 3, Telkomsel, Indosat, XL Axiata |
| Italy | 4880804 | Wind |
| 3424486444 | Vodafone | |
| » See SMS short codes for other countries | ||
This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.
Hover over the profile pic and click the Following button to unfollow any account.
When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.
The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.
Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.
Get instant insight into what people are talking about now.
Follow more accounts to get instant updates about topics you care about.
See the latest conversations about any topic instantly.
Catch up instantly on the best stories happening as they unfold.
Then I soldered wires to them and connected to Waveshare’s STLink V2 clone. Although it’s intended to be used with STM32s only, it happily works with this NXP MCU as wellpic.twitter.com/w07LxEkLU4
Default OpenOCD’s config for LPC1xxx sets 10 kHz tckrate, which leads to weird bugs whenever you try to access any fair amount of memory - e.g. you can read 16 bytes of memory just fine, but not 1024. And of course flashing worked neither
I did set it to 4 MHz and then it started to work flawlessly. The cable booted in disk mode - reflashing with astrisctl and it can now be recognized by Astris itself:pic.twitter.com/JwHi8DXVBq
Now let’s examine common problems The first one is damaged motherboard. There’re 2 broken tracks (one per side) that come from USB power of both cords. Something wasn’t powered up at all?
Here they are already fixed with little pieces of copper wires, but you can recognize their locations anyway:pic.twitter.com/aRFRayWCgv
Another problem is connector: 1) It’s weirdly ringed (continuity testing) with multimeter
2) Its bottom side’s pin pad (which is meant to be connected with the port) looks recessed. Not sure you can see that on the photo below, but it is. This, I believe, makes connection between it and the female port very unstable or just not working at allpic.twitter.com/Cg0UIslcNb
So, it is to be replaced. As I mentioned in my Lightning write-up, Kong’s connector doesn’t have any logic inside, as it’s handled by MCU and FPGA inside the enclosure. The pinout is written with silk on the MLB. I replaced the connector with jumper wires and a breakout boardpic.twitter.com/whK0PMC4Yd
Now, the last problem - Kong doesn’t seem to like modern HOSTIDs (again, look at my Lightning write-up in case you don't know what this means):pic.twitter.com/RXlRhMoDme
But that can be fixed easily by setting disableIdCheck environmental variable: astrisctl setenv disableIdCheck 1 (Only available in newer firmwares such as 0.52 or 0.49)
where did you find this from?
Impossible RE hack - don’t tell anyone: strings firmware.bin
Just a joke, don’t take personally. I really did just find the string in FW image and guessed what it could mean
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.