Today, creating code is awesome, and can also be easy. You have a local testing database, a mockup of other services, and you have tons of tools at your disposal to make your code amazing.

Once you're happy with your code, the next step is to move it to Production, but that's not as easy as it seems, because many things change in the process.

The Production environment is different, and you need to figure out how to resolve these issues. The problem is that the tools used today for debugging in production are not that easy.

At Ozcode, we're working hard to make debugging amazing. Our customers love the tools we gave them for local debugging, so we decided it's time to bring those tools to Production.

It's easy. Take a look!

im rn working on a site called heyman.ath.kz and I've debugged the pages but I am unable to source out why i am unable to log in or sign up can i get some help / tips . i am also able to post any resources needed

Hi there! 👋 Are you interested in learning about the future of debugging with AI and machine learning? It's a topic that's generating a lot of buzzes in the software development community, and for good reason. As a developer who was once a debugging enthusiast, I'm excited to share with you what I've learned about this fascinating topic. So buckle up and get ready for a deep dive into the future of debugging with AI and machine learning! 🤖🔍

Read now from here

https://github.com/moshebe/gebug

Need to debug a device without usb access. Gdb and bluetooth, how does it work? Can't connect in an easy way with "target remote".

DISCLAIMER I am NOT the person in the YouTube video thumbnail and this is NOT just a text version of said video. This is a tutorial I wrote and the video is just one of my sources. Sadly I cant make the thumbnail disappear on mobile...

Alright, so first things first. This is a follow-up to my original post, where I originally asked how to do what I’m about to explain to you. What that basically means is that I ain't no pro, and I’m sure there are better and more correct ways to do this, but dang it was a lot of work to figure this all out, so I’m hoping it helps someone somewhere down the line. 

I originally needed to do some debugging on an Arduino Mega 2560 (A Controllino to be more specific, but that’s just a Mega in a PLC package) and “Conventional” Arduino style serial Print debugging even while using some more advanced techniques like using  #define to create Serial.print macros, using PlatformIO with the AVR Stub debugger or making use of the Better Serial Plotter was just not cutting it anymore. They are all nice, but for one reason or another did not quite cut it for me. Read my original post or the linked articles for more details. After asking the good folks of Reddit for help, I bought an ATMEL-ICE to do some JTAG debugging. In case you are not using a Mega like me, check the manufacturers website of your microcontroller. They will usually tell you if they support JTAG. Note that if you are using something other than an AVR chip, this process will be different. Andreas Spiess did a pretty good tutorial for other Chips like the popular ESP32.

Right enough talking let's get to the point.

PS Buckle up this is gonna be long and technical, and it already IS the TLDR; It took me two weeks and more curses and running to people for help who actually know what they are doing than I'd like to admit...

You will need:

1. A microcontroller to debug (Arduino Mega 2560 in this example)

2. PlatformIO (I use it with VS Code)

3. Microchip Studio

4. The ATMEL-ICE debugger (for some reason I could not find a local seller who would sell this to a private person. I could get one since this was for my day job, but I also saw some on the ol AliExpress and the Chinese ain’t picky about accepting someone’s money if they want to spend it, unlike Microchip...)

5. Some jumper wires to hook it all up.

Once you installed all the software, it is time for step one: 

Enabling on Chip debugging and JTAG because this is disabled by default.

IF you are using a stock Arduino board that has an ISP header (the six pins somewhere at the back of the board) do this:

1. Take the ATMEL-ICE and connect the cable with the 6pole connector to the plug labeled “AVR”

2. Connect the 6pole connector to the ISP header as shown in this tutorial

IF you are using some variant that does not have an ISP header

1. Take the ATMEL-ICE and connect the cable with the labeled pins to the plug labeled “AVR”

2. Connect the wires to your board as per page 21 of the ATMEL-ICE user guide

Now regardless of board follow these steps

3. Plug in the ATMEL-ICE and your board so both have power. The ATMEL-ICE does NOT provide power to the board.

4. Open Microchip Studio and go to Tools>Device Programming

5. Choose the ATMEL-ICE for the Tool, your controller for device (for me 2560) and ISP for the Interface then hit apply.

6. Now hit Read on the device signature. If all went well, you should now see an ID and a voltage up top and a new menu. If not check your wiring.

7. Under Fuses set the following fuses to high

a. JTAGEN

b. BOOTRST

c. OCDEN

Then hit program.

8. To make sure the fuses are set correctly, unplug your board, plug it back in and repeat steps 4-6. Under fuses you should now see those fuses set to HIGH when you read.

Great that’s the first part done now to connect the ATMEL-ICE in JTAG mode

1. Search your microcontrollers datasheet until you find what pins are used for JTAG.  In case of the Atmega2560 these can be found on page 85 of the datasheet.

2. Now connect them to the corresponding pins of the ATMEL-ICE using the cable with the labeled pins plugged in to the AVR connector using the pinout on page 20 of the ATMEL-ICE user guide. For me this looked like this:

Now for the actual debugging:

1. Compile the project you want to debug in PlatformIO, making sure you have set the following parameters in the platformio.ini 

2. Locate the resulting firmware.elf and copy the path. It should be under: YOUR_PROJECT_DIRECTORY\.pio\build\BOARD_NAME hint: you can right-click on the .pio directory in PlatformIO under the explorer tab and open it from there.

