Whizzing通过了断点

为什么在Inc文件中应该有断点？Inc文件不应该包含可执行代码…



      以下为原文

   
Why there should be a breakpoint in an inc file?
An inc file should not contain executable code...

来自于HTTP//www. McCHIP.COM/FUMMS/M10329 31.ASPXI不知道为什么OP启动了一个新的主题。他正在做老式的绝对模式，并使用Inc文件在多个文件上传播源。MPLABX真正面向更现代的“可重定位”模式。



      以下为原文

    Comes from http://www.microchip.com/forums/m1032931.aspx
I don't know why the OP started a new topic.
He's doing old fashioned absolute mode, and using INC files to spread the source across more than one file.
MPLABX is really geared more towards the more modern "relocatable" mode.

是的，20年前重新定位是“现代的”；-老式的绝对模式根本不支持。



      以下为原文

   
Yep, relocatable was "modern" 20 years ago ;-)
The old fashioned absolute mode is simply not supported anymore.
http://www.microchip.com/forums/FindPost/1032397

好的，像MPLAB Xcrutiating遇到的很多问题是，它不会在断点处停止，因为IDE没有以MPASM的方式看到Inc文件。MPASM接受Inc文件，如果它可以找到它们，但MPLAX X只是不喜欢它们。我已经把这一个文件移动到源文件文件夹，而其他文件在项目文件夹中，它现在正在工作…也许我应该把它们都搬走？为什么有些工作而不是其他工作？这是不是相对地存储的？？？？



      以下为原文

    OK like many problems I'm encountering with MPLAB Xcrutiating is that it's not stopping at the breakpoint because the IDE does not see the inc files in the same way as MPASM.  MPASM accepts the inc files if it can find them but MPLAB X just doesn't like them.  I've moved this one file to the source file folder whereas the others are in the project folder and it's working now... maybe I should move them all?  Why do some work and not others?  Is this stored as relative not absolute???
 

我使用绝对模式，因为我可以通过互联网远程改变每个RAM和PGM位置。此外，我们现在还没有代码空间，所以我需要最有效的添加代码的方法。不管我是否应该使用它，这都是现有代码，而不是重写多年的工作。直到我切换到另一个不使用MPLAB的微



      以下为原文

    I use absolute mode because I can change each RAM and PGM location remotely over the internet.  Also we have no code space left now so I need the most efficient way of adding code.
 
Regardless of whether I should or shouldn't be using it this is existing code and I'm not re-writing years of work... until I switch to another micro that doesn't use MPLAB
 

可执行的汇编源代码应该是.ASM，不是.Inc.。你把这些文件添加到你的项目中了吗？硬件断点是有限的，依赖于PIC设备。



      以下为原文

    Executable assembly source code should be .asm, not .inc.  Did you add these files to your project?  Hardware breakpoints are limited and dependent on the PIC device.
 

是的，它们被添加了。在这个文件夹里，除了一个给人带来麻烦的文件之外，他们并不满意。我看不出有什么不同。将这个放在源文件夹中意味着断点工作并建立它。为什么应该执行代码不在Inc文件中。我这样做已经好几年了。对于MPLAB，它必须是非ASM。它现在正在建设和工作。顺便说一下，模拟器不模拟ADC。它忽略了连续模式，所以我必须为SIM插入一个IMPUT来手动重启它。使用具有相同设置的皮卡3可以很好地工作。



      以下为原文

    Yes they're added.  It wasn't happy with them in the source folder apart from this one file which was giving trouble. I don't see what's different.  Putting this one in the source folder means the breakpoints work and it builds.
 
Why should executable code not be in an inc file.  I've done it this way for years. With MPLAB it had to be inc not asm. It's building and working now.
 
By the way the simulator does not simulate the ADC properly.  It ignores continuous mode so I have to put an interupt in for the sim to manually restart it.  Works fine using the PICKit 3 with the same settings.

我不太明白你的意思。你是说这个文件位于其他地方，而不是在你的项目文件夹里？如果是这样，您可能需要为MPLABX提供一个路径。文件扩展.Inc用于包含（头）文件；而.ASM是源文件扩展名。您可以包括任何类型的文件，而不是ASM、.Inc.、FoO以及其他任何类型的文件。包括文件只是意味着把文件的内容放在那个位置。模拟器不支持所有外围设备。最好使用真正的硬件。



      以下为原文

   
I don't quite understand what you mean. Are you saying this file is located somewhere else, and not in your project folder? If so, you might have to provide a path for MPLABX.
 

The file extension .inc is for include (header) file; while .asm is a source file extension. You can include any type of file rather it is .asm, .inc, .foo, and whatever. Including a file simply means placing the content of that file in that location.
 

Simulator does not support all peripherals. It's best to use the real hardware.

我把它拿回来…它只是在它想要的时候工作。这是垃圾。我受够了Microchip。享受你的IDE粉丝男孩



      以下为原文

    I take it back... it just works when it wants to. It's rubbish. I've had enough of Microchip. Enjoy your IDE fan boys
 

你有什么问题吗？粉丝男孩？有一个小俱乐部。这不是因为你是粉丝，而是和你的工具一起工作。



      以下为原文

    There is you problem? MPLabX fan boys? There is a small club. It is not about being s fanboy, but working with the tools you have.

粉丝男孩？您想使用PIC设备，MPLAB是您必须使用的工具。没有什么阻止你使用另一个供应商的微控制器。



      以下为原文

   
Fan boys? You want to use PIC devices, MPLAB is the tool you have to work with. Nothing stops you from using another vendor's microcontrollers.

