Menu

Elusive Error no Clue what it is??

Help
xtal10
2016-07-19
2016-07-31
<< < 1 2 3 (Page 3 of 3)
  • xtal10

    xtal10 - 2016-07-23

    I have received nothing as yet

     
    • Anobium

      Anobium - 2016-07-23

      I have proof of delivery and the request for chat is awaiting you approval, see the attachment.

      This have worked everytime in the past - I have sent your personal messages and emails to the email address you provided.

      Check your trash, check your spam, check all of your folders.

       
  • xtal10

    xtal10 - 2016-07-23

    Nothing in spam nothing received .... check box set to all all to send me mail....primary email address is correct.....I tried sending a email from Gmail to Xtal10@user.sourceforge.net , and got notification failue.. is this normal ?

     
    • Anobium

      Anobium - 2016-07-23

      Look at the attachment!!!! what email address is this? Is this correct address???????

       
  • xtal10

    xtal10 - 2016-07-23

    Yes Email is correct

     
  • xtal10

    xtal10 - 2016-07-23

    is ther a space between c and h on the invite?

     

    Last edit: xtal10 2016-07-23
    • Anobium

      Anobium - 2016-07-23

      How about this. Log onto a Google account. Create one if you don't have one. When you have done this send a personal message with the Google email address. I only chat oñ Google chat so you don't get to choose.

       
  • xtal10

    xtal10 - 2016-07-23

    My gmail.com is the same user id as the charter.net.
    How do I send a PM ?

     
  • Anobium

    Anobium - 2016-07-23

    You are making a joke on me?

    Delivery to the following recipient failed permanently:

     xtal10@gmail.com
    

    Technical details of permanent failure:
    Google tried to deliver your message, but it was rejected by the server for the recipient domain gmail.com by gmail-smtp-in.l.google.com. [2607:f8b0:4003:c09::1b].

     
  • xtal10

    xtal10 - 2016-07-23

    use mswabcdes

     

    Last edit: xtal10 2016-07-23
  • xtal10

    xtal10 - 2016-07-28

    Anobium
    Have you done any checking on the 16F18326, and am I all wet, or are there some issues.
    Are thery any updated Demos available??
    thx

     
  • Anobium

    Anobium - 2016-07-29

    Support Update

    Current status - pending - not resolved

    Remember this is all free. Support is free, time is not.

    Not a very friendly microcontroller.

    1. Repeating the issues you have raised have been validated. I have the microcontroller in the lab on test. Root cause not yet identified.
    2. Great Cow BASIC was incorrectly iniitialising the microcontroller but this had no material impact.on the root cause. Note: system.h now supports this microcontroller correctly - I have adapted the system.h to support the latest errata for this microcontroller.
    3. Microchip case number: 00108515. This ticket relates to non-support of this chip within the Microchip IDE toolset. Currently with engineering to to resolve the MCC support issue identified. This also impacts the 16f18346 and this microcontroller the 16f18346. This issue prevents MPLAB-X from generating code to support the chip. Ticket is pending closure. Microchip will release a patch in early August. I have to test when released to me.
    4. Microchip case number: 00109610. This ticket is to address the issue related to the simpliest ASM file not working with the 16f18326. I have provided ASM source. This ticket is the proof of the current issue you are experiencing. Ticket is pending and therefore open.
    5. PicKit2 and 3 support. Currently, these microcontrollers are not supported by these programmers. You must use MP-IPE. Bill is investigating the support for this microcontroller. This support will be constrained to use two config words (not the four config words that MP-IPE supports). This will be released asap for testing.
    6. Bootloader support. Not tested. It is highly likely that bootloader support can be enabled for this microcontroller. Means no MP-IPE or Pickit required. I recommend we wait until we have resolved the current issues before we create the bootloader for this microcontroller.
    7. Hugh has requested the microcontroller from Microchip. Hugh will investigate the microcontroller when he receives it. He has provided me advice throughout my investigations.
    8. Internet research also shows that others have the same issue, if I ignore the posting created by XTal10 on another compilers support site, there are two unresolved cases with the same issue.
    9. MP-LAB-X. I can hand craft (see #3 above) a program to turn an LED on. But, as MP-LAB-X does not generate ASM I cannot use this code for root cause analysis. Howeverm this does reassure me that the test rig is valid. MP-LAB-X - an insight - code generated by the free compiler is NOT the same as the code generated by the licensed version. Code may not actually operate the microcontroller when using the free version of the XC8 compiler. Therefore, if your source file compilers and does not operate the microcontroller as expected this could be the root cause. Microchip have provided me a test program (for this microcontroller) that uses the licensed version of the XC8 compiler to ensure this was not the root cause of the issue (see #10 below). It is a fact that the XC8 compiler does does some specific changes to the generated hex file that can fix some of the silicon issues - so, having these XC8 hex files are simply reference points and not of great value to the identification of the root cause.
    10. Microchip assigned engineer. Microchip have assigned me an engineer, seperated from the open tickets, to support me. She now has created a HEX to light the LED. And, this DO NOTwork (see #9 above). She now has the ASM. She has not responded with her investigations with the ASM source.
    11. Using an alternative #chip configuration for creation of a program using Great Cow BASIC. I can get Great Cow BASIC to create a working program (LED lights up) but this approach is NOT valid as this is not supported and will expose other issues with respect to register management. This is simply a reference point that validates the test rig. BASICALLY - DO NOT DO THIS!

    I have source for XC8, Great Cow BASIC and ASM.
    .
    Current gut feel - this is something to do with the complexity of the configuration words and the initialisation of the clock. But, this is TOTALLY unproven.

    Test Activities

    Using the GCB Development board simple program to flash an LED. The program is shown below:
    This has an LED attached to porta.0 via a suitable resisitor.

     #chip 16f18326
     dir porta.0 out
     porta.0 = 1
     do forever
     loop
    

    This program generated by Great Cow BASIC does not light the LED.

    Currenly all tests fail except for when using MPLAB-X.

    Demos

    None. Adaption of the existing suite cannot be started until the root cause of the issue is resolved.

    Summary

    This microcontroller is not currently operating as expected when using Great Cow BASIC. Essentially, please wait until fixed by the huge team of people trying to figure this out. I am sure between Hugh, the Microchip engineer, Bill and myself we might be able to sort it.

     

    Last edit: Anobium 2016-07-29
  • xtal10

    xtal10 - 2016-07-29

    FYI
    On PB with questionable dev file I've just observed the following.....
    RA4 toggling, and TRISA = 0x2F and TRISC = 0x2F which is what I've set them..
    Now if I add BCF TRISA.2 TRISA does not change , but TRISA = %00101011 will change TRISA =0x2B, However RA4 then stops toggling.....I was wanting RA4, and RA2 to toggle ...
    In this case the BCF doesn't appear to be working - interesting event .....
    ,

     
    • Anobium

      Anobium - 2016-07-29

      We have fixes coming, just wait. I could not have given you more information.

      Please just short while.

       
    • Anobium

      Anobium - 2016-07-29

      The version of Great Cow BASIC you have DOES NOT SUPPORT this chip.
      Wait.

      The version you have WILL NOT operate a expected. It will not set the frequency, the configs or the ports. READ MY EARLIER posting - we have the baton to resolve the issue.

      I will issue you a new version once I have the root cause confirmed by Microchip, any related issues identified/resolved by Microchip then I will adapt the release. It will contain a number of demos - I currently have 10 fully operational.

      Microchip have just contacted me. They are confirming the root cause analysis.

       

      Last edit: Anobium 2016-07-29
  • Chris Roper

    Chris Roper - 2016-07-29

    As an outside observer to this conversation I think it is worth noting that:

    a) this is new Silicon, so new infact that MPLABX and XC8 do not fully support it yet.
    b) when Anobium contacted Microchip about the Issues they were deemed to be severe enough to allocate an Engineer to the problem, not just a help desk tech.
    c) Anobium has actually found errors and workarounds that Microchip themselves were not aware of and will have to redo several support files and all of the devices documentation.

    I am sure that Microchip are happy with the input they have received, especially if they can see a solution in the work that Anobium has done to date, rather than have to withdraw the part from market.

    I don't foresee a short term solution and would suggest that, if it is not critical that you use this particular device, you find another that has the features you need and is supported by MPLABX and Great Cow BASIC.

    Cheers
    Chris

     
  • Anobium

    Anobium - 2016-07-29

    Short update after a long day.

    1. This is new silicon.
    2. There is not much experience with chip - to quote a conversation today.
    3. Microchip have confirmed issues with the include file. We identified two issues that we confirmed in the last hour. The issues have a huge impact and ARE the root cause of the issues.
    4. The IDE C compiler and the IDE ASM compiler use different data sources for chip data hence I was getting the same issues with the ASM compiler.
    5. The route forward
    6. Revised .h files to support this new silicon
    7. Revised support .h files
    8. Complete testing of Great Cow BASIC for the new silicon
    9. Complete the demo's to test. Test results, so far, have raised further issues with CPP and PWM with this new silicon. Output, inputs, ADC, interrupts all have passed. 29 major tests to go......
    10. Release code to xtal10 for testing
    11. This probably impacted the following chips.
      16f18313, 16f18323, 16f18324, 16f18325, 16f18326, 16f18344 & 16f18346
    12. The revision Great Cow BASIC support internal will be for 32, 16, 8, 4, 2, 1, 0.5, 0.25, 0.125, 0.0625 24 and 12 are not supported without customisation of the user program.

    Now... only if xtal10 would read the email I sent to him... he would know I am trying to contact him. PM dont work, Google chat... no response.... Google email. :-) I will have a build for you soon.

    Anobium

     
  • Anobium

    Anobium - 2016-07-31

    Quick update. This was confirmed as a issue by Microchip. Please do not reply to this thread. Case closed.

    I will update the release and issue a patch as soon as practical.

     
<< < 1 2 3 (Page 3 of 3)

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.