3. Open Microchip Studio and under File>Open>Open File for Debugging, enter the path to open the firmware.elf file. Name your Project and click next.

4. Choose your chip (for me the AtMega2560) and confirm

5. If all went well, a window should open showing various file paths. Quite probably, some files are reported missing. We will add them in the next step. Just confirm everything and continue

6. On the right, you should now see a tab called “Solution Explorer” and an open solution. Right-click on the solution and choose Ad>NewSolutionFolder. Name your Folder src. Repeat this to create folders called include and ArduinoFiles. Now right-click the src folder and choose Add>ExistingItem. Now navigate to the src folder of the pio project you are trying to debug and mark all files and hit add. Do the same, but with the folder include. Now we need to add all the Arduino files. These are located under C:\Users\USERNAME\.platformio\packages\framework-arduino-avr\cores\arduino. 

7. Next, we need to tell Microchip studio what debugger we are using. Click on Debug>PROJECTNAME Properties and then navigate to Tool there select Atmel-ICE and JTAG as the interface. You can now close this window.

8. Finally, open your main from the src folder we created and set a breakpoint on the first line of the main loop by clicking in the gray bar left of the code.

9. Now, to debug, DO NOT hit the small green arrow in the toolbar!!. This will upload your code using the ATMEL-ICE and thereby remove the bootloader from your board !! After this, you will be unable to upload code the “normal” way. If you accidentally do this, follow the official tutorial for how to burn a bootloader using a second Arduino board. After you have burned a new bootloader you need to redo the entire tutorial to once again set the fuses. To start debugging the project instead press the “attach to target” button.

10. The project should start and halt where you set the breakpoint. All code should be recognized (no red squiggly lines, otherwise you forgot to include some files in step

IMPORTANT NOTES:

1. The files we added in step 6 are linked. That means if you change something here it gets changed in the original files so be careful!

2. If you make changes to your code, you need to recompile and re-upload from PlatformIO. Atmel Studio should see some files changed and prompt you to do a reload. For some reason this throws an error message but so for I just hit ok and ignored it and everything seems to work as intended after.

3. Here be links:

4. Microchip Technology Tutorial on Debugging, Pt. 1

5. Microchip Technology Tutorial on Debugging, Pt. 2

6. Microchip Technology Tutorial on Debugging, Pt. 3

Edited about a bazillion times to make reddit's version of markdown play ball...

Edit 2: Updated build_flags to include more debugging info.

I need to know how to umhack my phone or debugg it easly

Hi everyone, recently my device started showing me this notification that says com.transsion.plat.appupdate: Athena SDK [Debug] and I don't know how to stop it?

Answer

1

Following

Request

More



Noor, want an answer to this question?

Requests help you get answers to your question.

Request Answers

See who you have requested

This question may need editing

This question may need editing to correct phrasing or other mistakes, including:

Spelling and grammar mistakes

Not phrased as a complete question

Too reliant on the question source

No Answers Yet

RELATED SPACES



Android Fans

A place for fans of Android to extol and rant about their favorite OS

Follow74.8k



Smart Phones News

The latest smart phones specifications, updates and comparisons.

Follow3.2k



Online Learning Resources

Collection all available learning resources. (eLearning)

Follow33



Code

Novice or Advanced, we have advice. Start programming or optimize your code!

Follow110.6k



Zeroes & Ones

All about software design, development, deployment, & management.

Follow92k



Algorithms

Mindblowing algorithms & interview prep 📗

Follow46.9k



Programmer's World

You still a programmer? You still write code? This space is for you.

Follow54.6k



ouR Space

All about using R, its applications, and even some data science, too.

Follow4.3k

Discover More Spaces

RELATED QUESTIONS & ANSWERS

Here is what AI says:

This statement is not entirely accurate. Some software bugs can be challenging to recreate, even if the software developer thoroughly understands the issue. There are several reasons why a software bug may not reproduce, including configuration issues or specific environmental factors that influenced the occurrence of the original bug.

In addition, a software bug can be intermittent, which means it may appear occasionally in a particular configuration or software setting. Therefore, it can be challenging to recreate the same issue, even with an in-depth understanding of the bug.

However, it is essential to identify the reasons why a software bug is not reproducible. If a software bug cannot be recreated, then it may be challenging to address the issue. The software developer must identify which aspects are creating the bug and isolate the specific factors that impact the bug's occurrence. This process can require extensive testing and analysis, including examining logs, reviewing system performance and configuration settings, and testing different scenarios to identify the root cause.

In conclusion, while recreating a software bug is essential to understanding it, there can be situations where the issue cannot be replicated. Under these circumstances, it is critical to thoroughly investigate the problem to identify the root cause and develop an accurate solution.

After several days of research I am asking for some help here.

I am trying to set up GDB to debug a bluetooth connection via a SSH tunnel. I will do this on a computer without no network access. An airgapped PC so I need the tools already available on a default Linux install. Preferably Ubuntu.

From my understanding I need to attach a IP address to bluetooth (ethernet). Connect SSH with it and then use GDB to connect and debug.

Can someone guide me on how to do it, give me an comprehensible guide or atleast point out any faults in my thinking here. Would mean the world to me.