我总是使用绝对模式。它不使用“C”编译器/链接器范例，因此它给了你更多的自由。我的Inc文件定义和构建基于环境的需要的函数。他们根据情况分配变量。它们还可以分配比特标志。它们将代码发射到不同的部分中，例如，Inc文件可以将代码注入初始化部分、进入主循环部分、进入特定设计的事件处理部分等。它们还可以定义我可以在我的主代码中使用的代码。EDOM带有可重新定位的代码——你所拥有的是与C链接的能力，如果我在汇编程序中写，我不需要。所以，不要把“现代”混淆为“进步”和“大家推荐”的“现代”。



      以下为原文

    I always use absolute mode. It doesn't use "C" compiler/linker paradigm, so it gives you much more freedom. My inc files define and build functions which are needed based on circumstances. They allocate variables based on circumstances. They can also allocate bit flags. They emit code into various sections - e.g. the inc file can inject code into initialization section, into main loop section, into specifically designed event-handling sections etc. They also can do defines which I can use in my main code.
 
You will never get such freedom with reclocatable code - all you've got is an ability to link with C, which, if I write in assembler, I don't need.
 
So, don't confuse "modern" as "progressive" with "modern" as "everyone recommends".
 

如果我出于某种原因选择ASM，那是因为我需要“完全自由和完全控制”，所以“可重新定位”超出了范围。BTW:我从来没有在“Inc”文件上设置代码，甚至连“X”都没有问题。也许这是一个发展过程的问题，只是我的2分钱…



      以下为原文

    Hi
 

 
I'll subscribe to that.
 
If, for some reason I chose ASM, is because I need my "total freedom and total control", so "relocatable" is out of scope.
 
BTW:
I never had problems in putting code on "inc" files, not even with "the X thing". Maybe its a question of development process.
 
Just my 2 cents....
 
 
Best regards
Jorge
 

我认为，如果你想要完全控制，你也可以在可重新定位的代码中使用。因此，使用可重新定位的样式是我个人的“完全自由”。老实说，几年以来我在汇编中代码不多。让链接器做所有无聊的事情，在真正需要的时候只使用总控制…



      以下为原文

    I think if you want total control, you can have this in relocatable code as well.
So using relocatable style is my personal "total freedom".
 
Honestly I do not code much in assembly since years.
Guess if one usually codes in C, it is more easy to switch back to relocatable
than to absolute assembly code. Let the linker do all that boring stuff and
only use total control when really necessary...

HII主要希望对可变布局进行完全控制，主要是探索RAM并行系统具有类似的并行结构，使得字段具有相同的偏移量。例如，在BANG1中具有TX-FIFO结构，在BANG2中具有RX FIFO。“放置/获取/计数/缓冲器”偏移（均衡器）将是相同的。或者类似地将状态机分散在状态变量中，在同一银行中的外围处理机的“本地”变量是外围设备的SFR。这样，在每个状态机的开头，我只需要切换银行，而不是在示例中像任何RAM访问一样。E代码从微芯片数据表。同样的规划可以做子程序/ LUTS/…布局，尽量减少“页面化”。我发现这与“可重定位代码”很不协调，但是Otoh我没有太多的经验。



      以下为原文

    Hi
 
I mainly want total control on variable placement.
Mostly to explore the RAM banking system to have similar structures in parallel so the fields have the same offset.
For example having the a TX FIFO structure in bank1 and the RX FIFO in bank2. The "put/get/count/buffer" offsets (EQU) will be the same. Or likewise spread state machines state variables in parallel, also have the "local" variables of a peripheral handler in the same bank were the SFRs for that peripheral are.
This way I only have to switch banks at the beginning of each state machine, and not before any RAM access like in the example code from Microchip datasheets.
The same planning can be made on subroutine/LUTs/...  placement, to minimize "pagging".
 
I find this quite dificult to do with "relocatable code", but OTOH I don't have much experience with it.
 
Best regards
Jorge
 
 

我也是。此外，绝对模式是否具有“操作数包含不可解析标签或过于复杂”的错误，这是由于使用可重定位模式而造成的错误。我想我们是叛逆的。这里也一样，但是要小心“完全控制”这样的词。我在近十年前使用了这两个确切的词，并在这个论坛上发动了2008次战争。（文件扩展不会影响汇编操作。这只是一个编码约定。尽管如此，可重新定位模式可以通过使用绝对地址来编写绝对代码，但这样做的目的是什么。



      以下为原文

     
Me too.  Besides, absolute mode does _not_ have such a drag as the "operand contains unresolvable labels or is too complex" assembler error from using relocatable mode. 
 

I guess we are rebellious. ;)
 

Same here, but be careful with words like "total control".  I used these two exact words almost a decade ago and it started the War of 2008 in this forum. :(
 

The file extension does not affect assembly operation. It is just a coding convention.
 
With all that said, relocatable mode can be made to write absolute code by using absolute addresses, but what is the point of doing that.
 
 

编写可重定位代码并指定所有的固定地址是没有意义的。但是，如果在一个项目中需要有绝对地址的代码和变量的10%，为什么要用90%？当我试图修改AN1310引导程序重新定位时，有一次我遇到了这个问题。我想这会在几分钟内完成，直到出现…



      以下为原文

   
Would make no sense to write relocatable code and specify fixed addresses for everything.
But, if in a project there is a need of absolute addresses for <10% of code and variables, why bother with the 90%?
 
One point for absolute ;-)
 
Once I had this issue when I tried to modify the AN1310 bootloader to relocatable. Thought it would be done in a few minutes until this came up...

绝对模式就是这样的；



      以下为原文

   
That is what absolute mode is for ;-)