Harmony 1.10+PIC32MX795F512L GFX_HGC_GetScreenState出错

什么例外？你是否单步寻找导致异常的线路？



      以下为原文

    What exception?
Did you single step in to find the line that causes the exception?

嗨，NKurzman，我在调试中做了一步，发现：在SysStask-任务中：gfx任务（SysObj.gfxObjut0）；它执行gfxpPrimiTyvia句柄gfxpPrimiTyvOPEN（const SysSimuleEx index index）-在该函数例程上，而在LyDrvxGFx句柄DRV句柄= PrimiTeVo上BJ[Index ] .IntDATA & G.；DRVOPENT（索引，DRVVIOION IntEntType）-它进入GETGFXHGCGETFIGSTORT STATE（），然后进入异常处理程序，并以LeSysSyDebug Grand打印（SysHyrrOrthError）\NeUngEnter异常%s（原因＝%D，ADDR＝%X）.n，O.EaseSySTR，AuthExodeCype，AyExablAdDR；不写入。调试窗口的任何内容



      以下为原文

    Hi NKurzman, 
 
I did single step into the debug and found that:
in the sys_tasks - it goes to funtion: GFX_Tasks(sysObj.gfxObject0);
and it goes to execute GFX_PRIMITIVE_HANDLE GFX_PRIMITIVE_Open( const SYS_MODULE_INDEX index ) - in that function routine while on line DRV_GFX_HANDLE drvHandle = primitiveObj[index].initData->drvOpen(index, DRV_IO_INTENT_EXCLUSIVE) - it goes to get GFX_HGC_GetScreenState() and it then goes into exception handler
 
and somehow the line 
SYS_DEBUG_PRINT(SYS_ERROR_ERROR, "nGeneral Exception %s (cause=%d, addr=%x).n",
_cause_str, _excep_code, _excep_addr);
does not write anything to the debug window 
 
Thanks
Silas
 

这条线将把数据从调试串口中取出。这是一个需要在和谐中启用和配置的东西。我不使用HGC用于我的屏幕。当我启动时，它不起作用。所以你的问题在那里，而不是司机。我假设你：正确地配置它。有屏幕创建。有足够的堆来使用它。你有没有一步ItgfxHgcGETScFieldStand（）？或者在电话中有例外？



      以下为原文

    That Line would the Data out of the Debug Serial Port.
It is something that would need to be enabled and configured in Harmony.
 
I am Not Using the HGC for my screens.  It did not work when I started.
SO you Issue is there and not with the driver.
I assume you:

• configured it correctly.
  
• Have screens created.
  
• Have enough Heap for it to use.
  

Did you single step into GFX_HGC_GetScreenState() ?  Or does it get the exception on the call?
 

嗨，NKurzman，是的，我的驱动程序配置正确，屏幕也被创建了，除了字体文件外，没有什么特别的东西。我做了一个步骤——它只是在GFXHGCGETGETScript状态（）上调用异常。我想我会回到1.09并安装和测试。谢西拉斯



      以下为原文

    Hi NKurzman,
 
Yes, I do have driver configured correctly, also screens created, and nothing much really except fonts file loaded. 
I did signle step - it just gets exception on GFX_HGC_GetScreenState() call.
 
I think I would go back to 1.09 and setup and test.  
 
thanks
Silas
 

你怎么会有例外呢？它是一个虚空函数，它不需要进入函数。我怀疑从1.09到1.10的变化很大。我假设你使用的是和声和MHC的匹配版本。



      以下为原文

    Step into gives you the exception?
It is a Void function, it shouldn't
You need to step into the function.
 
I doubt much changed from 1.09 to 1.10.
I assume you are using a matching version of Harmony and MHC. 

Hi NKurZMANN函数只是一行返回-执行指针出现在返回行上，它抛出异常-转到异常处理程序。是的，我使用的是和声和MHC的匹配版本。我现在是和声版本1.09，并从SSD1926文件集导出了ILI9163C的驱动程序。代码生成没有任何问题，也可以很好地写“原样”。我需要对DRVIVGFXILI9163C头和C源文件进行更新。



      以下为原文

    Hi NKurzman
 
The function is just one line return - the execution pointer comes on the return line and it throws exception - goes to exception handler. Yes, I am using matching versions of Harmony and MHC. 
 
I am now Harmony version 1.09 - and derived the driver for ILI9163c  from SSD1926 set of files. The code is generated without any issue and also comiles fine "as is". I need to make updates to drv_gfx_ili9163c header and c source files now.
 
thanks 
Silas

引起异常的返回线是什么？我看不懂密码。什么和谐模块在里面？或者是你的密码？您可以尝试调试您自己，或者您可以放入支持票并等待。



      以下为原文

    What is the return line that is causing the exception?, I can't see the Code.  
What Harmony module is in in? Or is it your code?
 
You can Try to debug this your self, or you can put in a support ticket and wait.

下面是执行的方式：在文件FGFXPrimiType句柄中，GFxxPrimiType打开（const SysMuleMedex index index）-gt；在GfxHgcLyMealth.c中输入TopfxHgcGETScutsStand（），然后在SyrSyExtExcExcExcRe.c中创建一个SypRealApExalExpReLo.c。一旦完成了1.09的设置，我想检查我是否在那里得到了类似的行为。如果它工作得很好，我仍然想走过去看看发生了什么。



      以下为原文

    here is how the execution goes:
In the file gfx_primitive.c  working in the function 
GFX_PRIMITIVE_HANDLE GFX_PRIMITIVE_Open( const SYS_MODULE_INDEX index )
      --> goes to line DRV_GFX_HANDLE drvHandle = primitiveObj[index].initData->drvOpen(index, DRV_IO_INTENT_EXCLUSIVE);
      --> from there it goes to GFX_HGC_GetScreenState() in gfx_hgc_definitions.c  and then to _general_exception_handler in system_exceptions.c  
 
Once the set up for 1.09 is completed, I want to check if I get this similar behavior there. If it works fine, I still want to step through and see what is happening. 
 
thanks
Silas